What is the severity of CVE-2020-2727?

CVE-2020-2727 has a high severity rating due to its ease of exploitation by privileged attackers.

How do I fix CVE-2020-2727?

To fix CVE-2020-2727, you should upgrade Oracle VM VirtualBox to version 5.2.36, 6.0.16, or 6.1.2 or later.

What versions of Oracle VM VirtualBox are affected by CVE-2020-2727?

Oracle VM VirtualBox versions prior to 5.2.36, 6.0.16, and 6.1.2 are affected by CVE-2020-2727.

Can CVE-2020-2727 be exploited remotely?

CVE-2020-2727 requires local access to the infrastructure, thus it is not remotely exploitable.

What component of Oracle VM VirtualBox is affected by CVE-2020-2727?

The Core component of Oracle VM VirtualBox is affected by CVE-2020-2727.

Vulnerability/
CVE-2020-2727

medium

15/1/2020

30/9/2024

CVE-2020-2727

First published: Wed Jan 15 2020(Updated: )

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 unauthorized access to critical data or complete access to all Oracle VM VirtualBox accessible data. CVSS 3.0 Base Score 6.0 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N).

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
Oracle VM VirtualBox	>=5.2.0<5.2.36
Oracle VM VirtualBox	>=6.0.0<6.0.16
Oracle VM VirtualBox	>=6.1.0<6.1.2

Remedy

https://www.oracle.com/security-alerts/cpujan2020.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2020-2727?
CVE-2020-2727 has a high severity rating due to its ease of exploitation by privileged attackers.
How do I fix CVE-2020-2727?
To fix CVE-2020-2727, you should upgrade Oracle VM VirtualBox to version 5.2.36, 6.0.16, or 6.1.2 or later.
What versions of Oracle VM VirtualBox are affected by CVE-2020-2727?
Oracle VM VirtualBox versions prior to 5.2.36, 6.0.16, and 6.1.2 are affected by CVE-2020-2727.
Can CVE-2020-2727 be exploited remotely?
CVE-2020-2727 requires local access to the infrastructure, thus it is not remotely exploitable.
What component of Oracle VM VirtualBox is affected by CVE-2020-2727?
The Core component of Oracle VM VirtualBox is affected by CVE-2020-2727.

collector/nvd-index
agent/type
agent/softwarecombine
agent/references
agent/author
agent/remedy
agent/severity
agent/first-publish-date
agent/tags
agent/event
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/source
vendor/oracle
canonical/oracle vm virtualbox
version/oracle vm virtualbox/5.2.0
version/oracle vm virtualbox/6.0.0
version/oracle vm virtualbox/6.1.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.