Loading vulnerability…
A buffer overflow vulnerability exists in Apple iTunes version 4.7, where the application fails to properly handle long URLs embedded in .m3u or .pls playlist files. This flaw allows remote attackers to craft malicious playlist files that, when opened by a victim, trigger a buffer overflow condition, potentially leading to arbitrary code execution within the context of the user running iTunes.
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 targeting a stack buffer overflow vulnerability in Apple iTunes 4.7 (build 4.7.0.42) on Windows 2000 Pro SP4 and Windows XP Pro SP2 (CVE-2005-0043). The exploit works by serving a malicious .pls playlist file via an HTTP server. When a victim opens the playlist in a vulnerable version of iTunes, a buffer overflow is triggered, allowing the attacker to execute arbitrary code. The module allows the attacker to select a payload (up to 500 bytes, avoiding specific bad characters) and handles the delivery and exploitation process. The main attack vector is through the victim's browser or direct opening of the malicious playlist file from a network location. The repository is structured as a single Ruby file compatible with the Metasploit framework, leveraging its payload and handler infrastructure.
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.