Loading vulnerability…
CVE-2010-10016 affects BS.Player version 2.57 build 1051 on Windows. The vulnerability is in the playlist import/parsing functionality for .m3u files. When the application processes playlist entries containing excessively long URLs, it does not properly validate the length of the input before copying or handling it in the Unicode parsing path, leading to a stack-based buffer overflow condition. The overflow is severe enough to overwrite Structured Exception Handler (SEH) records, which can be leveraged during exploitation. The issue is triggered when a user opens a crafted .m3u playlist file in the vulnerable client.
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 (modules/exploits/windows/fileformat/bsplayer_m3u.rb) that exploits a Unicode SEH buffer overflow vulnerability in BS.Player version 2.57 (v2.5.7.1051) on Windows XP and Windows 7. The exploit works by generating a specially crafted .m3u playlist file containing a payload that, when imported into BS.Player, triggers a buffer overflow and allows arbitrary code execution. The module leverages Metasploit's payload system, allowing the attacker to select from a variety of payloads (such as reverse shells or Meterpreter sessions). The attack vector is local, requiring the victim to open the malicious file. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The only fingerprintable endpoint is the crafted .m3u file itself. The code is written in Ruby and follows the standard Metasploit module structure.
5 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.