CVE-2023-22001 json
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core).
published 2023-04-18 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-26166
- cvss
- 4.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 23%
- public exploits
- 0
- none known
Summary
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are Prior to 6.1.44 and Prior to 7.0.8. Easily exploitable vulnerability allows high 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 (scope change). Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle VM VirtualBox accessible data as well as unauthorized read access to a subset of Oracle VM VirtualBox accessible data. CVSS 3.1 Base Score 4.6 (Confidentiality and Integrity impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N).
Patch / fix
- Oracle Corporation VM VirtualBox 6.1.44, 7.0.8
- virtualbox openSUSE Tumbleweed 7.0.8-1.1
- virtualbox openSUSE Leap 15.4 7.0.8-lp154.2.32.2
- virtualbox-kmp openSUSE Leap 15.4 7.0.8-lp154.2.32.1
opensuse advisories openSUSE-SU-2024:12912-1openSUSE-SU-2023:0166-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 23% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.6 | CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N |
Affected products
- Oracle Corporation VM VirtualBox
References
-
oracle.com
/security-alerts/cpuapr2023.html
vendor-advisory
Sources
- CVE List CVE-2023-22001
- NVD CVE-2023-22001
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.