A stack-based buffer overflow exists in Apple iTunes versions 10.4.0.80 through 10.6.1.7 on both Windows and MacOS. The vulnerability is triggered when iTunes processes an extended M3U playlist file containing a specially crafted '#EXTINF:' tag. The content following '#EXTINF:,' is copied from a heap buffer to a fixed-size (0x274-byte) stack buffer without proper boundary checks, leading to a potential overflow. The vulnerable code is located in iTunes.dll, using REP MOVSD on Windows and MEMMOVE on MacOS for the unsafe copy operation. This flaw can be exploited by importing a malicious playlist file or by opening remote playlists via HTTP or itms:// links, including those embedded in web pages. Safari automatically opens iTunes for itms:// links, increasing the risk of exploitation. The vulnerability was discovered by Rh0 and fixed in iTunes 10.6.3.25.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.