A stack-based buffer overflow exists in the web server component of Cogent Real-Time Systems Cogent DataHub before 7.3.0, OPC DataHub before 6.4.22, Cascade DataHub before 6.4.22 on Windows, and DataHub QuickTrend before 7.3.0. The vulnerability is triggered by sending a long HTTP header, which can overflow a stack buffer, potentially allowing remote attackers to crash the daemon or execute arbitrary code.
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 module targeting a stack-based buffer overflow vulnerability (CVE-2013-0680) in the HTTP server of Cogent DataHub version 7.3.0 on Windows XP SP3. The exploit works by sending a specially crafted HTTP request with an overly long header, triggering the overflow and allowing arbitrary code execution. The module includes a check method to verify if the target is running the vulnerable service by requesting '/datahub.asp' and looking for a specific HTML title. The exploit method constructs a payload that overwrites the Structured Exception Handler (SEH) and delivers shellcode, leveraging Metasploit's payload system. The only file present is a Ruby script structured as a standard Metasploit exploit module, making use of the framework's HTTP client and SEH exploitation mixins. No hardcoded IPs or domains are present; the exploit targets the service at a user-specified host and port.
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.