CVE-2014-1300 json
Unspecified vulnerability in Apple Safari 7.0.2 on OS X allows remote attackers to execute arbitrary code with root privileges via unknown…
published 12y ago modified 4mo ago also EUVD-2014-1378
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.5%
- EPSS 5.5% chance of exploitation in 30 days, percentile 92%
- public exploits
- 0
- none known
Summary
Unspecified vulnerability in Apple Safari 7.0.2 on OS X allows remote attackers to execute arbitrary code with root privileges via unknown vectors, as demonstrated by Google during a Pwn4Fun competition at CanSecWest 2014.
Is CVE-2014-1300 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2014-1300 updated cvss 7.3
webkitgtk: arbitrary code execution with root privileges (WSA-2015-0001)
-
Red Hat Enterprise Linux 6 webkitgtk Red Hat Enterprise Linux 7 webkitgtk3, libwebkit2gtkaffected: no fix planned “Will not fix”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
5.51% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
References
-
archives.neohapsis.com
/archives/bugtraq/2014-04/0136.html
vendor-advisory
-
archives.neohapsis.com
/archives/bugtraq/2014-04/0135.html
vendor-advisory
-
archives.neohapsis.com
/archives/bugtraq/2014-04/0009.html
vendor-advisory
- twitter.com /thezdi/statuses/443796547872903168
- support.apple.com /kb/HT6537
- pwn2own.com /2014/03/pwn2own-results-for-wednesday-day-one/
Sources
- CVE List CVE-2014-1300
- NVD CVE-2014-1300
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.