Loading vulnerability…
A stack-based buffer overflow vulnerability exists in Fat Player version 0.6b. The vulnerability is triggered when the application processes a .wav file containing an excessively long string, leading to a buffer overflow on the stack. This can allow an attacker to overwrite critical stack data, including the return address, and potentially 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 (3 hidden).
This repository contains a single Metasploit module (modules/exploits/windows/fileformat/fatplayer_wav.rb) that exploits a buffer overflow vulnerability in Fat Player Media Player version 0.6b (CVE-2009-4962). The exploit works by generating a specially crafted WAV file (default name: msf.wav) that, when imported into the vulnerable application, triggers a buffer overflow and allows execution of arbitrary code. The module allows the attacker to embed any Metasploit payload (up to 500 bytes, avoiding null and newline characters) into the malicious file. The attack vector is local, requiring the victim to manually open the malicious file. The code is operational and leverages Metasploit's file format and SEH (Structured Exception Handler) exploitation techniques. The repository is structured as a single Ruby file compatible with the Metasploit framework, and its sole purpose is to generate the exploit file for this specific vulnerability.
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.