Skip to content
CTI Academy Sponsor CTI Academy
CRITICAL · CVSS 9.8 CISA Known Exploited Vulnerability

CVE-2015-2590

Oracle Java SE and Java SE Embedded Remote Code Execution Vulnerability

Oracle Java SE

Unspecified vulnerability in Oracle Java SE 6u95, 7u80, and 8u45, and Java SE Embedded 7u75 and 8u33 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Libraries, a different vulnerability than CVE-2015-4732.

CVSS
9.8
CRITICAL
EPSS
25.5%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
16 Jul 2015
NVD

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 3 March 2022. US federal agencies were required to remediate it by 24 March 2022.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 25.5%, which is higher than 98% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2015-2590 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2015-2590.

What does CVE-2015-2590 affect?

CVE-2015-2590 affects Oracle Java SE. Unspecified vulnerability in Oracle Java SE 6u95, 7u80, and 8u45, and Java SE Embedded 7u75 and 8u33 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Libraries, a different vulnerability than CVE-2015-4732.

How severe is CVE-2015-2590?

CVE-2015-2590 is rated CRITICAL with a CVSS base score of 9.8. EPSS puts the probability of exploitation in the next 30 days at 25.5%, higher than 98% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 24 March 2022.

How should organisations respond to CVE-2015-2590?

Apply the vendor patch for Oracle Java SE as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.