CVE-2019-5515 json
VMware Workstation (15.x before 15.0.3, 14.x before 14.1.6) and Fusion (11.x before 11.0.3, 10.x before 10.1.6) updates address an out-of-b…
published 7y ago modified 4mo ago also EUVD-2019-15090
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.2%
- EPSS 4.2% chance of exploitation in 30 days, percentile 90%
- public exploits
- 0
- none known
Summary
VMware Workstation (15.x before 15.0.3, 14.x before 14.1.6) and Fusion (11.x before 11.0.3, 10.x before 10.1.6) updates address an out-of-bounds write vulnerability in the e1000 and e1000e virtual network adapters. Exploitation of this issue may lead to code execution on the host from the guest but it is more likely to result in a denial of service of the guest.
Patch / fix
- vmware fusion 10.1.6, 11.0.3
- vmware workstation 14.1.6, 15.0.3
Is CVE-2019-5515 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.16% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
Affected products
- VMware VMware Workstation and Fusion
Classification
- Weakness
-
- CWE-787 Out-of-bounds Write
- Technology feeds
References
-
vmware.com
/security/advisories/VMSA-2019-0005.html
vendor-advisory
-
zerodayinitiative.com
/advisories/ZDI-19-306/
third-party-advisory, vdb-entry
-
securityfocus.com
/bid/107634
vdb-entry, third-party-advisory
-
packetstormsecurity.com
/files/152290/VMware-Security-Advisory-2019-0005.html
third-party-advisory, vdb-entry
- zerodayinitiative.com /advisories/ZDI-19-516/
Sources
- CVE List CVE-2019-5515
- NVD CVE-2019-5515
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.