dbcve.org
Vm VirtualboxApplication · Oracle

CVE-2020-2913

HIGH · 7.0 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to 6.0.20 / 6.1.6 or later.
See remediation →
72/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 6.0.20 and prior to 6.1.6. Difficult to exploit 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 takeover of Oracle VM VirtualBox. CVSS 3.0 Base Score 7.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:L/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

Vulnerability in Oracle VM VirtualBox core component allowing low privileged attacker with local logon access to compromise VirtualBox and potentially take over the virtualization platform. The difficult-to-exploit vulnerability affects versions prior to 6.0.20 and 6.1.6, enabling attacks via local access with high attack complexity.

MitigationUpgrade Oracle VM VirtualBox to version 6.0.20 or later, or 6.1.6 or later, depending on the major version line in use. Apply the appropriate patch as per Oracle's official documentation.

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.0.20>= 6.1.0, < 6.1.6
LeapOperating system
Affected:= 15.1

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

CVSS:3.1/AV:L/AC:H/PR:L/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. Check if VirtualBox is installed
    On Windows: open Command Prompt or PowerShell and run 'VBoxManage --version' or check Programs and Features. On Linux: run 'VBoxManage --version' or check package manager (dpkg -l | grep virtualbox, rpm -qa | grep VirtualBox)
    Affected if VirtualBox is not installed - the CVE does not apply
  2. Identify installed VirtualBox version
    Run 'VBoxManage --version' from command line. The output will be in format like '6.1.4r136709' where the first two numbers are the version (6.1.4)
    Affected if Version cannot be determined - manual inspection of installation required
  3. Compare version against affected ranges
    Parse the version number from step 2. Vulnerable versions are: < 6.0.20 (any 6.0.x before 6.0.20), and >= 6.1.0 but < 6.1.6 (any 6.1.x before 6.1.6). Safe versions are 6.0.20 and later in the 6.0 line, or 6.1.6 and later in the 6.1 line
    Affected if Installed version is 6.0.x before 6.0.20, OR 6.1.x before 6.1.6 - your environment is affected
  4. Check OpenSUSE Leap 15.1 package version (if applicable)
    If running OpenSUSE Leap 15.1, check VirtualBox package version via 'rpm -qa | grep -i virtualbox' or 'zypper info virtualbox'
    Affected if Running OpenSUSE Leap 15.1 with any VirtualBox package version - per advisory, this distribution is explicitly noted as affected

Your environment is affected if VirtualBox is installed and the version is either 6.0.x before 6.0.20, or 6.1.x before 6.1.6, or on OpenSUSE Leap 15.1 regardless of version.

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.

From vendor data
Upgrade available Upgrade to 6.0.20 / 6.1.6 or later
Fixed in 6.0.206.1.6
Interim mitigation

Upgrade Oracle VM VirtualBox to version 6.0.20 or later, or 6.1.6 or later, depending on the major version line in use. Apply the appropriate patch as per Oracle's official documentation.

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-2020-2913 — 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-2020-2913 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