dbcve.org
SafariWeb browser · Apple

CVE-2014-1297

MEDIUM · 5.0 CVSS v2.0 Published 2014-04-02
Fix available
A fix is available. Upgrade to after 6.1.2 or later.
See remediation →
59/100
Remediation priority · Elevated
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 Safari before 6.1.3 and 7.x before 7.0.3, does not properly validate WebProcess IPC messages, which allows remote attackers to bypass a sandbox protection mechanism and read arbitrary files by leveraging WebProcess access.

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

This is a sandbox bypass vulnerability in WebKit (used by Apple Safari) where improper validation of WebProcess IPC messages allows remote attackers to read arbitrary files on the system by leveraging WebProcess access. The vulnerability affects Safari versions before 6.1.3 and 7.x before 7.0.3.

MitigationUpgrade Safari to version 6.1.3 or later, or 7.0.3 or later depending on the OS branch, to resolve the improper WebProcess IPC message validation.

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.2= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5= 6.1= 6.1.1= 7.0= 7.0.1= 7.0.2

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
Low
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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. Determine installed Safari version
    Open Safari, click Safari menu, select 'About Safari'. The version number displays in the window that opens.
    Affected if Version is 6.1.2 or lower, or 7.0.2 or lower (including 6.0.x through 6.1.x and 7.0 through 7.0.2)
  2. Confirm exact minor version
    In 'About Safari' window, note the full version string such as 6.1.1, 6.1.2, 7.0, 7.0.1, or 7.0.2.
    Affected if Version matches any of: 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.1, 6.1.1, 6.1.2, 7.0, 7.0.1, 7.0.2
  3. Verify WebKit WebProcess is in use
    This is the default for Safari. Confirm no third-party engine replacements are installed that bypass WebKit.
    Affected if Using Safari with default WebKit engine (the vulnerability exists in WebKit, not in Safari-specific code)

You are affected if Safari version is 6.1.2 or earlier, or 7.0.2 or earlier, as these versions contain the vulnerable WebKit IPC validation.

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

Upgrade Safari to version 6.1.3 or later, or 7.0.3 or later depending on the OS branch, to resolve the improper WebProcess IPC message validation.

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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