dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2022-21465

MEDIUM · 6.7 CVSS v3.1 Published 2022-04-19
Fix available
A fix is available. Upgrade to 6.1.34 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). The supported version that is affected is Prior to 6.1.34. Easily exploitable vulnerability allows high 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 unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle VM VirtualBox as well as unauthorized update, insert or delete access to some of Oracle VM VirtualBox accessible data. CVSS 3.1 Base Score 6.7 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:L/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 · moderate confidence

Vulnerability in Oracle VM VirtualBox Core component affecting versions prior to 6.1.34. Allows a high-privileged attacker with local access to the infrastructure to cause a denial of service (complete crash or hang) and gain unauthorized update, insert, or delete access to some VirtualBox accessible data. The attack has low complexity and no user interaction required.

MitigationUpgrade Oracle VM VirtualBox to version 6.1.34 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:>= 6.1.0, < 6.1.34

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

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:N/I:L/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: check for VirtualBox in Programs and Features or look for C:\Program Files\Oracle\VirtualBox. On Linux: run 'dpkg -l | grep virtualbox' or 'rpm -qa | grep virtualbox'. On macOS: check /Applications for VirtualBox.app.
    Affected if VirtualBox is found on the system
  2. Determine installed VirtualBox version on Windows
    Open Command Prompt and run: 'C:\Program Files\Oracle\VirtualBox\VBoxManage.exe --version' or check the About section in VirtualBox GUI.
    Affected if Command fails or version cannot be determined (VirtualBox may not be fully installed)
  3. Determine installed VirtualBox version on Linux
    Run 'VBoxManage --version' in terminal.
    Affected if Command fails (VBoxManage not in PATH or VirtualBox not installed)
  4. Compare version against affected range
    Compare the installed version number to the vulnerable range: versions 6.1.0 through 6.1.33 are affected. Versions below 6.1.0 are not in scope, and version 6.1.34 and later are fixed.
    Affected if Installed version is 6.1.0, 6.1.1, 6.1.2, 6.1.3, 6.1.4, 6.1.5, 6.1.6, 6.1.7, 6.1.8, 6.1.9, 6.1.10, 6.1.11, 6.1.12, 6.1.13, 6.1.14, 6.1.15, 6.1.16, 6.1.17, 6.1.18, 6.1.19, 6.1.20, 6.1.21, 6.1.22, 6.1.23, 6.1.24, 6.1.25, 6.1.26, 6.1.27, 6.1.28, 6.1.29, 6.1.30, 6.1.31, 6.1.32, or 6.1.33

If VirtualBox version is 6.1.0 through 6.1.33, the environment is affected by this vulnerability; version 6.1.34 or later is not affected.

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 6.1.34 or later
Fixed in 6.1.34
Interim mitigation

Upgrade Oracle VM VirtualBox to version 6.1.34 or later to remediate this vulnerability.

Recommended fix High confidence

VirtualBox 6.1.34 or later

  1. Backup all VirtualBox virtual machine configurations and disk images
  2. Ensure all running virtual machines are powered off or saved
  3. Uninstall the current version of VirtualBox (versions 6.1.0 through 6.1.33)
  4. Download VirtualBox version 6.1.34 or later from the official Oracle website (www.oracle.com) or your distribution's package manager
  5. Install VirtualBox 6.1.34 or later following standard installation procedures
  6. Verify the installed version matches or exceeds 6.1.34
  7. Test that existing virtual machines start correctly after the upgrade
Caveat Minor version upgrades typically maintain VM compatibility but backup is recommended; some host OS kernel updates may require VirtualBox extension pack reinstallation

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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