What is the severity of CVE-2017-10236?

CVE-2017-10236 is classified as a high severity vulnerability due to its potential for exploitation by a high privileged attacker.

How do I fix CVE-2017-10236?

To mitigate CVE-2017-10236, upgrade Oracle VM VirtualBox to version 5.1.24 or later.

Who is affected by CVE-2017-10236?

CVE-2017-10236 affects installations of Oracle VM VirtualBox prior to version 5.1.24.

What type of attacks can exploit CVE-2017-10236?

CVE-2017-10236 can be exploited by an attacker with high privileges who has logged on to the infrastructure where Oracle VM VirtualBox runs.

Is CVE-2017-10236 still relevant?

While CVE-2017-10236 was relevant at the time of its discovery, it should be addressed by upgrading to secure versions to prevent potential exploitation.

Vulnerability/
CVE-2017-10236

high

7.3

8/8/2017

4/10/2024

CVE-2017-10236

First published: Tue Aug 08 2017(Updated: )

Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core). The supported version that is affected is Prior to 5.1.24. 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 ability to cause a hang or frequently repeatable crash (complete DOS) of Oracle VM VirtualBox as well as unauthorized update, insert or delete access to some of Oracle VM VirtualBox accessible data and unauthorized read access to a subset of Oracle VM VirtualBox accessible data. CVSS 3.0 Base Score 7.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:H).

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
Oracle VirtualBox	<=5.1.22

Remedy

http://www.oracle.com/technetwork/security-advisory/cpujul2017-3236622.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-10236?
CVE-2017-10236 is classified as a high severity vulnerability due to its potential for exploitation by a high privileged attacker.
How do I fix CVE-2017-10236?
To mitigate CVE-2017-10236, upgrade Oracle VM VirtualBox to version 5.1.24 or later.
Who is affected by CVE-2017-10236?
CVE-2017-10236 affects installations of Oracle VM VirtualBox prior to version 5.1.24.
What type of attacks can exploit CVE-2017-10236?
CVE-2017-10236 can be exploited by an attacker with high privileges who has logged on to the infrastructure where Oracle VM VirtualBox runs.
Is CVE-2017-10236 still relevant?
While CVE-2017-10236 was relevant at the time of its discovery, it should be addressed by upgrading to secure versions to prevent potential exploitation.

agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/author
agent/references
agent/last-modified-date
agent/severity
agent/remedy
agent/description
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/oracle
canonical/oracle virtualbox
version/oracle virtualbox/5.1.22

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.