Menu

Star on GitHub · 3.2k

CVE-2015-2625

2.6 · LOW

Unspecified vulnerability in Oracle Java SE 6u95, 7u80, and 8u45; JRockit R28.3.6; and Java SE Embedded 7u75 and 8u33 allows remote attackers to affect confidentiality via vectors related to JSSE.

Published Jul 16, 2015oracleEPSS 3.84%

Overview

CVE-2015-2625 is a low-severity vulnerability affecting oracle jdk. It was published on July 16, 2015 and has a CVSS 2.0 base score of 2.6 (LOW).

This vulnerability has a CVSS 2.0 base score of 2.6, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

Unspecified vulnerability in Oracle Java SE 6u95, 7u80, and 8u45; JRockit R28.3.6; and Java SE Embedded 7u75 and 8u33 allows remote attackers to affect confidentiality via vectors related to JSSE.

Remediation

Check the references section for vendor advisories and patches from oracle. Update jdk to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Affected products

VendorProductVersionsStatus

Frequently asked questions

What is CVE-2015-2625?

CVE-2015-2625 is a low-severity vulnerability affecting oracle jdk. It was published on July 16, 2015 and has a CVSS 2.0 base score of 2.6 (LOW).

How severe is CVE-2015-2625?

This vulnerability has a CVSS 2.0 base score of 2.6, rated LOW. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2015-2625?

Check the references section for vendor advisories and patches from oracle. Update jdk to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2015-2625?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2015-2625 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related LOW CVEs from 2015

View all