CVE-2016-5608
First published: Tue 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-5613.
Credit: secalert_us@oracle.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Oracle VM VirtualBox | >=5.0.0<5.0.28 | |
| Oracle VM VirtualBox | >=5.1.0<5.1.8 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2016-5608?
CVE-2016-5608 is classified as a medium severity vulnerability.
How do I fix CVE-2016-5608?
To mitigate CVE-2016-5608, upgrade Oracle VM VirtualBox to version 5.0.28 or later for 5.0.x versions, and 5.1.8 or later for 5.1.x versions.
Who is affected by CVE-2016-5608?
Local users of Oracle VM VirtualBox versions prior to 5.0.28 and 5.1.x prior to 5.1.8 are affected by CVE-2016-5608.
What type of attack does CVE-2016-5608 enable?
CVE-2016-5608 can allow local users to affect the availability of Oracle VM VirtualBox.
Is CVE-2016-5608 related to other vulnerabilities?
Yes, CVE-2016-5608 is noted as a different vulnerability than CVE-2016-5613.
- collector/nvd-index
- agent/references
- agent/type
- agent/softwarecombine
- agent/remedy
- agent/weakness
- agent/severity
- agent/author
- agent/tags
- agent/description
- agent/event
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- vendor/oracle
- canonical/oracle vm virtualbox
- version/oracle vm virtualbox/5.0.0
- version/oracle vm virtualbox/5.1.0