SafariWeb browser · Apple
CVE-2014-1303
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 · uneditedHeap-based buffer overflow in Apple Safari 7.0.2 allows remote attackers to execute arbitrary code and bypass a sandbox protection mechanism via unspecified vectors, as demonstrated by Liang Chen during a Pwn2Own competition at CanSecWest 2014.
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 confidenceHeap-based buffer overflow in Apple Safari 7.0.2 enables remote attackers to execute arbitrary code and bypass the browser's sandbox protection mechanism. The vulnerability was demonstrated by Liang Chen at Pwn2Own CanSecWest 2014, indicating active exploitation potential.
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.2CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 Safari versionOpen Safari, click Safari menu, select About Safari. Alternatively, run 'defaults read /Applications/Safari.app/Contents/Info CFBundleShortVersionString' in Terminal.Affected if The displayed version is exactly 7.0.2
-
Confirm macOS baselineCheck that the system is running a version of OS X that shipped with Safari 7.0.2 (typically OS X Mavericks 10.9.x). Run 'sw_vers' to verify the macOS version.Affected if Running an older macOS version that would have included Safari 7.0.2 as the bundled browser
-
Verify browser is in useConfirm that Safari is the active or configured browser for user web activity. Check browser usage in enterprise asset inventory if available.Affected if Safari 7.0.2 is actively used to browse web content, as the vulnerability is triggerable through malicious web pages
A user is affected if Safari version 7.0.2 is installed and actively used to render untrusted web content, as this specific version contains the heap overflow that enables remote code execution and sandbox bypass.
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.
dbcve · scopedApply the vendor-supplied security update for Safari or upgrade to a newer supported version. In enterprise environments, validate browser compatibility post-update before broad deployment.
Safari 7.0.3 or later (Apple Security Update 2014-001)
- 1. Open the App Store on macOS or check for Safari updates via Software Update
- 2. Update Safari to version 7.0.3 or later, which contains the security fix for CVE-2014-1303
- 3. Alternatively, apply the Apple security update (Safari 7.0.3) available through macOS Software Update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Safari
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1303 — 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-1303 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