CVE-2016-5613: Medium severity oracle virtualbox vulnerability

Q: What is the severity of CVE-2016-5613?

CVE-2016-5613 has not been assigned a specific CVSS score, but it is classified as a local privilege escalation vulnerability affecting Oracle VM VirtualBox.

Q: How do I fix CVE-2016-5613?

To mitigate the effects of CVE-2016-5613, upgrade Oracle VM VirtualBox to version 5.0.28 or 5.1.8 or later.

Q: Who is affected by CVE-2016-5613?

Local users of Oracle VM VirtualBox prior to version 5.0.28 and 5.1.x before 5.1.8 are affected by CVE-2016-5613.

Q: What type of vectors are involved in CVE-2016-5613?

CVE-2016-5613 involves vectors related to the Core component of Oracle VM VirtualBox.

Q: Is CVE-2016-5613 related to any other vulnerabilities?

Yes, CVE-2016-5613 is mentioned as a different vulnerability than CVE-2016-5608.

Published Oct 25, 2016

Updated

Unspecified vulnerability in the Oracle VM VirtualBox component before 5.0.28 and 5.1.x before 5.1.8 in Oracle Virtualization allows local users to affect availability via vectors related to Core, a different vulnerability than CVE-2016-5608.

Affected Software

2 affected components

Oracle VM VirtualBox>=5.0.0<5.0.28

Oracle VM VirtualBox>=5.1.0<5.1.8

Remediation

Patch Available

http://www.oracle.com/technetwork/security-advisory/cpuoct2016-2881722.html

Event History

Oct 25, 2016

CVE Published

via MITRE·02:00 PM

Data Sourced

via MITRE·02:00 PM

Description

Frequently Asked Questions

What is the severity of CVE-2016-5613?

CVE-2016-5613 has not been assigned a specific CVSS score, but it is classified as a local privilege escalation vulnerability affecting Oracle VM VirtualBox.

How do I fix CVE-2016-5613?