Loading vulnerability…
A stack-based buffer overflow exists in Castillo Bueno Systems CCMPlayer 1.5. The vulnerability is triggered when a specially crafted m3u playlist file containing an overly long track name is processed by the application, leading to a buffer overflow on the stack. This can allow an attacker to overwrite critical stack data, including the return address, and execute 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 (1 hidden).
This repository contains a single Metasploit module (Ruby file) that exploits a stack-based buffer overflow vulnerability in CCMPlayer 1.5 (CVE-2011-5170). The exploit works by generating a malicious .m3u playlist file (default name: msf.m3u) with a specially crafted track name that overflows a buffer and overwrites the SEH (Structured Exception Handler) record. When the victim opens this file in CCMPlayer, the exploit triggers an SEH overwrite, redirecting execution to attacker-controlled shellcode embedded in the file. The module allows the attacker to specify a Metasploit payload, which is encoded and inserted into the file. The exploit is effective on multiple Windows versions (XP SP3, Vista, 7). The only endpoints involved are the generated .m3u file and the file path references within the exploit. The repository is structured as a standard Metasploit exploit module, with all logic contained in a single Ruby file.
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.