Winamp versions 5.21, 5.5, and 5.51 contain multiple stack-based buffer overflows in in_mp3.dll when constructing stream titles from Ultravox streaming metadata. An overly long artist tag or name tag can overflow a stack buffer.
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 buffer overflow vulnerability in Winamp 5.24's in_mp3.dll, specifically when parsing Ultravox streaming metadata. The exploit sets up a malicious HTTP server (default port 8080) that serves a crafted Ultravox metadata response with an overly long artist tag, triggering the buffer overflow when processed by a vulnerable Winamp client. The module allows for arbitrary code execution via customizable Metasploit payloads. The attack can be triggered either by enticing a user to open a malicious stream in their browser or directly in the Winamp client. The code is written in Ruby and leverages Metasploit's TcpServer mixin for network delivery. The only endpoints involved are the attacker's HTTP server and the reference to the vulnerable in_mp3.dll plugin. The exploit is operational and not just a proof of concept, as it delivers a working payload and is integrated into 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.