Loading vulnerability…
Multiple buffer overflows exist in Computer Associates (CA) Message Queuing (CAM / CAFT) versions 1.05, 1.07 (prior to Build 220_13), and 1.11 (prior to Build 29_13). These vulnerabilities allow remote attackers to execute arbitrary code via unspecified vectors, due to improper bounds checking in the handling of network messages.
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 (modules/exploits/windows/unicenter/cam_log_security.rb) that exploits a stack buffer overflow vulnerability in the CA CAM service, part of Unicenter TNG. The exploit targets the log_security() function by sending a specially crafted TCP packet with an overly long parameter, overwriting the stack and allowing arbitrary code execution. The module supports multiple Windows targets (Windows 2000, XP, 2003) and Unicenter v3.1, with specific return addresses for each. The exploit is operational and allows the attacker to execute custom payloads (such as reverse shells) with the privileges of the CAM service. The only network endpoint involved is the CAM service, typically running on TCP port 4104. The repository is structured as a standard Metasploit exploit module written in Ruby, and is not a detection script or fake exploit.
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.