Loading vulnerability…
A stack-based buffer overflow vulnerability exists in Apple iTunes versions prior to 8.2. The vulnerability is triggered when iTunes parses a specially crafted 'itms:' URL containing an excessively long component after a colon. This flaw allows remote attackers to execute arbitrary code or cause a denial of service (application crash) by enticing a user to open a maliciously crafted URL. The vulnerability affects iTunes on Mac OS X v10.4.10 or later, Mac OS X Server v10.4.10 or later, and Windows Vista or XP SP2 or later.
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 (3 hidden).
This repository contains a single Metasploit module (modules/exploits/multi/browser/itms_overflow.rb) that exploits a stack-based buffer overflow vulnerability in Apple iTunes 8.1.1's handling of itms:// URLs (CVE-2009-0950). The exploit is delivered via a malicious HTML page served by the module's built-in HTTP server. When a victim visits the page using Safari (or another browser that automatically opens itms:// URLs in iTunes), a specially crafted itms:// URL is triggered, causing a buffer overflow in iTunes and allowing arbitrary code execution. The payload is customizable and must be vfork-based due to iTunes' multithreaded architecture. The module is written in Ruby and is designed to be used within the Metasploit Framework. The main attack vector is browser-based, leveraging the automatic handling of itms:// URLs on Mac OS X. The only fingerprintable endpoints are the itms:// protocol handler and the HTTP server endpoint serving the exploit page.
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.