Skip to content
Fencer Intel
high 7.5

CVE-2015-1916 json

Unspecified vulnerability in IBM Java 8 before SR1 allows remote attackers to cause a denial of service via unknown vectors related to SSL/…

published 11y ago modified 4mo ago also EUVD-2015-2021

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.7%
EPSS 2.7% chance of exploitation in 30 days, percentile 86%
public exploits
0
none known

Summary

Unspecified vulnerability in IBM Java 8 before SR1 allows remote attackers to cause a denial of service via unknown vectors related to SSL/TLS and the Secure Socket Extension provider.

Is CVE-2015-1916 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-1916 updated cvss 5.0

JDK: unspecified SSL/TLS server DoS

  • Red Hat Enterprise Linux 5 java-1.5.0-ibm, java-1.6.0-ibm, java-1.7.0-ibm Red Hat Enterprise Linux 6 java-1.5.0-ibm, java-1.6.0-ibm, java-1.7.1-ibm, java-1.5.0-ibm-src, java-1.6.0-ibm-src, java-1.7.1-ibm-src, +11 more Red Hat Enterprise Linux 7 java-1.7.1-ibm, java-1.7.1-ibm-src, java-1.7.1-ibm-demo, java-1.7.1-ibm-jdbc, java-1.7.1-ibm-plugin
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
5mo ago

Exploit prediction

2.70% chance of exploitation in the next 30 days, higher than 86% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.