dbcve.org
Mac Os XOperating system · Apple

CVE-2014-4410

MEDIUM · 6.8 CVSS v2.0 Published 2014-09-18
Fix available
A fix is available. Upgrade to after 10.9.4 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 8 and Apple TV before 7, 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-2014-09-17-1 and APPLE-SA-2014-09-17-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

A memory corruption vulnerability in WebKit allows remote attackers to execute arbitrary code or cause a denial of service via a crafted website. The flaw affects Apple iOS devices before version 8 and Apple TV devices before version 7. This is a client-side code execution vulnerability that can be triggered simply by a user visiting a malicious webpage.

MitigationUpdate affected Apple iOS devices to version 8 or later and Apple TV devices to version 7 or later to receive the vendor patch. Until patched, avoid browsing untrusted websites or disable JavaScript in Safari settings.

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
Mac Os XOperating system
Affected:<= 10.9.4
TvosOperating system
Affected:<= 6.2= 6.0= 6.0.1= 6.0.2= 6.1= 6.1.1= 6.1.2
Iphone OsOperating system
Affected:<= 7.1.2= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5= 7.0.6= 7.1= 7.1.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. Identify your Apple device type
    Determine whether the device is an iPhone, iPad, iPod touch, Apple TV, or Mac computer. On iOS devices, go to Settings > General > About. On Apple TV, go to Settings > General > About. On Mac, click the Apple menu and select About This Mac.
    Affected if The device is any Apple iOS, tvOS, or Mac OS X device
  2. Check iOS version on iOS devices
    On iPhone, iPad, or iPod touch, go to Settings > General > About and note the Version number. Compare it against the affected iOS versions: 7.0 through 7.1.2, or any version <= 7.1.2.
    Affected if iOS version is 7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.1, 7.1.1, 7.1.2, or any version 7.1.2 or lower
  3. Check tvOS version on Apple TV
    On Apple TV (2nd or 3rd generation), go to Settings > General > About and note the Version number. Compare it against the affected tvOS versions: 6.0, 6.0.1, 6.0.2, 6.1, 6.1.1, 6.1.2, or any version <= 6.2.
    Affected if tvOS version is 6.0, 6.0.1, 6.0.2, 6.1, 6.1.1, 6.1.2, or 6.2 or lower
  4. Check Mac OS X version
    On Mac, click the Apple menu > About This Mac and note the OS X version. Compare it against the affected version: 10.9.4 or any earlier version.
    Affected if Mac OS X version is 10.9.4 or lower, including 10.9 and earlier releases
  5. Confirm WebKit browser usage
    Verify that Safari is enabled and in use, or that any third-party iOS browser that uses the WebKit rendering engine is active. On iOS, Safari is the primary WebKit-based browser. On Apple TV, the built-in WebKit-based iTunes Store and streaming interfaces may be used.
    Affected if Safari or any WebKit-based browser is regularly used to browse websites

The environment is affected if the device runs iOS 7.1.2 or earlier, tvOS 6.2 or earlier, or Mac OS X 10.9.4 or earlier, and the user accesses untrusted websites via Safari or another WebKit-based browser.

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 10.9.4
Interim mitigation

Update affected Apple iOS devices to version 8 or later and Apple TV devices to version 7 or later to receive the vendor patch. Until patched, avoid browsing untrusted websites or disable JavaScript in Safari settings.

Fix this in Mac Os X 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-2014-4410 — 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-4410 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