dbcve.org
SafariWeb browser · Apple

CVE-2014-4415

MEDIUM · 6.8 CVSS v2.0 Published 2014-09-18
Fix available
A fix is available. Upgrade to after 7.1.2 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

Memory corruption vulnerability in WebKit affecting iOS devices before version 8 and Apple TV devices before version 7. Remote attackers can trigger the flaw by tricking users into visiting specially crafted malicious websites, potentially leading to arbitrary code execution or denial of service through application crashes.

MitigationUpdate affected Apple iOS devices to version 8 or later and Apple TV devices to version 7 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
SafariWeb browser
Affected:= 6.1= 7.1
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 if you use an iOS device (iPhone, iPad, or iPod Touch) that may run Safari
    Check your device model and confirm it is an Apple iOS device. Note that this vulnerability affects Safari on iOS, not macOS.
    Affected if You have an iOS device running Safari as the browser
  2. Check the iOS version installed on your iOS device
    Go to Settings > General > About on your iOS device and look at the 'Version' field. Compare this version number to the affected ranges: iOS 7.0 through 7.1.2, or any version 7.1 or 7.1.1 specifically.
    Affected if Your 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, or 7.1.2, or any version 7.1 or below (7.1.2 or earlier)
  3. Identify if you use an Apple TV device
    Check if you have an Apple TV set-top box. This is a separate device from iOS devices.
    Affected if You own an Apple TV device
  4. Check the tvOS or firmware version on your Apple TV
    On Apple TV (2nd generation or later), go to Settings > General > About to view the version. Compare to affected versions: 6.0, 6.0.1, 6.0.2, 6.1, 6.1.1, 6.1.2, or any version up to and including 6.2.
    Affected if Your Apple TV firmware is version 6.0, 6.0.1, 6.0.2, 6.1, 6.1.1, 6.1.2, or 6.2 or earlier
  5. Verify that Safari is in use as the browser on the affected iOS device
    Confirm Safari is the default browser or the browser you use to visit websites. The vulnerability is triggered through Safari rendering malicious web content.
    Affected if You use Safari as your browser on an affected iOS version (iOS 7.x or earlier)

You are affected if you use Safari on an iOS device running version 7.0 through 7.1.2 (or any iOS version 7.1.2 or earlier), or if you use an Apple TV running firmware version 6.2 or earlier.

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.1.2
Interim mitigation

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

Fix this in Safari Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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