A stack-based buffer overflow exists in lcfd.exe, a component of IBM Tivoli Management Framework versions 3.7.1, 4.1, 4.1.1, and 4.3.1. The vulnerability is triggered when a remote authenticated user sends a specially crafted request with an overly long 'opts' field, leading to a buffer overflow condition. This can allow the attacker to overwrite the stack and potentially execute arbitrary code with the privileges of the lcfd process.
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-2011-1220) in IBM Tivoli Endpoint Manager (lcfd.exe) versions 3.7.1, 4.1, 4.1.1, and 4.3.1 on Windows. The exploit works by sending a specially crafted HTTP POST request to the /addr endpoint on TCP port 9495, using hardcoded credentials (tivoli:boss) to bypass authentication. The payload is user-supplied (up to 400 bytes, avoiding null, CR, and LF), allowing for arbitrary code execution on the target system. The module is operational and leverages Metasploit's payload system, making it flexible for various post-exploitation actions. The repository structure is standard for Metasploit, with the exploit logic and configuration 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.