dbcve.org
SafariWeb browser · Apple

CVE-2014-1364

MEDIUM · 6.8 CVSS v2.0 Published 2014-07-01
Fix available
A fix is available. Upgrade to after 7.1.1 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.2, Apple Safari before 6.1.5 and 7.x before 7.0.5, and Apple TV before 6.1.2, 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-06-30-1, APPLE-SA-2014-06-30-3, and APPLE-SA-2014-06-30-4.

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 · moderate confidence

WebKit memory corruption vulnerability allowing remote code execution or denial of service via crafted malicious web pages. The flaw affects the WebKit rendering engine in Apple iOS, Safari, and Apple TV.

MitigationApply vendor patches: update iOS to 7.1.2 or later, Safari to 6.1.5/7.0.5 or later, and Apple TV to 6.1.2 or later. As a temporary workaround, 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
SafariWeb browser
Affected:= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4<= 6.1.4= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5
Iphone OsOperating system
Affected:<= 7.1.1= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5= 7.0.6= 7.1
TvosOperating system
Affected:<= 6.1.1= 6.0= 6.0.1= 6.0.2= 6.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 the Apple product running WebKit
    Determine if the system runs Safari on OS X, iOS on iPhone/iPad, or Apple TV. This CVE affects WebKit in all three platforms.
    Affected if Any of these three Apple products are in use
  2. Check Safari version on OS X
    Open Safari, click Safari menu > About Safari. Note the version number (e.g., 7.0.4, 6.1.4).
    Affected if Version is 7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, or 6.0.x through 6.1.4
  3. Check iOS version on iPhone/iPad
    Go to Settings > General > About. Note the Version (e.g., 7.1, 7.0.2).
    Affected if Version is 7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4, 7.0.5, 7.0.6, 7.1, or any version 7.1.1 or earlier
  4. Check Apple TV version
    Go to Settings > General > About Apple TV. Note the version (e.g., 6.1, 6.0.2).
    Affected if Version is 6.0, 6.0.1, 6.0.2, 6.1, or any version 6.1.1 or earlier
  5. Verify WebKit exposure in Safari
    In Safari, go to Safari > Settings > Security and check if Enable JavaScript is checked. This vulnerability is exploited through malicious web pages.
    Affected if JavaScript is enabled and the browser version falls within affected ranges above

If the product is Safari, iOS, or Apple TV and its version matches the affected ranges (Safari 6.0-7.0.4 or <=6.1.4, iOS <=7.1.1, Apple TV <=6.1.1) with JavaScript enabled, the environment is vulnerable to this WebKit flaw.

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

Apply vendor patches: update iOS to 7.1.2 or later, Safari to 6.1.5/7.0.5 or later, and Apple TV to 6.1.2 or later. As a temporary workaround, disable JavaScript in Safari settings.

Fix this in Safari Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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