Loading vulnerability…
A stack-based buffer overflow exists in the BCAAA component prior to build 60258, as used in Blue Coat ProxySG versions 4.2.3 through 6.1 and ProxyOne. The vulnerability is triggered by sending a large packet to the BCAAA synchronization port (16102/tcp), which can result in the execution of arbitrary code by a remote attacker.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit exploit module targeting a stack buffer overflow vulnerability (CVE-2011-5124) in the Blue Coat Authentication and Authorization Agent (BCAAA) version 5.4.6.1.54128, specifically in the bcaaa-130.exe process listening on TCP port 16102. The exploit leverages a crafted buffer containing a ROP chain to bypass DEP/ASLR protections and delivers a customizable Metasploit payload (up to 936 bytes, avoiding null bytes). The module allows the user to specify the number of exploit attempts (default 3) due to the unreliable nature of the vulnerability. Upon successful exploitation, arbitrary code execution is achieved on the target Windows system. The code is written in Ruby and is structured as a standard Metasploit module, making use of the framework's payload and handler mechanisms. No hardcoded IP addresses or URLs are present; the only fingerprintable endpoint is the TCP port 16102, which is the default for the vulnerable service.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.