CVE-2016-5501
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 confidentiality, integrity, and availability via vectors related to Core, a different vulnerability than CVE-2016-5538.
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-5501?
CVE-2016-5501 has a medium severity level, impacting confidentiality, integrity, and availability for local users.
How do I fix CVE-2016-5501?
To fix CVE-2016-5501, upgrade Oracle VM VirtualBox to version 5.0.28 or later or 5.1.8 or later.
Which versions of Oracle VM VirtualBox are affected by CVE-2016-5501?
CVE-2016-5501 affects Oracle VM VirtualBox versions prior to 5.0.28 and 5.1.x versions before 5.1.8.
What vectors allow exploitation of CVE-2016-5501?
CVE-2016-5501 can be exploited through unspecified vectors related to the Core component of Oracle VM VirtualBox.
Is CVE-2016-5501 more severe than CVE-2016-5538?
CVE-2016-5501 is considered a different vulnerability with distinct impacts compared to CVE-2016-5538.
- collector/nvd-index
- agent/type
- agent/remedy
- agent/author
- agent/references
- agent/severity
- agent/description
- agent/first-publish-date
- agent/softwarecombine
- agent/event
- agent/tags
- 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