CVE-2014-8370 json
VMware Workstation 10.x before 10.0.5, VMware Player 6.x before 6.0.5, VMware Fusion 6.x before 6.0.5, and VMware ESXi 5.0 through 5.5 allo…
published 11y ago modified 4mo ago also EUVD-2014-8207
- cvss
- 6.4
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.2%
- EPSS 4.2% chance of exploitation in 30 days, percentile 91%
- public exploits
- 0
- none known
Summary
VMware Workstation 10.x before 10.0.5, VMware Player 6.x before 6.0.5, VMware Fusion 6.x before 6.0.5, and VMware ESXi 5.0 through 5.5 allow host OS users to gain host OS privileges or cause a denial of service (arbitrary write to a file) by modifying a configuration file.
Patch / fix
Is CVE-2014-8370 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 FencerExploit prediction
4.19% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.4 | AV:N/AC:L/Au:N/C:N/I:P/A:P |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
- Technology feeds
References
-
vmware.com
/security/advisories/VMSA-2015-0001.html
patch, vendor-advisory
-
jvn.jp
/en/jp/JVN88252465/index.html
third-party-advisory, vdb-entry
-
securitytracker.com
/id/1031642
vdb-entry, third-party-advisory
-
jvndb.jvn.jp
/jvndb/JVNDB-2015-000007
third-party-advisory, vdb-entry
-
secunia.com
/advisories/62605
third-party-advisory
-
securityfocus.com
/bid/72338
vdb-entry, third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/100933
vdb-entry
-
secunia.com
/advisories/62551
third-party-advisory
-
securitytracker.com
/id/1031643
vdb-entry, third-party-advisory
-
secunia.com
/advisories/62669
third-party-advisory
Sources
- CVE List CVE-2014-8370
- NVD CVE-2014-8370
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.