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.

Vulnerability/
CVE-2017-3513

low

2.5

24/4/2017

7/10/2024

CVE-2017-3513

First published: Mon Apr 24 2017(Updated: )

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).

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
Oracle VM VirtualBox	>=5.0.0<=5.0.36
Oracle VM VirtualBox	>=5.1.0<=5.1.18

Remedy

http://www.oracle.com/technetwork/security-advisory/cpuapr2017-3236618.html

Never miss a vulnerability like this again

Reference Links

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.

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

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.