Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2017-8870: Buffer Overflow in AudioCoder 0.8.46 via .m3u File

Published Jul 27, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3
EPSS13.7%97th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Mediacoderhq
IdentifiersCVE-2017-8870CWE-120

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows remote attackers to execute arbitrary code in the context of the user running AudioCoder, potentially leading to full system compromise if the user has sufficient privileges.

Mitigation

If you can’t patch tonight, do this now.

Avoid opening untrusted .m3u files with AudioCoder 0.8.46. Employ host-based intrusion prevention systems and application whitelisting to reduce the risk of exploitation.

Remediation

Patch, then assume compromise.

Upgrade to a patched version of AudioCoder, if available, that addresses the buffer overflow vulnerability. If no patch is available, discontinue use of the affected version.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
MediacoderhqAudiocoderapplication
FAQ

Frequently asked questions

Is CVE-2017-8870 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2017-8870 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2017-8870?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2017-8870, the earliest disclosed May 1, 2013.
Is there a patch for CVE-2017-8870?
Upgrade to a patched version of AudioCoder, if available, that addresses the buffer overflow vulnerability. If no patch is available, discontinue use of the affected version.
What products are affected by CVE-2017-8870?
Mediacoderhq Audiocoder.
How severe is CVE-2017-8870?
CVE-2017-8870 has a CVSS v3 score of 7.8 (High) and an EPSS score of 13.7% (97th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

No public activity tracked yet. Mallory keeps watching.

View more in app →

No public activity observed for this vulnerability.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.