CVE-2012-3606
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWebKit, as used in Apple iTunes before 10.7, allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption and application crash) via a crafted web site, a different vulnerability than other WebKit CVEs listed in APPLE-SA-2012-09-12-1.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMemory corruption vulnerability in WebKit rendering engine as embedded in Apple iTunes versions prior to 10.7. Remote attackers can achieve arbitrary code execution or cause denial of service by tricking users into visiting crafted malicious websites.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 10.6.3= 4.0.0= 4.0.1= 4.1.0= 4.2.0= 4.5= 4.5.0= 4.6= 4.6.0= 4.7= 4.7.0= 4.7.1<= 6.0.2= 6.0= 6.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed iTunes version on WindowsOpen iTunes, go to Help > About iTunes to view the version number, or check Programs and Features in Control PanelAffected if The version is 10.6.3 or earlier, or is one of: 4.0.0, 4.0.1, 4.1.0, 4.2.0, 4.5, 4.5.0, 4.6, 4.6.0, 4.7, 4.7.0, or 4.7.1
-
Verify iTunes WebKit component is in useThe vulnerability exists in the WebKit rendering engine used by iTunes' embedded browser. Check if the iTunes Store or links within iTunes are accessible, which indicates the WebKit component is activeAffected if The embedded browser component is present and functional in the installed iTunes version
-
Confirm iOS version for iPhone/iPad devices that sync with iTunesOn the iOS device, go to Settings > General > About > Version to check the iOS versionAffected if iOS version is 6.0, 6.0.1, or 6.0.2 (this applies to devices that may interact with the affected iTunes version)
Your environment is affected if iTunes version is 10.6.3 or earlier, or matches any of the specific 4.x versions listed, AND the embedded WebKit browser component is enabled and functional.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate Apple iTunes to version 10.7 or later to obtain the patched WebKit component. Avoid browsing untrusted websites using iTunes' embedded browser until patched.
iTunes 10.7 or later; iOS 6.1 or later (for iPhone OS devices)
- Upgrade iTunes to version 10.7 or later to resolve the WebKit memory corruption vulnerability
- For iPhone OS devices, upgrade to iOS 6.1 or later to address the vulnerability in iOS versions 6.0, 6.0.1, and 6.0.2
- After upgrading, verify the iTunes version by opening iTunes and navigating to Help > About iTunes
- Ensure the iOS device is updated by connecting it to a computer with the updated iTunes and checking for iOS updates via the device summary page
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3606 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2012-3606 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data