dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2024-21112

HIGH · 8.8 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to 7.0.16 or later.
See remediation →
90/100
Remediation priority · Urgent
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are Prior to 7.0.16. 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 (scope change). Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 8.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Local privilege escalation vulnerability in Oracle VM VirtualBox Core component. A low-privileged user with logon access to the host infrastructure can exploit this to achieve takeover of VirtualBox, potentially affecting additional products due to scope change.

MitigationUpgrade Oracle VM VirtualBox to version 7.0.16 or later to address this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Vm VirtualboxApplication
Affected:< 7.0.16

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify VirtualBox is installed
    Check for VirtualBox installation directories and binaries. On Windows, look in C:\Program Files\Oracle\VirtualBox or C:\Program Files (x86)\Oracle\VirtualBox. On Linux, check /usr/lib/virtualbox or /opt/VirtualBox. Run command: ls -la /usr/lib/virtualbox/VBoxSVC or dir "C:\Program Files\Oracle\VirtualBox"
    Affected if VirtualBox binaries or directories are found on the system
  2. Determine installed VirtualBox version
    Run the VirtualBox version command. On Windows: "C:\Program Files\Oracle\VirtualBox\VBoxManage.exe" --version. On Linux: VBoxManage --version or /usr/lib/virtualbox/VBoxManage --version
    Affected if The version output shows a number lower than 7.0.16 (for example, 7.0.14, 7.0.10, 6.1.x, etc.)
  3. Confirm VirtualBox is actively used or configured
    Check if VirtualBox services or processes are present. On Windows: tasklist | findstr VBox or sc query vbox. On Linux: ps aux | grep -i vbox or systemctl list-unit-files | grep -i vbox
    Affected if VirtualBox services, processes, or configured VMs are found on the host

The system is affected if VirtualBox is installed with a version lower than 7.0.16 and the low-privileged user has logon access to the host where VirtualBox is installed or configured.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.0.16 or later
Fixed in 7.0.16
Interim mitigation

Upgrade Oracle VM VirtualBox to version 7.0.16 or later to address this vulnerability.

Recommended fix High confidence

7.0.16 (or latest 7.0.x stable release)

  1. Backup all existing virtual machines by exporting them or copying their virtual disk files to a safe location
  2. Download VirtualBox 7.0.16 (or the latest 7.0.x release) from the official Oracle website: https://www.oracle.com/virtualization/virtualbox/
  3. Uninstall the current VirtualBox version through the operating system's standard uninstall process
  4. Install VirtualBox 7.0.16 using the downloaded installer, accepting default options
  5. After installation, verify the version by opening VirtualBox and checking Help > About VirtualBox confirms version 7.0.16 or later
  6. Import any previously exported virtual machines or re-register VM disk files if needed
Caveat Point releases within the same major.minor branch typically have minimal breaking changes; review Oracle's VirtualBox 7.0.16 release notes for any specific compatibility notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vm Virtualbox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,840.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21112 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-21112 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data