CVE-2012-3607
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 · high confidenceThis is a memory corruption vulnerability in WebKit, the rendering engine used by Apple iTunes before version 10.7. Attackers can achieve remote code execution or cause a denial of service (application crash) by tricking users into visiting a maliciously crafted website.
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 if Apple iTunes is installedOn Windows, look for iTunes in Program Files (C:\Program Files\iTunes or C:\Program Files (x86)\iTunes) or check the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Apple Computer, Inc.\iTunesAffected if iTunes is not found in expected locations or registry keys are missing, meaning the product is not installed and this CVE does not apply
-
Determine installed iTunes versionRight-click iTunes.exe in the iTunes program folder, select Properties, and check the Details tab for the Version number. Alternatively, open iTunes and go to Help > About iTunesAffected if The version displayed is 10.6.3 or lower, or matches any of these affected versions: 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 WebKit component is presentCheck for the WebKit.dll file within the iTunes installation directory (typically in the iTunes folder under Program Files)Affected if WebKit.dll exists in the iTunes directory, confirming the vulnerable WebKit rendering engine component is present and could be exploited
-
Confirm iPhone OS version if applicableOn an iOS device, go to Settings > General > About and check the Version fieldAffected if The iOS version is 6.0, 6.0.1, or 6.0.2, making the device vulnerable to this WebKit flaw
You are affected if iTunes version is 10.6.3 or lower (including the 4.x series listed) or iOS version is 6.0 through 6.0.2, and the WebKit component is present in the installation.
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 iTunes to version 10.7 or later to patch the vulnerable WebKit component. Users should avoid visiting untrusted websites until the update is applied.
iTunes 10.7+ or iOS 6.1+
- Upgrade Apple 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 same WebKit vulnerability
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3607 — 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-3607 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