Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2009-4755: Stack Buffer Overflow in Mercury Audio Player 1.21 Playlist Parsing

Published Mar 29, 2010 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.3Critical · v2
EPSS6.8%94th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Mercuryaudio
IdentifiersCVE-2009-4755CWE-121

Mercury Audio Player 1.21 contains multiple stack-based buffer overflow vulnerabilities in its handling of playlist files. Specifically, when parsing malformed .b4s or .pls playlist files containing excessively long strings, the application fails to properly check buffer boundaries, leading to stack-based buffer overflows. This flaw allows remote attackers to craft malicious playlist files that, when opened by the victim, can trigger arbitrary code 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 with the privileges of the user running Mercury Audio Player. This can lead to full system compromise if the user has administrative rights.

Mitigation

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

Do not open playlist files from untrusted sources. Employ host-based intrusion prevention systems (HIPS) and application whitelisting to reduce the risk of exploitation. Consider running the application with reduced privileges to limit impact.

Remediation

Patch, then assume compromise.

Upgrade to a patched version of Mercury Audio Player, if available. If no patch is available, discontinue use of the affected version and avoid opening untrusted .b4s or .pls files.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
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
MercuryaudioAudio Playerapplication
FAQ

Frequently asked questions

Is CVE-2009-4755 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2009-4755 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2009-4755?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2009-4755.
Is there a patch for CVE-2009-4755?
Upgrade to a patched version of Mercury Audio Player, if available. If no patch is available, discontinue use of the affected version and avoid opening untrusted .b4s or .pls files.
What products are affected by CVE-2009-4755?
Mercuryaudio Audio Player.
How severe is CVE-2009-4755?
CVE-2009-4755 has a CVSS v2 score of 9.3 (Critical) and an EPSS score of 6.8% (94th 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.