Loading vulnerability…
A stack-based buffer overflow vulnerability exists in the UtilConfigHome.csp endpoint of InterSystems Caché 2009.1. The issue is triggered by a specially crafted HTTP GET request containing an oversized argument processed by the .csp handler. Due to insufficient bounds checking on attacker-controlled input, a stack buffer can be overrun, potentially overwriting saved control data and redirecting execution flow. The available information identifies InterSystems Caché 2009.1 as affected, but it is currently not available whether a patch was issued or what the full affected version range is.
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 in InterSystems Cache 2009.1 for Windows (CVE-2009-20005). The exploit works by sending a specially crafted HTTP GET request to the '/csp/sys/mgr/UtilConfigHome.csp' endpoint on TCP port 57772, triggering a buffer overflow and allowing arbitrary code execution. The module is operational and allows the attacker to specify a custom Metasploit payload (up to 650 bytes, with certain bad characters filtered). The exploit is designed for Windows 2000 SP4 English systems and leverages a specific return address in 'libhttpd.dll'. The repository is structured as a single Ruby file compatible with the Metasploit framework, and all exploit logic is contained within this 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.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.