SafariWeb browser · Apple
CVE-2014-1325
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 · uneditedWebKit, 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 · high confidenceMemory corruption vulnerability in WebKit's rendering engine allows remote code execution or denial of service via maliciously crafted web pages. The vulnerability affects iOS Safari, Apple TV, and desktop Safari versions prior to the fixed releases.
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
= 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<= 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<= 6.1.1= 6.0= 6.0.1= 6.0.2= 6.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Apple product running WebKitDetermine if the device is running Apple Safari on macOS, Safari on iOS (iPhone/iPad), or Apple TV. Check the device type and operating system.Affected if The device runs any of the affected Apple products (Safari desktop, Safari iOS, or Apple TV)
-
Check Safari desktop version on macOSOpen Safari, click Safari in the menu bar, then select About Safari. The version number will display next to Safari.Affected if The version is 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.1.4, or any 7.0.x version (7.0, 7.0.1, 7.0.2, 7.0.3, 7.0.4)
-
Check iOS version on iPhone or iPadOpen Settings app, tap General, then tap About. Look for the Version field displaying the iOS version number.Affected if The 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, or any version 7.1.1 or earlier
-
Check Apple TV software versionOn Apple TV, go to Settings > General > About. The Version field shows the software version.Affected if The Apple TV version is 6.0, 6.0.1, 6.0.2, 6.1, or any version 6.1.1 or earlier
-
Verify WebKit is in useThis vulnerability exists in the WebKit rendering engine used by Safari. Confirm Safari is the browser in use (not an alternative like Chrome or Firefox).Affected if Safari is the browser and the version matches the affected ranges listed above
A user is affected if they are running Safari on macOS, iOS, or Apple TV with a version number matching the affected ranges, and they browse untrusted web pages.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patches by updating 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. Avoid browsing untrusted websites until updates are applied.
Fix this in Safari
Scoped from the published advisory
- Consultation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-1325 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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