dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2024-21263

MEDIUM · 6.1 CVSS v3.1 Published 2024-10-15
Fix available
A fix is available. Upgrade to after 7.1.2 or later.
See remediation →
63/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.22 and prior to 7.1.2. Easily exploitable vulnerability allows low 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 unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle VM VirtualBox and unauthorized read access to a subset of Oracle VM VirtualBox accessible data. CVSS 3.1 Base Score 6.1 (Confidentiality and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/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

Vulnerability in Oracle VM VirtualBox Core component allows a low-privileged user with local access to the host system to cause a denial of service (hang or crash) and gain unauthorized read access to a subset of VirtualBox accessible data. Affects versions prior to 7.0.22 and 7.1.2.

MitigationUpgrade Oracle VM VirtualBox to version 7.0.22 or 7.1.2 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.0, <= 7.0.22>= 7.1.0, <= 7.1.2

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
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/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: Look for VirtualBox in 'C:\Program Files\Oracle\VirtualBox' or check Registry under HKLM\SOFTWARE\Oracle\VirtualBox. On Linux: run 'dpkg -l | grep virtualbox' or 'rpm -qa | grep virtualbox'. On macOS: check /Applications for VirtualBox.app or run 'pkgutil --pkgs | grep -i virtualbox'.
    Affected if VirtualBox is present on the system
  2. Determine the installed VirtualBox version
    On Windows: Run 'VBoxManage --version' from the VirtualBox installation directory, or check the Version value in Registry key HKLM\SOFTWARE\Oracle\VirtualBox. On Linux: Run 'VBoxManage --version' in terminal. On macOS: Right-click VirtualBox.app > Get Info to see version, or run 'VBoxManage --version' via command line.
    Affected if Version command executes successfully and returns a version number
  3. Compare installed version against vulnerable ranges
    Parse the version number from the previous step. Check if it falls within 7.0.0 through 7.0.22 (inclusive) OR 7.1.0 through 7.1.2 (inclusive). Versions prior to 7.0.0 are not affected. Versions 7.0.23 and later, or 7.1.3 and later, are not affected.
    Affected if Version is 7.0.x where x is 22 or lower, OR version is 7.1.x where x is 2 or lower

A user is affected if VirtualBox is installed and the version number is 7.0.0-7.0.22 or 7.1.0-7.1.2, since the vulnerability requires a low-privileged local user to exploit the VirtualBox Core component.

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 a release after 7.1.2
Interim mitigation

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

Recommended fix High confidence

7.0.22 (for 7.0.x branch) or 7.1.2 (for 7.1.x branch) or later

  1. 1. Back up any critical virtual machines and VirtualBox configuration files
  2. 2. Visit the official Oracle VirtualBox download page: https://www.virtualbox.org/wiki/Downloads
  3. 3. For users on 7.0.x: Download VirtualBox version 7.0.22 or later
  4. 4. For users on 7.1.x: Download VirtualBox version 7.1.2 or later
  5. 5. Uninstall the current VirtualBox version following Oracle's uninstallation procedures
  6. 6. Install the downloaded fixed version
  7. 7. After installation, verify the installed version matches the fixed release (Help > About VirtualBox)
  8. 8. Test that existing VMs start correctly and that the VirtualBox service runs properly
Caveat Check VirtualBox release notes for any guest OS compatibility changes or new feature requirements before upgrading

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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