SafariWeb browser · Apple
CVE-2014-1363
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 rendering engine allows remote attackers to execute arbitrary code or cause denial of service via a crafted website. Affected products include iOS < 7.1.2, Safari < 6.1.5/7.0.5, and Apple TV < 6.1.2.
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
<= 6.1.4= 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= 6.1.3= 7.0<= 6.1.1= 6.0= 6.0.1= 6.0.2= 6.1<= 7.1.1= 7.0= 7.0.1= 7.0.2= 7.0.3= 7.0.4= 7.0.5= 7.0.6= 7.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 productDetermine whether you are running Safari (on macOS), iOS (iPhone/iPad), or Apple TV. On macOS, check the application name. On iOS, go to Settings > General > About > Model. On Apple TV, check Settings > General > About > Apple TV.Affected if The device is running Safari, iOS, or Apple TV from the affected product list
-
Check Safari version on macOSOpen Safari, then go to Safari > About Safari. Note the version number displayed (e.g., 6.1.4, 7.0).Affected if Version is 6.0 through 6.1.4 inclusive, or exactly 7.0
-
Check iOS version on iPhone or iPadOpen Settings > General > About > Version. Note the version number (e.g., 7.1, 7.1.1).Affected if Version is 7.0 through 7.1.1 inclusive, or any version <= 7.1.1
-
Check Apple TV versionOn Apple TV, go to Settings > General > About > Version. Note the version number (e.g., 6.0.2, 6.1).Affected if Version is 6.0 through 6.1.1 inclusive, or any version <= 6.1.1
-
Confirm WebKit rendering is in useThis vulnerability is in the WebKit engine used by Safari, iOS Safari, and Apple TV web content. Ensure the Safari or web browser application is being used on the device.Affected if WebKit-based browser is actively in use on an affected version
You are affected if the installed version of Safari is 6.0 through 6.1.4 or exactly 7.0, iOS is 7.0 through 7.1.1, or Apple TV is 6.0 through 6.1.1.
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-supplied patches by updating iOS, Safari, and Apple TV to the specified versions or later. Consider network-level controls (web filtering, proxy) to block known malicious sites as an interim measure.
Fix this in Safari
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing2.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 $2,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1363 — 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-1363 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