How severe is CVE-2016-0417?

CVE-2016-0417 has a CVSS 2.0 base score of 4.6, rated medium severity.

Is CVE-2016-0417 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (32nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2016-0417?

CVE-2016-0417 primarily affects Oracle Solaris Cluster. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2016-0417?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2016-0417 published?

CVE-2016-0417 was published on 2016-01-21 and last updated on 2026-06-17.

CVE-2016-0417

CVE-2016-0417 is a medium-severity vulnerability in Oracle Solaris Cluster with a CVSS 2.0 base score of 4.6. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: Medium (CVSS 2.0 base score 4.6)
EPSS exploit prediction: 0% (32nd percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Oracle Solaris Cluster
Published: 2016-01-21
Last modified: 2026-06-17

Description

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.

Frequently asked questions

What is CVE-2016-0417?: 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.
How severe is CVE-2016-0417?: CVE-2016-0417 has a CVSS 2.0 base score of 4.6, rated medium severity.
Is CVE-2016-0417 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (32nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-0417?: CVE-2016-0417 primarily affects Oracle Solaris Cluster. In total, 2 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2016-0417?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2016-0417 published?: CVE-2016-0417 was published on 2016-01-21 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:oracle:solaris_cluster:3.3:*:*:*:*:*:*:*
cpe:2.3:a:oracle:solaris_cluster:4.2:*:*:*:*:*:*:*

More vulnerabilities in Oracle Solaris Cluster

CVE-2019-17195 — Critical (CVSS 9.8): Connect2id Nimbus JOSE+JWT before v7.9 can throw various uncaught exceptions while parsing a JWT, which could result in…
CVE-2018-2930 — Critical (CVSS 9.8): Vulnerability in the Solaris Cluster component of Oracle Sun Systems Products Suite (subcomponent: NAS device…
CVE-2019-10086 — High (CVSS 7.3): In Apache Commons Beanutils 1.9.2, a special BeanIntrospector class was added which allows suppressing the ability for…
CVE-2017-3588 — High (CVSS 7.3): Vulnerability in the Solaris Cluster component of Oracle Sun Systems Products Suite (subcomponent: HA for MySQL).…
CVE-2017-10234 — High (CVSS 7.3): Vulnerability in the Solaris Cluster component of Oracle Sun Systems Products Suite (subcomponent: NAS device…
CVE-2018-2822 — Medium (CVSS 6.6): Vulnerability in the Solaris Cluster component of Oracle Sun Systems Products Suite (subcomponent: Cluster Geo). The…

All CVEs affecting Oracle Solaris Cluster →