Loading vulnerability…
CVE-2011-3625 is a stack-based buffer overflow in the sub_read_line_sami function in subreader.c in MPlayer, as used in SMPlayer 0.6.9. The flaw is triggered when the application processes a crafted SAMI subtitle file containing an overly long string, causing a stack buffer to be overwritten. This can crash the application and, depending on exploitability conditions, may allow arbitrary code execution in the context of the user running the media player.
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 (mplayer_sami_bof.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2011-3625) in the handling of SAMI subtitle files by MPlayer (specifically, the version distributed with SMPlayer 0.6.8 on Windows XP SP3). The exploit works by generating a malicious .smi subtitle file (default name: msf.smi) containing a payload that triggers the overflow when loaded by the vulnerable MPlayer. The module allows the attacker to specify a Metasploit payload, which is encoded and embedded in the file. The exploit is triggered when a victim opens a movie file and then loads the malicious subtitle file, either via the GUI or the '-sub' command-line option. The repository is structured as a standard Metasploit exploit module, written in Ruby, and leverages the Metasploit FILEFORMAT exploit mixin to generate the malicious file. No network endpoints are involved; the attack vector is local, requiring user interaction to open the crafted 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.
2 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.