How severe is CVE-2016-3479?

CVE-2016-3479 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2016-3479 being actively exploited?

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

What products are affected by CVE-2016-3479?

CVE-2016-3479 primarily affects Oracle Database. 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-3479?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2016-3479 published?

CVE-2016-3479 was published on 2016-07-21 and last updated on 2026-06-17.

CVE-2016-3479

CVE-2016-3479 is a high-severity vulnerability in Oracle Database with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 7.8
EPSS exploit prediction: 4% (89th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Oracle Database
Published: 2016-07-21
Last modified: 2026-06-17

Description

Unspecified vulnerability in the Portable Clusterware component in Oracle Database Server 11.2.0.4 and 12.1.0.2 allows remote attackers to affect availability via unknown vectors.

Frequently asked questions

What is CVE-2016-3479?: Unspecified vulnerability in the Portable Clusterware component in Oracle Database Server 11.2.0.4 and 12.1.0.2 allows remote attackers to affect availability via unknown vectors.
How severe is CVE-2016-3479?: CVE-2016-3479 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2016-3479 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (89th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-3479?: CVE-2016-3479 primarily affects Oracle Database. 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-3479?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2016-3479 published?: CVE-2016-3479 was published on 2016-07-21 and last updated on 2026-06-17.

References

Affected products (2)

cpe:2.3:a:oracle:database:11.2.0.4:*:*:*:*:*:*:*
cpe:2.3:a:oracle:database:12.1.0.2:*:*:*:*:*:*:*

More vulnerabilities in Oracle Database

CVE-2017-10202 — Critical (CVSS 9.9): Vulnerability in the OJVM component of Oracle Database Server. Supported versions that are affected are 11.2.0.4,…
CVE-2020-35169 — Critical (CVSS 9.1): Dell BSAFE Crypto-C Micro Edition, versions before 4.1.5, and Dell BSAFE Micro Edition Suite, versions before 4.5.2,…
CVE-2017-3310 — Critical (CVSS 9.0): Vulnerability in the OJVM component of Oracle Database Server. Supported versions that are affected are 11.2.0.4 and…
CVE-2016-3609 — Critical (CVSS 9.0): Unspecified vulnerability in the OJVM component in Oracle Database Server 11.2.0.4, 12.1.0.1, and 12.1.0.2 allows…
CVE-2016-3454 — Critical (CVSS 9.0): Unspecified vulnerability in the Java VM component in Oracle Database Server 11.2.0.4, 12.1.0.1, and 12.1.0.2 allows…
CVE-2008-1814 — Critical (CVSS 9.0): Unspecified vulnerability in the Oracle Secure Enterprise Search or Ultrasearch component in Oracle Database 9.0.1.5…

All CVEs affecting Oracle Database →