Loading vulnerability…
CVE-2010-10017 is a client-side buffer overflow vulnerability in WM Downloader version 3.1.2.2 triggered during processing of a specially crafted .m3u playlist file. The application does not properly validate input length while parsing playlist content, which allows an attacker to overflow a memory buffer and overwrite Structured Exception Handler (SEH) records. By controlling the SEH overwrite, an attacker can redirect execution flow and run arbitrary code. Exploitation is local in the sense that the victim must open the malicious .m3u file, after which the attacker-controlled payload executes in the 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 (wm_downloader_m3u.rb) that exploits a buffer overflow vulnerability in WM Downloader v3.1.2.2 (CVE-2010-10017). The exploit works by generating a specially crafted .m3u playlist file (default name: msf.m3u) that, when imported into the vulnerable application, triggers a buffer overflow and allows execution of arbitrary code. The module is written in Ruby and leverages the Metasploit framework's file format exploitation capabilities. The payload is customizable and can be any Metasploit-compatible shellcode. The attack vector is local, requiring user interaction to open the malicious file. The repository is operational and suitable for demonstrating code execution via a crafted file against the specified vulnerable version of WM Downloader.
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.