What is the severity of CVE-2017-3561?

CVE-2017-3561 is considered easily exploitable and allows low privileged attackers access within the Oracle VM VirtualBox environment.

How do I fix CVE-2017-3561?

To fix CVE-2017-3561, upgrade Oracle VM VirtualBox to version 5.0.38 or later, or version 5.1.20 or later.

Which versions of Oracle VM VirtualBox are affected by CVE-2017-3561?

CVE-2017-3561 affects Oracle VM VirtualBox versions prior to 5.0.38 and prior to 5.1.20.

What type of attackers can exploit CVE-2017-3561?

CVE-2017-3561 can be exploited by low privileged attackers who have logon access to the infrastructure where Oracle VM VirtualBox is running.

Is there a workaround for CVE-2017-3561?

There is no specific workaround for CVE-2017-3561; the recommended action is to update to a fixed version.

Vulnerability/
CVE-2017-3561

high

8.8

24/4/2017

4/10/2024

CVE-2017-3561

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. Easily "exploitable" vulnerability allows low 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.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
Oracle VM VirtualBox	>=5.0.0<5.0.38
Oracle VM VirtualBox	>=5.1.0<5.1.20

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-3561?
CVE-2017-3561 is considered easily exploitable and allows low privileged attackers access within the Oracle VM VirtualBox environment.
How do I fix CVE-2017-3561?
To fix CVE-2017-3561, upgrade Oracle VM VirtualBox to version 5.0.38 or later, or version 5.1.20 or later.
Which versions of Oracle VM VirtualBox are affected by CVE-2017-3561?
CVE-2017-3561 affects Oracle VM VirtualBox versions prior to 5.0.38 and prior to 5.1.20.
What type of attackers can exploit CVE-2017-3561?
CVE-2017-3561 can be exploited by low privileged attackers who have logon access to the infrastructure where Oracle VM VirtualBox is running.
Is there a workaround for CVE-2017-3561?
There is no specific workaround for CVE-2017-3561; the recommended action is to update to a fixed version.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/author
agent/remedy
agent/description
agent/first-publish-date
agent/tags
agent/event
agent/source
vendor/oracle
canonical/oracle vm virtualbox
version/oracle vm virtualbox/5.0.0
version/oracle vm virtualbox/5.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.