dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2024-21109

MEDIUM · 5.9 CVSS v3.1 Published 2024-04-16
Fix available
A fix is available. Upgrade to 7.0.16 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges 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. Difficult to exploit vulnerability allows unauthenticated attacker with network access via HTTP to compromise Oracle VM VirtualBox. Successful attacks of this vulnerability can result in unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data. CVSS 3.1 Base Score 5.9 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N).

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 unauthenticated remote attackers with network access via HTTP to potentially access critical or all accessible data. The high attack complexity (AC:H) indicates the vulnerability is difficult but not impossible to exploit, with high confidentiality impact but no integrity or availability impact.

MitigationUpgrade Oracle VM VirtualBox to version 7.0.16 or later to remediate this vulnerability. Consider network segmentation to limit exposure if immediate upgrade is not feasible.

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

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

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 Oracle VM VirtualBox is installed
    On Windows, check Program Files\Oracle\VirtualBox or look for VirtualBox in Add/Remove Programs. On Linux, run 'dpkg -l | grep virtualbox' or 'rpm -qa | grep virtualbox'. On macOS, check /Applications for VirtualBox.app.
    Affected if VirtualBox is installed on the system
  2. Determine the installed VirtualBox version
    Run 'VBoxManage --version' from command line, or right-click VirtualBox in Windows and select About to view the version number.
    Affected if The version number is lower than 7.0.16 (e.g., 7.0.14, 7.0.10, 6.x.x)
  3. Verify VirtualBox HTTP server is accessible
    Check if the VirtualBox web service is enabled by reviewing VirtualBox preferences or configuration files. On systems with VRDE/VRDP or the VirtualBox web service (vboxwebsrv) running, check if port 18083 or other web service ports are listening with 'netstat -an | grep -E "18083|18084"'.
    Affected if The VirtualBox HTTP service is exposed and accessible over the network

You are affected if VirtualBox is installed and the installed version is lower than 7.0.16, particularly if the VirtualBox HTTP web service is network-accessible.

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. Consider network segmentation to limit exposure if immediate upgrade is not feasible.

Recommended fix High confidence

VirtualBox 7.0.16

  1. 1. Back up all existing virtual machines before upgrading VirtualBox.
  2. 2. Uninstall the current version of VirtualBox from the system.
  3. 3. Download VirtualBox version 7.0.16 or later from the official Oracle website (www.oracle.com).
  4. 4. Install the new VirtualBox version 7.0.16 using the downloaded installer.
  5. 5. After installation, verify the installed version by checking VirtualBox > Help > About VirtualBox.
  6. 6. Update Guest Additions in existing virtual machines if prompted or manually reinstall them for compatibility.
  7. 7. Test that existing VMs start correctly with the new VirtualBox version.
Caveat Minor: Virtual machine configuration format may be updated; backing up VMs before upgrade is recommended; guest additions should be reinstalled for full compatibility

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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