A buffer overflow vulnerability exists in the goaway function of the aim:goaway URI handler in AOL Instant Messenger (AIM) version 5.5, including 5.5.3595. The vulnerability is triggered when a remote attacker sends a specially crafted aim:goaway URI with an excessively long Away message, causing a buffer overflow and potentially allowing the execution of arbitrary code.
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 (2 hidden).
This repository contains a single Metasploit module (aim_goaway.rb) that exploits a buffer overflow vulnerability in the 'goaway' URI handler of AOL Instant Messenger 5.5 on Windows. The exploit works by acting as a malicious HTTP server that serves a web page containing an iframe with a specially crafted 'aim:goaway?message=' URI. When a victim with a vulnerable version of AIM visits the page, the oversized 'message' parameter triggers an SEH overwrite, allowing arbitrary code execution. The module supports customizable payloads up to 1014 bytes and targets Windows NT/2000/XP/2003 platforms. The main attack vector is through the browser, leveraging the AIM protocol handler. The only fingerprintable endpoint is the 'aim:goaway?message=' URI. The exploit is operational and part of the Metasploit framework.
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.