dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2024-21107

MEDIUM · 6.7 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to 7.0.16 or later.
See remediation →
69/100
Remediation priority · Elevated
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 high privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. Note: This vulnerability applies to Windows hosts only. CVSS 3.1 Base Score 6.7 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/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

A privilege escalation vulnerability exists in Oracle VM VirtualBox's core component on Windows hosts. The flaw allows a high-privileged attacker with local system access to escalate privileges and achieve full takeover of the VirtualBox environment. This affects all versions prior to 7.0.16.

MitigationUpgrade Oracle VM VirtualBox to version 7.0.16 or later to address this vulnerability. Since this affects Windows hosts only, prioritize patching Windows-based VirtualBox installations.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/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 on Windows
    Check for VirtualBox installation by looking for the VirtualBox program directory (typically C:\Program Files\Oracle\VirtualBox) or by running 'vboxmanage --version' in Command Prompt or PowerShell
    Affected if VirtualBox is installed on a Windows host system
  2. Determine installed VirtualBox version
    Run 'vboxmanage --version' from Command Prompt or PowerShell, or check the version listed in 'Add or Remove Programs' in the Windows Control Panel
    Affected if The displayed version number is lower than 7.0.16 (for example, 7.0.14, 7.0.10, 6.1.x, etc.)
  3. Confirm the host operating system is Windows
    Verify the host machine is running Windows. This vulnerability only affects VirtualBox on Windows hosts, not Linux or macOS hosts. Check via 'systeminfo' in Command Prompt or System Properties
    Affected if The host operating system is Windows and the VirtualBox version is below 7.0.16

You are affected if VirtualBox is installed on a Windows host and the installed version is any release earlier than 7.0.16, since the vulnerability allows privilege escalation from a high-privileged local account.

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. Since this affects Windows hosts only, prioritize patching Windows-based VirtualBox installations.

Recommended fix High confidence

VirtualBox 7.0.16

  1. 1. Back up all virtual machines and their configurations before upgrading.
  2. 2. Download VirtualBox version 7.0.16 or later from the official Oracle website (https://www.virtualbox.org/wiki/Downloads).
  3. 3. On the Windows host, close VirtualBox and ensure no VMs are running.
  4. 4. Run the VirtualBox installer and complete the upgrade installation.
  5. 5. After installation, launch VirtualBox and verify all existing VMs are listed correctly.
  6. 6. Test that VMs start and operate normally to confirm the upgrade was successful.
Caveat Oracle minor version updates typically do not introduce major breaking changes, but verify VM configurations and guest additions compatibility after upgrading.

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

Fix this in Vm Virtualbox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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