CVE-2012-3671
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 (the HTML rendering engine used by iTunes) that allows remote code execution or denial of service via maliciously crafted web pages. Exploits occur when a user visits a specially constructed website, causing the application to crash or potentially execute attacker-controlled code.
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.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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Verify iTunes is installedCheck for iTunes installation on Windows by looking in the registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for an iTunes entry, or check if C:\Program Files\iTunes\ or C:\Program Files (x86)\iTunes\ folders exist.Affected if No iTunes installation found means the system is not affected by this specific iTunes vulnerability.
-
Determine installed iTunes versionRead the iTunes version from the Windows registry at HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{iTunes GUID}\DisplayVersion, or right-click on iTunes.exe in the installation folder and view Properties > Details to see the File Version.Affected if The version number returned is in the affected list: 10.6.3 or lower, or exactly 4.0.0, 4.0.1, 4.1.0, 4.2.0, 4.5, 4.5.0, 4.6, 4.6.0, 4.7, or 4.7.1.
-
Confirm WebKit component usageVerify that iTunes includes the WebKit component by checking for the presence of WebKit.dll in the iTunes installation directory (typically C:\Program Files\iTunes\ or C:\Program Files (x86)\iTunes\).Affected if The WebKit.dll file exists in the iTunes folder, indicating the vulnerable component is present.
-
Check for vulnerable web content handlingThis vulnerability is triggered when iTunes processes malicious web content. Verify if iTunes has ever displayed web content from untrusted sources, or if any iTunes Store browsing or web-based iTunes functions were used.Affected if The system was used to browse web content through iTunes or visit untrusted websites via iTunes WebKit renderer.
A system is affected if iTunes is installed with version 10.6.3 or lower, or one of the specific affected 4.x versions, AND the WebKit component is present in the iTunes installation directory.
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.
From vendor dataUpdate iTunes to version 10.7 or later to obtain the patched WebKit component. For custom applications using WebKit, update to a patched WebKit revision and implement additional sandboxing or memory protection mitigations.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3671 — 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-3671 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