Loading vulnerability…
CVE-2011-10027 is a stack-based buffer overflow in AOL Desktop 9.6, specifically in the Tool\rich.rct component while parsing .rtx files. The flaw is triggered by an overly long string embedded in a hyperlink tag within a crafted .rtx file. Based on the provided description, the vulnerable condition is caused by unsafe strcpy operations that copy attacker-controlled data into a fixed-size stack buffer without proper bounds checking. Successful exploitation can occur when a victim opens the malicious .rtx file, leading to memory corruption and potential 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 Metasploit module that exploits a buffer overflow vulnerability (CVE-2011-10027) in AOL Desktop 9.6's Tool\rich.rct component. The exploit works by generating a malicious .rtx file containing an overly long hyperlink tag, which, when opened by a user in AOL Desktop 9.6, triggers a buffer overflow due to unsafe use of strcpy. This allows for arbitrary code execution with the privileges of the user. The module supports multiple targets, including Windows XP SP3 and Windows 7, with specific return addresses and ROP chains for NX bypass. The payload is customizable using Metasploit's payload system, typically allowing for reverse shells or Meterpreter sessions. The only fingerprintable endpoint is the malicious .rtx file itself, which must be delivered to and opened by the victim. The repository structure is typical for Metasploit, with the exploit logic contained in a single Ruby file under the appropriate modules directory.
2 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.