Loading vulnerability…
A stack-based buffer overflow vulnerability exists in CoCSoft Stream Down version 6.8.0. The vulnerability is triggered when a remote web server sends an excessively long response to a download request, causing a buffer overflow on the stack. This can allow an attacker to overwrite critical stack data, including the return address, and execute arbitrary code in the context of the affected application.
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 module (modules/exploits/windows/misc/stream_down_bof.rb) that exploits a buffer overflow vulnerability (CVE-2011-5052) in CoCSoft StreamDown version 6.8.0 for Windows. The exploit works by running a malicious HTTP server that waits for a vulnerable StreamDown client to connect. When the client connects and sends a request with a matching User-Agent, the server responds with a specially crafted payload that overflows a buffer, overwrites the Structured Exception Handler (SEH), and executes arbitrary code. The payload is customizable using Metasploit's payload system, allowing for actions such as spawning a shell or running arbitrary commands. The exploit is operational and requires the attacker to lure or wait for a vulnerable client to connect to the attacker's server. The only fingerprintable endpoint is the HTTP server set up by the module, which is used to deliver the exploit. The code is written in Ruby and is structured as a standard Metasploit exploit module.
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.