CVE-2012-3675
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 bundled in Apple iTunes versions prior to 10.7. Exploitation occurs through a maliciously crafted website causing heap corruption, leading to arbitrary code execution or denial of service via application crash.
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.
-
Identify installed iTunes versionOn Windows, open Control Panel > Programs and Features, locate iTunes, and note the version. On Mac, open iTunes and select iTunes > About iTunes. Alternatively, right-click the iTunes.exe file and select Properties > Details to view the version.Affected if The displayed version is 10.6.3 or lower, or matches any of these: 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 is the Apple-provided versionConfirm the software is Apple iTunes (not a third-party alternative) by checking the publisher in Programs and Features or the application name in /Applications on Mac.Affected if The installed software is Apple iTunes and the version falls within the affected ranges listed above.
-
Confirm WebKit component is presentWebKit is bundled with iTunes for Store browsing and media preview features. Check if iTunes has been used to access the iTunes Store or if related web content rendering components exist in the iTunes installation directory.Affected if iTunes is installed with its standard components intact and has been used for web-facing features like the iTunes Store.
If the installed Apple iTunes version matches 10.6.3 or earlier, or any of the 4.x versions listed (4.0.0 through 4.7.1), the environment is vulnerable to CVE-2012-3675 when iTunes is used to browse untrusted web content.
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 Apple iTunes to version 10.7 or later to obtain the patched WebKit component. Users should avoid untrusted websites until the update is applied.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-3675 — 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-3675 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