A buffer overflow vulnerability exists in BlueCoat WinProxy before version 6.1a and in the web console access functionality of ProxyAV before version 2.4.2.3. The vulnerability is triggered by a long Host: header in HTTP requests, which can overflow a buffer and allow remote attackers to execute arbitrary code on the affected system.
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 (1 hidden).
This repository contains a single Metasploit exploit module targeting a buffer overflow vulnerability (CVE-2005-4085) in Blue Coat Systems WinProxy (versions <= 6.1 R1a) on Windows. The exploit works by sending a specially crafted HTTP request to the WinProxy service, specifically overflowing the port value in the Host header to trigger a SEH-based buffer overflow. The module allows the attacker to deliver a customizable payload (up to 600 bytes, avoiding specific bad characters) that can result in arbitrary code execution with the privileges of the WinProxy service. The exploit is network-based, targeting TCP port 80, and is operational in maturity, as it provides a working payload mechanism. The only code file is a Ruby Metasploit module, and no additional files or detection scripts are present.
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.