dbcve.org
Iphone OsOperating system · Apple

CVE-2012-0612

HIGH · 9.3 CVSS v2.0 Published 2012-03-08
Fix available
A fix is available. Upgrade to 5.1 / 10.6 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
WebKit, 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 confidence

Memory corruption vulnerability in WebKit (used by Safari in iOS and iTunes) allows remote code execution via maliciously crafted websites. Attackers can achieve arbitrary code execution or cause application crashes through heap corruption when users visit specially crafted webpages.

MitigationUpdate affected devices to iOS 5.1 or later and iTunes 10.6 or later. Apply vendor security patches immediately as this is a remote code execution vulnerability with CVSS 9.3.

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
Iphone OsOperating system
Affected:< 5.1
ItunesApplication
Affected:< 10.6

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if iTunes is installed
    On Windows, open Control Panel > Programs and Features or right-click the iTunes shortcut and select Properties. On Mac, open Finder and navigate to /Applications to locate iTunes.
    Affected if iTunes is present on the system
  2. Determine installed iTunes version
    On Windows, right-click the iTunes icon, select Properties, and look at the version number on the Details tab. On Mac, right-click iTunes in Applications, select Get Info, and read the version number.
    Affected if Version displayed is less than 10.6 (for example, 10.5.x or earlier)
  3. Identify iOS device model and iOS version
    Connect the iPhone/iPad to a computer with iTunes. Select the device in iTunes. In the Summary tab, look for the version number next to 'Version' (for example, 5.0.1).
    Affected if iOS version shown is less than 5.1 (for example, 5.0.x, 4.x, etc.)
  4. Verify WebKit-based browser usage
    Confirm that Safari is the default browser or has been used on the iOS device. This vulnerability is triggered through Safari visiting malicious webpages.
    Affected if Safari has been used to browse the web on an affected iOS version

You are affected if iTunes is installed with version below 10.6, or if any iOS device runs a version below 5.1, and Safari has been used to access untrusted websites.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 5.1 / 10.6 or later
Fixed in 5.110.6
Interim mitigation

Update affected devices to iOS 5.1 or later and iTunes 10.6 or later. Apply vendor security patches immediately as this is a remote code execution vulnerability with CVSS 9.3.

Recommended fix High confidence

iOS 5.1 and iTunes 10.6

  1. Back up your iOS device data before performing the update
  2. For iOS devices: Navigate to Settings > General > Software Update and install iOS 5.1 or later
  3. For iTunes: Download and install iTunes 10.6 or later from Apple's official website
  4. After updating, verify the installation by checking iOS version in Settings > General > About > Version
  5. Restart the device and iTunes to ensure the security update takes full effect
Caveat iOS 5.1 may have older device compatibility limitations; ensure your iPhone/iPad/iPod touch model is supported by iOS 5.1 before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Iphone Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-0612 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-0612 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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