CVE-2012-0611
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 iOS before 5.1 and iTunes before 10.6, 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-03-07-1 and APPLE-SA-2012-03-07-2.
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 confidenceMemory corruption vulnerability in WebKit rendering engine allows remote code execution or DoS via crafted websites. Affected: iOS <5.1 and iTunes <10.6. Exploitation requires user to visit malicious page.
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< 5.1< 10.6CVSS 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 iOS version on iPhone or iPadOpen Settings app, go to General > About, and read the Version field. Alternatively, connect device to computer and view version in iTunes device summary.Affected if Version number is less than 5.1 (for example, 5.0.x, 4.x series)
-
Check iTunes version on WindowsOpen iTunes, go to Help > About iTunes and note the version number displayed in the dialog.Affected if Version number is less than 10.6 (for example, 10.5.x or earlier)
-
Check iTunes version on macOSOpen iTunes, click the iTunes menu > About iTunes and note the version number displayed.Affected if Version number is less than 10.6 (for example, 10.5.x or earlier)
-
Confirm WebKit-based browser usageNote that this vulnerability affects the WebKit rendering engine used by Mobile Safari on iOS and iTunes for Windows (via the iTunes Store or WebKit rendering). The flaw is triggerable when visiting malicious websites.Affected if Using Safari on iOS version <5.1, or using iTunes with iTunes Store access on iTunes <10.6
You are affected if iOS is below 5.1 or iTunes is below 10.6, as the vulnerable WebKit component is present in those versions.
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 · scoped5.110.6
Update iOS to 5.1+ and iTunes to 10.6+ to patch vulnerable WebKit component. No network-level mitigation available; client-side patching required.
iOS 5.1 and iTunes 10.6
- For iOS devices: Navigate to Settings > General > Software Update and install iOS 5.1 or later
- For iTunes: Download and install iTunes 10.6 or later from Apple's official website
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-0611 — 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-0611 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