dbcve.org
Iphone OsOperating system · Apple

CVE-2014-1289

MEDIUM · 6.8 CVSS v2.0 Published 2014-03-14
Fix available
A fix is available. Upgrade to after 7.0.6 or later.
See remediation →
77/100
Remediation priority · High
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 7.1 and Apple TV before 6.1, 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 CVE-2014-1290, CVE-2014-1291, CVE-2014-1292, CVE-2014-1293, and CVE-2014-1294.

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 allows remote attackers to execute arbitrary code or cause denial of service via maliciously crafted websites. Affects WebKit component in Apple iOS versions before 7.1 and Apple TV versions before 6.1.

MitigationUpdate affected iOS devices to version 7.1 or later and Apple TV devices to version 6.1 or later to obtain the patched WebKit component.

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:<= 7.0.6= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5
TvosOperating system
Affected:<= 6.0.2= 6.0= 6.0.1

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

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

  1. Check iOS version on iPhone or iPad
    Go to Settings > General > About on the iOS device and locate the Version field
    Affected if The version listed is 7.0.6 or lower, or any of 7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, or 7.0.5
  2. Check Apple TV version
    Navigate to Settings > General > About > Version on the Apple TV device
    Affected if The version listed is 6.0.2 or lower, or any of 6.0 or 6.0.1
  3. Verify WebKit component presence
    The WebKit rendering engine is built into Safari and all iOS apps that display web content. Confirm the device has Safari or any third-party browsers installed and has been used to browse the internet
    Affected if The device runs a vulnerable iOS or Apple TV version AND has been used to access websites, as the exploit is triggered through maliciously crafted web pages rendered by WebKit

You are affected if your iPhone, iPad, or Apple TV runs iOS version 7.0 through 7.0.6 or Apple TV version 6.0 through 6.0.2 and you use the device to browse the web

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.

From vendor data
Upgrade available Upgrade to a release after 7.0.6
Interim mitigation

Update affected iOS devices to version 7.1 or later and Apple TV devices to version 6.1 or later to obtain the patched WebKit component.

Fix this in Iphone Os Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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