CVE-2012-10031 affects BlazeVideo HDTV Player Pro v6.6.0.3. The vulnerability is a stack-based buffer overflow in the handling of user-controlled data embedded in .plf playlist files. During parsing of a crafted .plf file, the MediaPlayerCtrl.dll component calls PathFindFileNameA() to obtain a filename from a URL-like string, then copies the returned value into a fixed-size stack buffer using an inline strcpy operation without bounds checking. An overlong filename value can therefore overwrite stack memory, causing a crash and potentially enabling arbitrary code execution in the security context of the current user.
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 BlazeVideo HDTV Player Pro v6.6.0.3 (CVE-2012-10031). The exploit abuses improper filename handling in the MediaPlayerCtrl.dll component, where a long filename embedded in a specially crafted .plf file triggers a buffer overflow via an unsafe strcpy operation. The module generates a malicious .plf file (default name: msf.plf) containing a payload that overwrites the SEH (Structured Exception Handler) and executes arbitrary code when opened by the vulnerable application. The exploit is operational, allowing the attacker to select and encode a payload using Metasploit's framework. The attack vector is local, requiring user interaction to open the malicious file. The only fingerprintable endpoint is the generated .plf file. The code is written in Ruby and follows the standard Metasploit module structure.
3 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.