dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2024-21114

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

Oracle VM VirtualBox Core component vulnerability allows a low-privileged attacker with local access to the infrastructure to compromise VirtualBox and potentially take over the virtualization platform. The vulnerability affects versions prior to 7.0.16 and enables complete confidentiality, integrity, and availability compromise.

MitigationUpgrade Oracle VM VirtualBox to version 7.0.16 or later to remediate 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. Check if VirtualBox is installed
    On Windows: open Programs and Features or run 'vboxmanage --version' from Command Prompt. On Linux: run 'vboxmanage --version' or check for VirtualBox packages via package manager.
    Affected if VirtualBox is present on the system
  2. Determine installed VirtualBox version
    Run the command 'vboxmanage --version' from a terminal or command prompt. This displays the exact version number in format like 7.0.x.
    Affected if The version number returned is less than 7.0.16
  3. Verify version matches affected range
    Compare the installed version number to the affected range. Look for versions prior to 7.0.16, such as 7.0.14, 7.0.12, 7.0.10, 6.1.x, or 6.0.x.
    Affected if The installed version is any release prior to 7.0.16

You are affected if Oracle VM VirtualBox is installed and its version is lower than 7.0.16.

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 remediate this vulnerability.

Recommended fix High confidence

VirtualBox 7.0.16

  1. 1. Check current VirtualBox version by opening VirtualBox and navigating to Help > About, or running `vboxmanage --version`
  2. 2. Download VirtualBox 7.0.16 or later from the official Oracle website (https://www.virtualbox.org/wiki/Downloads)
  3. 3. Install the updated VirtualBox version by running the downloaded installer
  4. 4. After installation, verify the version by checking Help > About or running `vboxmanage --version` to confirm the update was successful
  5. 5. Restart any running virtual machines if necessary to ensure full functionality with the updated installation
Caveat Point release upgrades typically preserve VM configurations and settings; however, it is recommended to back up important VM images before updating

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
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-21114 — 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-21114 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