CVE-2020-2682: High severity Oracle VM VirtualBox vulnerability
Vulnerability in the Oracle VM VirtualBox product of Oracle Virtualization (component: Core). Supported versions that are affected are Prior to 5.2.36, prior to 6.0.16 and prior to 6.1.2. 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. Successful attacks of this vulnerability can result in takeover of Oracle VM VirtualBox. CVSS 3.0 Base Score 8.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Oracle VM VirtualBox (Oracle Virtualization) - Coreto a version that resolves this vulnerability.Fixed in 5.2.36 - Upgrade
Upgrade
Oracle VM VirtualBox (Oracle Virtualization) - Coreto a version that resolves this vulnerability.Fixed in 6.0.16 - Upgrade
Upgrade
Oracle VM VirtualBox (Oracle Virtualization) - Coreto a version that resolves this vulnerability.Fixed in 6.1.2
Event History
Frequently Asked Questions
What is the severity of CVE-2020-2682?
CVE-2020-2682 is considered easily exploitable and allows high privileged attackers to compromise Oracle VM VirtualBox.
Which versions of Oracle VM VirtualBox are affected by CVE-2020-2682?
CVE-2020-2682 affects Oracle VM VirtualBox versions prior to 5.2.36, prior to 6.0.16, and prior to 6.1.2.
How do I fix CVE-2020-2682?
To fix CVE-2020-2682, upgrade Oracle VM VirtualBox to version 5.2.36 or later, 6.0.16 or later, or 6.1.2 or later.
What is the impact of exploiting CVE-2020-2682?
Exploiting CVE-2020-2682 can allow a high privileged attacker to gain control over the infrastructure hosting Oracle VM VirtualBox.
Is there a workaround for CVE-2020-2682?
Currently, the best remediation for CVE-2020-2682 is to apply the relevant software updates, as no specific workarounds are recommended.