dbcve.org
Iphone OsOperating system · Apple

CVE-2012-0627

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 (Apple's browser engine) allows remote code execution or denial of service via malicious websites. Affects iOS devices before version 5.1 and iTunes installations before version 10.6. The vulnerability stems from improper memory handling when processing crafted web content.

MitigationApply vendor patches by updating iOS to version 5.1 or later and iTunes to version 10.6 or later. Until updates are applied, restrict user access to untrusted websites.

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 iOS version on iPhone/iPad/iPod Touch
    On the device, go to Settings > General > About and look at the Version field. Alternatively, connect the device to a computer with iTunes and select the device to view its summary page which displays the iOS version.
    Affected if Version number is less than 5.1 (for example, 5.0.1, 4.x, etc.)
  2. Check iTunes version on Windows or Mac
    Open iTunes and navigate to Help > About iTunes (Windows) or iTunes > About iTunes (Mac). The version number appears in the dialog box that opens.
    Affected if Version number is less than 10.6 (for example, 10.5.x, 10.4.x, etc.)
  3. Verify WebKit-based browser usage (iOS)
    Confirm that Mobile Safari is used to browse web content. The vulnerability exists in the WebKit rendering engine that powers Mobile Safari. Open Mobile Safari and attempt to load a webpage to confirm the browser is functional.
    Affected if Mobile Safari is actively used and the iOS version is below 5.1, meaning the vulnerable WebKit component is present and exploitable through malicious web content.

If either iOS version is below 5.1 or iTunes version is below 10.6, the environment contains the vulnerable WebKit component and could be exploited via malicious 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

Apply vendor patches by updating iOS to version 5.1 or later and iTunes to version 10.6 or later. Until updates are applied, restrict user access to untrusted websites.

Recommended fix High confidence

iOS 5.1 and iTunes 10.6

  1. Back up your iOS device and iTunes library before upgrading
  2. For iOS: Connect your iPhone, iPad, or iPod touch to your computer, open iTunes, select your device, and click 'Check for Update' to install iOS 5.1
  3. For iOS: Alternatively, go to Settings > General > Software Update on the device to update to iOS 5.1 if available
  4. For iTunes: Download iTunes 10.6 from Apple's website or through the iTunes application and install it
  5. Restart your computer after upgrading iTunes
  6. Verify the WebKit version in Safari to confirm the update was applied
Caveat iOS 5.1 may not support older devices; consider upgrading to a more recent iOS version if your device supports it, as iOS 5.1 is from 2012

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-0627 — 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-0627 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