What is the severity of CVE-2019-2850?

CVE-2019-2850 is considered to have a high severity level due to its easily exploitable nature allowing low privileged attackers.

How do I fix CVE-2019-2850?

To fix CVE-2019-2850, upgrade Oracle VM VirtualBox to version 5.2.32 or later, or 6.0.10 or later.

Which versions of Oracle VM VirtualBox are affected by CVE-2019-2850?

Versions prior to 5.2.32 and prior to 6.0.10 of Oracle VM VirtualBox are affected by CVE-2019-2850.

Can CVE-2019-2850 be exploited remotely?

No, CVE-2019-2850 requires local access to the infrastructure to be exploited.

What components of Oracle Virtualization are impacted by CVE-2019-2850?

CVE-2019-2850 impacts the Core component of Oracle VM VirtualBox.

Vulnerability/
CVE-2019-2850

low

2.8

23/7/2019

1/10/2024

CVE-2019-2850

First published: Tue Jul 23 2019(Updated: )

Vulnerability in the Oracle VM VirtualBox component of Oracle Virtualization (subcomponent: Core). Supported versions that are affected are Prior to 5.2.32 and prior to 6.0.10. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle VM VirtualBox executes to compromise Oracle VM VirtualBox. Successful attacks require human interaction from a person other than the attacker. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle VM VirtualBox. CVSS 3.0 Base Score 2.8 (Availability impacts). CVSS Vector: (CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L).

Credit: secalert_us@oracle.com

Affected Software	Affected Version	How to fix
Oracle VirtualBox	>=5.0.0<5.2.32
Oracle VirtualBox	>=6.0.0<6.0.10
SUSE Linux	=15.0
SUSE Linux	=15.1

Remedy

http://www.oracle.com/technetwork/security-advisory/cpujul2019-5072835.html

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2019-2850?
CVE-2019-2850 is considered to have a high severity level due to its easily exploitable nature allowing low privileged attackers.
How do I fix CVE-2019-2850?
To fix CVE-2019-2850, upgrade Oracle VM VirtualBox to version 5.2.32 or later, or 6.0.10 or later.
Which versions of Oracle VM VirtualBox are affected by CVE-2019-2850?
Versions prior to 5.2.32 and prior to 6.0.10 of Oracle VM VirtualBox are affected by CVE-2019-2850.
Can CVE-2019-2850 be exploited remotely?
No, CVE-2019-2850 requires local access to the infrastructure to be exploited.
What components of Oracle Virtualization are impacted by CVE-2019-2850?
CVE-2019-2850 impacts the Core component of Oracle VM VirtualBox.

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

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.