Loading vulnerability…
CVE-2009-20002 affects Millenium MP3 Studio versions up to and including 2.0. The vulnerability is a stack-based buffer overflow in the application's handling of .pls playlist files. Specifically, the application does not properly validate the length of the File1 field while parsing a playlist, allowing a specially crafted .pls file to overflow a stack buffer. Successful exploitation can overwrite the Structured Exception Handler (SEH) and redirect execution flow to attacker-controlled code, resulting in arbitrary code execution in the context of the user running the application.
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 in Millenium MP3 Studio 2.0 (CVE-2009-20002). The exploit generates a malicious .pls (playlist) file, which, when opened by a victim using the vulnerable application, triggers a buffer overflow and allows execution of arbitrary code. The module leverages SEH (Structured Exception Handler) overwrite using a return address from xaudio.dll. The payload is customizable and can be any Metasploit-compatible shellcode up to 1000 bytes, avoiding certain bad characters. The attack vector is primarily local (user must open the file), but the description notes a potential for remote exploitation if the PLS extension is registered to the application and opened via a browser (not tested in this module). The repository is structured as a typical Metasploit exploit module written in Ruby, with all logic contained in a single file.
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.