CVE-2019-2656 json
Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core).
published 2019-04-23 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-12296
- cvss
- 8.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 44%
- public exploits
- 0
- none known
Summary
Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core). Supported versions that are affected are Prior to 5.2.28 and prior to 6.0.6. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. While the vulnerability is in Oracle VM VirtualBox, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.0 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).
Patch / fix
- Oracle Corporation VM VirtualBox 5.2.28, 6.0.6
- virtualbox openSUSE Tumbleweed 6.1.26-3.2
- virtualbox openSUSE Leap 15.1, openSUSE Leap 15.0 6.0.10-lp151.2.6.1
opensuse advisories openSUSE-SU-2024:11501-1openSUSE-SU-2019:1814-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.51% chance of exploitation in the next 30 days, higher than 44% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 8.8 | CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H |
| NVD | 2.0 | 4.6 | AV:L/AC:L/Au:N/C:P/I:P/A:P |
Affected products
- Oracle Corporation VM VirtualBox
References
-
oracle.com
/technetwork/security-advisory/cpuapr2019-5072813.html
patch, vendor-advisory
-
lists.opensuse.org
/opensuse-security-announce/2019-07/msg00056.html
vendor-advisory
Sources
- CVE List CVE-2019-2656
- NVD CVE-2019-2656
Fencer Vulns 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.