Loading vulnerability…
A stack-based buffer overflow exists in Un4seen XMPlay versions 3.3.0.5 and earlier. The vulnerability is triggered when the application parses a maliciously crafted M3U playlist file containing an overly long FileName field, leading to a buffer overflow on the stack. Additionally, a long DisplayName field can cause a crash, though code execution is only confirmed via the FileName vector.
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 (xmplay_asx.rb) that exploits a stack buffer overflow vulnerability (CVE-2006-6063) in XMPlay 3.3.0.4, a Windows media player. The exploit works by serving a malicious ASX playlist file via an HTTP server. When a victim opens this file in XMPlay, an overly long filename in the playlist triggers a buffer overflow, allowing the attacker to execute arbitrary code. The module supports customizable payloads (up to 750 bytes, avoiding specific bad characters) and targets Windows 2000 Pro SP4 and Windows XP Pro SP2 (English). The main attack vector is through the victim's browser or direct opening of the malicious playlist file. The only fingerprintable endpoint is the crafted file URI in the ASX file. The code is written in Ruby and is fully integrated into the Metasploit framework, making it a weaponized exploit.
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.