CVE-2016-0417
First published: Thu Jan 21 2016(Updated: )
Unspecified vulnerability in the Solaris Cluster component in Oracle Sun Systems Products Suite 3.3 and 4.2 allows local users to affect confidentiality, integrity, and availability via vectors related to HA for MySQL.
Credit: secalert_us@oracle.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Oracle Solaris Cluster | =3.3 | |
| Oracle Solaris Cluster | =4.2 |
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-0417?
The severity of CVE-2016-0417 is significant, as it can affect confidentiality, integrity, and availability for local users.
How do I fix CVE-2016-0417?
To fix CVE-2016-0417, users should update to a patched version of the Oracle Solaris Cluster software.
Who is affected by CVE-2016-0417?
CVE-2016-0417 affects local users of Oracle Solaris Cluster versions 3.3 and 4.2 in the Oracle Sun Systems Products Suite.
What impact does CVE-2016-0417 have?
CVE-2016-0417 can potentially allow local users to impact the confidentiality, integrity, and availability of the system.
Is CVE-2016-0417 still a threat?
The threat level of CVE-2016-0417 depends on the existence of unpatched systems running affected versions of Oracle Solaris Cluster.
- collector/nvd-index
- agent/type
- agent/references
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/severity
- agent/last-modified-date
- agent/description
- agent/event
- agent/tags
- agent/first-publish-date
- agent/source
- vendor/oracle
- canonical/oracle solaris cluster
- version/oracle solaris cluster/3.3
- version/oracle solaris cluster/4.2