Skip to content
Fencer Vulns
high 7.9

CVE-2023-22100 json

Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core).

published 2023-10-17 3 y ago modified 2026-06-17 4 mo ago also EUVD-2023-26265

cvss
7.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 33%
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 7.0.12. 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 access to critical data or complete access to all Oracle VM VirtualBox accessible data and unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle VM VirtualBox. Note: Only applicable to 7.0.x platform. CVSS 3.1 Base Score 7.9 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:H).

Patch / fix

  • Oracle Corporation VM VirtualBox 7.0.12
  • virtualbox openSUSE Tumbleweed 7.0.12-1.1
  • virtualbox openSUSE Leap 15.5 7.0.12-lp155.2.13.1
  • virtualbox-kmp openSUSE Leap 15.5 7.0.12-lp155.2.13.1
  • virtualbox openSUSE Leap 15.4 7.0.12-lp154.2.43.1
  • virtualbox-kmp openSUSE Leap 15.4 7.0.12-lp154.2.43.1

opensuse advisories openSUSE-SU-2024:13355-1openSUSE-SU-2023:0352-1openSUSE-SU-2023:0351-1

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 7.9 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:H

Affected products

  • Oracle Corporation VM VirtualBox

References

Sources

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.