dbcve.org
Iphone OsOperating system · Apple

CVE-2012-0625

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 rendering engine used by Apple iOS and iTunes allows remote code execution via maliciously crafted webpages. The vulnerability stems from improper memory handling during web content processing.

MitigationUpdate affected devices to iOS 5.1 or later and iTunes 10.6 or later to patch the WebKit vulnerability. Organizations should deploy OS/software updates through MDM or patch management infrastructure.

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 iTunes version on Windows
    Open Registry Editor (regedit) and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\iTunes.exe, or check Programs and Features to view the installed version of iTunes.
    Affected if The displayed iTunes version is earlier than 10.6
  2. Check iTunes version on macOS
    Open Terminal and run: defaults read /Applications/iTunes.app/Contents/Info CFBundleVersion, or right-click iTunes in Applications and select Get Info to view the version number.
    Affected if The displayed iTunes version is earlier than 10.6
  3. Identify iOS device version via MDM or device inventory
    Query your MDM solution (such as Jamf, Microsoft Intune, or similar) for enrolled iOS devices, or review device inventory reports to identify the iOS version installed on iPhones and iPads.
    Affected if Any managed iOS device runs a version earlier than 5.1
  4. Check for WebKit-based content processing
    Verify that iTunes includes the WebKit component for processing web content (iTunes stores and Genius features). This is present by default in affected versions.
    Affected if iTunes version is earlier than 10.6, meaning the bundled WebKit component contains the vulnerability
  5. Review enterprise device patch status
    Query your patch management or software distribution system for installed iTunes and iOS versions across managed endpoints and mobile devices.
    Affected if Systems show iTunes < 10.6 or iOS devices on versions < 5.1 that have not received the security update

An environment is affected if any system runs iTunes versions earlier than 10.6 or any iOS device runs a version earlier than 5.1, as these contain the vulnerable WebKit rendering engine.

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 to patch the WebKit vulnerability. Organizations should deploy OS/software updates through MDM or patch management infrastructure.

Recommended fix High confidence

iOS 5.1 and iTunes 10.6

  1. Upgrade Apple iOS device(s) to iOS 5.1 or later to resolve the WebKit vulnerability
  2. Upgrade Apple iTunes to version 10.6 or later on affected Windows or Mac systems
  3. After upgrading, verify the iOS and iTunes versions by checking Settings > General > About on iOS, or iTunes > About iTunes on desktop
Caveat iOS 5.1 and iTunes 10.6 are legacy versions from 2012; upgrading from very old iOS/iTunes versions may require synchronizing with updated iCloud services or could affect compatibility with older device backups

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

Fix this in Iphone Os Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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