CVE-2017-3513: Low severity Oracle VM VirtualBox vulnerability
Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core). Supported versions that are affected are Prior to 5.0.38 and Prior to 5.1.20. Difficult to exploit 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 read access to a subset of Oracle VM VirtualBox accessible data. CVSS 3.0 Base Score 2.5 (Confidentiality impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:C/C:L/I:N/A:N).
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Oracle VM VirtualBox (Core)to a version that resolves this vulnerability.Fixed in 5.0.38 - Upgrade
Upgrade
Oracle VM VirtualBox (Core)to a version that resolves this vulnerability.Fixed in 5.1.20
Event History
Frequently Asked Questions
What is the severity of CVE-2017-3513?
CVE-2017-3513 has been rated as a difficult to exploit vulnerability that can be leveraged by a high-privileged attacker.
How do I fix CVE-2017-3513?
To fix CVE-2017-3513, upgrade Oracle VM VirtualBox to version 5.0.38 or later and 5.1.20 or later.
What components are affected by CVE-2017-3513?
CVE-2017-3513 affects the Oracle VM VirtualBox component of Oracle Virtualization, specifically versions prior to 5.0.38 and 5.1.20.
Is CVE-2017-3513 a remote vulnerability?
CVE-2017-3513 requires a high-privileged attacker with logon access to the infrastructure, thus it is not classified as a remote vulnerability.
What versions of Oracle VM VirtualBox are vulnerable to CVE-2017-3513?
Versions prior to Oracle VM VirtualBox 5.0.38 and 5.1.20 are vulnerable to CVE-2017-3513.