Loading vulnerability…
CVE-2011-10022 affects SPlayer 3.7 and earlier. The vulnerability is a stack-based buffer overflow triggered when the application processes an HTTP response containing an overly long Content-Type header. Based on the provided information, the flaw is caused by improper bounds checking on the Content-Type header value during HTTP response handling. A malicious server can return a crafted header that overruns a stack buffer and overwrites the Structured Exception Handler (SEH), enabling control of execution flow and arbitrary code execution in the context of the SPlayer process. Exploitation requires the victim to open a media file that causes SPlayer to issue an HTTP request to attacker-controlled infrastructure.
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/misc/splayer_content_type.rb) that exploits a buffer overflow vulnerability in SPlayer version 3.7 or prior (CVE-2011-10022). The exploit works by running a malicious HTTP server that delivers a specially crafted 'Content-Type' header when SPlayer requests a media file URL. The buffer overflow allows for arbitrary code execution on the victim's machine, typically resulting in a shell or Meterpreter session. The module is operational and allows for customizable payloads using Metasploit's framework. The exploit targets Windows XP SP2/SP3 and requires the victim to open a media file URL pointing to the attacker's server. The code is written in Ruby and leverages Metasploit's HttpServer::HTML mixin to handle incoming requests and deliver the exploit. No hardcoded IPs or domains are present; the attacker configures the server endpoint.
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.