CVE-2007-2864 is a stack-based buffer overflow in the CA (formerly Computer Associates) Anti-Virus engine's processing of CAB archives. The flaw exists before content update 30.6 and is triggered when the engine parses a .CAB file containing a large invalid value in the coffFiles field. A remote attacker can supply a crafted CAB archive to the vulnerable scanning engine, causing memory corruption on the stack and potentially achieving arbitrary 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.
This repository contains a single Metasploit exploit module targeting a stack buffer overflow vulnerability in CA eTrust Antivirus 8.1.637 (CVE-2007-2864). The exploit works by generating a specially crafted CAB file ('msf.cab' by default) that, when scanned or opened by the vulnerable antivirus engine on Windows 2000 or Windows XP SP0/SP1, triggers a buffer overflow and allows arbitrary code execution. The module is written in Ruby and leverages Metasploit's FILEFORMAT exploit mixin. The payload is customizable, with a maximum size of 250 bytes, and is inserted into the CAB file at the appropriate offset to gain control of execution flow. The exploit does not require network interaction; the attack vector is local, relying on the target system processing the malicious file. The repository structure is typical for a Metasploit module, with all 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.
1 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.