CVE-2008-2639 is a stack-based buffer overflow in the ODBC server service of Citect CitectSCADA versions 6 and 7 and CitectFacilities version 7. The flaw is triggered by a long string supplied in the second application packet of a TCP session to the ODBC service on port 20222, allowing remote code execution.
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 stack buffer overflow vulnerability in the ODBC daemon of CitectSCADA and CitectFacilities (CVE-2008-2639). The exploit is implemented in Ruby and is designed to be used within the Metasploit Framework. It targets multiple versions of CitectSCADA (5.x, 6.x, 7.x) running on Windows platforms. The exploit works by sending a specially crafted payload over TCP (default port 20222) to the vulnerable ODBC service, resulting in remote code execution. The module allows for customizable payloads (e.g., reverse shell, meterpreter) and includes various target configurations for different versions and DLLs. The code is operational and ready for use within Metasploit, requiring only the correct target selection and payload configuration. No hardcoded IPs or URLs are present, but the default network port is fingerprintable. The repository is structured as a typical Metasploit module with all exploit logic contained in a single Ruby file.
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.