SafariWeb browser · Apple
CVE-2014-1390
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 Safari before 6.1.6 and 7.x before 7.0.6, 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 HT6367.
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 confidenceThis is a memory corruption vulnerability in WebKit, the rendering engine used by Apple Safari. Remote attackers can exploit this by tricking users into visiting maliciously crafted websites, leading to arbitrary code execution or denial of service through memory corruption and application crashes. The vulnerability affects Safari versions before 6.1.6 and 7.x before 7.0.6.
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= 7.0.5<= 6.1.5= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4CVSS 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.
-
Confirm Safari is installedCheck if /Applications/Safari.app exists on the systemAffected if Safari.app is not present in /Applications - the product is not installed
-
Retrieve Safari version numberOpen Safari, then go to Safari > About Safari to display the version, or run: defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionStringAffected if Unable to determine version - Safari may be corrupted or inaccessible
-
Compare installed version to affected rangesCompare the retrieved version against: 6.0 through 6.1.5, or 7.0 through 7.0.5Affected if Version falls within 6.0-6.1.5 or 7.0-7.0.5 - the installed Safari is affected by this CVE
-
Verify WebKit component version (optional)Check Safari's installed components via Safari > Preferences > Advanced > Show Develop menu, then Develop > WebKit VersionAffected if WebKit version corresponds to affected Safari versions above
A system is affected if Safari is installed and its version is 6.0 through 6.1.5 or 7.0 through 7.0.5, as these versions contain the vulnerable WebKit component.
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 dataUpdate Safari to version 6.1.6 or later (for OS X 10.7/10.8) or 7.0.6 or later (for OS X 10.9). Since this is a client-side vulnerability exploited via web browsing, organizations should ensure endpoint patch management processes cover browser updates and consider deploying the update via MDM or patch management tools.
Fix this in Safari
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1390 — 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-1390 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