A buffer overflow vulnerability exists in AudioCoder version 0.8.46, which can be triggered by processing a specially crafted .m3u playlist file. The vulnerability arises due to improper bounds checking when handling input from the .m3u file, allowing an attacker to overwrite memory and potentially control program execution.
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 (1 hidden).
This repository contains a single Metasploit module (audio_coder_m3u.rb) that exploits a buffer overflow vulnerability (CVE-2017-8870) in AudioCoder version 0.8.18.5353 on Windows XP SP3 and Windows 7 SP1. The exploit works by generating a specially crafted .m3u playlist file containing a long buffer, a SEH overwrite, and a customizable Metasploit payload. When a victim opens this file with a vulnerable version of AudioCoder, arbitrary code execution is achieved with the privileges of the user. The module is fully integrated into the Metasploit framework, allowing for easy payload customization and file generation. The attack vector is local, requiring user interaction to open the malicious file. The only fingerprintable endpoint is the crafted .m3u file itself.
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.