dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2024-21110

HIGH · 7.3 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to 7.0.16 or later.
See remediation →
73/100
Remediation priority · Elevated

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. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.1 Base Score 7.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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

Oracle VM VirtualBox versions prior to 7.0.16 contain a vulnerability in the Core component that allows a low-privileged user with local access to the host system to compromise VirtualBox through a attack requiring human interaction from another user. Successful exploitation grants the attacker complete control over the VirtualBox installation, including the ability to take over hosted virtual machines.

MitigationUpgrade Oracle VM VirtualBox to version 7.0.16 or later. Prior to updating, ensure all VMs are properly shut down and back up critical VM configurations and data.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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
    Check for VirtualBox installation by looking for the executable: on Windows, check 'C:\Program Files\Oracle\VirtualBox\VirtualBox.exe' exists; on Linux, run 'which VBoxManage' or check /usr/lib/virtualbox
    Affected if VirtualBox is not found on the system, then this CVE does not apply
  2. Determine installed VirtualBox version
    Run 'VBoxManage --version' from command line, or on Windows check the file properties of VirtualBox.exe, or on Linux check the package version with 'dpkg -l virtualbox' or 'rpm -q VirtualBox'
    Affected if The version shown is below 7.0.16 (for example 7.0.14, 7.0.10, 6.1.x, etc.)
  3. Confirm local user access exists
    Verify that untrusted or low-privileged users have local access to the host system by checking system user accounts and their privileges with 'who' or 'net user' on Windows, or 'users' or 'id' on Linux
    Affected if Low-privileged local users exist on the host machine and can log in interactively
  4. Check for active VirtualBox VMs or configurations
    Run 'VBoxManage list vms' and 'VBoxManage list runningvms' to see if any VMs are configured or running
    Affected if Any VMs are present, as the vulnerability allows taking control of hosted virtual machines

You are affected if VirtualBox is installed with a version lower than 7.0.16 and low-privileged local users have access to the host system.

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. Prior to updating, ensure all VMs are properly shut down and back up critical VM configurations and data.

Recommended fix High confidence

7.0.16

  1. Check current VirtualBox version by opening VirtualBox and going to Help > About, or running: VBoxManage --version
  2. Backup important VM data (export VMs or copy VM folder locations) as a precautionary measure before upgrading
  3. Download VirtualBox 7.0.16 from the official Oracle website (https://www.virtualbox.org/wiki/Downloads)
  4. Close VirtualBox and any running virtual machines
  5. Install the VirtualBox 7.0.16 update (on Windows, run the installer; on Linux, use your package manager or run the installation script)
  6. After installation, verify the version by running: VBoxManage --version (should show 7.0.16 or higher)
  7. Test that existing VMs start correctly
Caveat Point release upgrade typically preserves VM compatibility; however, always backup VMs before upgrading as a precaution

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

Fix this in Vm Virtualbox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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