Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 24 Mar 2022.
Ubuntu LinuxOperating system · Canonical

CVE-2015-2590

CRITICAL · 9.8 CVSS v3.1 Published 2015-07-16
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a critical severity vulnerability in Oracle Java SE's Libraries component affecting versions 6u95, 7u80, 8u45 and Java SE Embedded 7u75/8u33. The vulnerability allows remote unauthenticated attackers to achieve complete compromise of confidentiality, integrity, and availability. Due to the vague 'unspecified' disclosure, the exact technical root cause (buffer overflow, deserialization flaw, etc.) is not publicly detailed.

MitigationApply Oracle Critical Patch Update July 2015 or later which includes the fix for this vulnerability in the Libraries component. Upgrade to Java SE 8u45 or later, or 7u80 or later, or 6u95 or later as appropriate for your deployment.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Ubuntu LinuxOperating system
Affected:= 12.04= 14.04= 15.04
Debian LinuxOperating system
Affected:= 7.0= 8.0
SatelliteApplication
Affected:= 5.6= 5.7
Enterprise Linux DesktopOperating system
Affected:= 5.0= 6.0= 7.0
Enterprise Linux EusOperating system
Affected:= 6.6= 6.7= 7.1= 7.2= 7.3= 7.4= 7.5
Enterprise Linux For Ibm Z SystemsOperating system
Affected:= 6.0_s390x
Enterprise Linux For Ibm Z Systems EusOperating system
Affected:= 6.7_s390x= 7.1_s390x= 7.2_s390x= 7.3_s390x= 7.4_s390x= 7.5_s390x
Enterprise Linux For Power Big EndianOperating system
Affected:= 6.0_ppc64= 7.0_ppc64

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Java is installed
    Run 'java -version' or 'which java' to determine if Java is present on the system
    Affected if No Java installation found means this CVE does not apply directly, but Java may be installed in non-standard locations
  2. Identify installed Java version
    Run 'java -version 2>&1' and note the full version string (e.g., 1.6.0_95, 1.7.0_80, 1.8.0_45)
    Affected if Version matches 6u95 (1.6.0_95), 7u80 (1.7.0_80), or 8u45 (1.8.0_45) exactly, or falls within the range 6u95-6u, 7u75-7u80, or 8u33-8u45 for Embedded versions
  3. Check Java vendor and update channel
    Run 'java -verbose' or check package manager: 'dpkg -l | grep java' (Debian/Ubuntu) or 'rpm -qa | grep java' (Red Hat)
    Affected if Java originates from Oracle JDK/JRE or OpenJDK and version falls within affected ranges; note that some distributions backport fixes so compare against upstream Oracle version numbers
  4. Determine Java SE Embedded usage
    Check for embedded Java installations in paths like /usr/lib/jvm/ or application-specific Java installations; run 'find /opt -name java 2>/dev/null' or check application documentation for bundled Java
    Affected if Using Java SE Embedded versions 7u75 or 8u33 exactly, or versions between these points
  5. Verify patch status via vendor repositories
    Check system package repositories: 'apt-cache policy openjdk-7-jdk' (Ubuntu) or 'yum list java-1.7.0' (Red Hat) to see available patch versions
    Affected if No patched version is available from OS vendor and installed version matches affected ranges, or vendor has not released an update for this CVE

System is affected if Oracle Java SE 6u95, 7u80, or 8u45 (or Java SE Embedded 7u75/8u33) is installed, as the Libraries component vulnerability can be exploited via unknown vectors to achieve full compromise.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Interim mitigation

Apply Oracle Critical Patch Update July 2015 or later which includes the fix for this vulnerability in the Libraries component. Upgrade to Java SE 8u45 or later, or 7u80 or later, or 6u95 or later as appropriate for your deployment.

Recommended fix High confidence

OpenJDK 7u85+/OpenJDK 8u91+ or Oracle Java SE 7u85+/8u91+ (or the latest available patched version in your distribution's repositories)

  1. Identify the current Java installation: run 'java -version' to confirm the installed version and vendor (OpenJDK or Oracle JDK)
  2. For Debian/Ubuntu systems: run 'apt-get update && apt-get upgrade openjdk-7-jdk' or 'apt-get upgrade openjdk-8-jdk' to apply available security updates
  3. For RHEL-based systems: run 'yum update java-1.7.0-openjdk' or 'yum update java-1.8.0-openjdk' to fetch and apply the latest security patches
  4. Alternatively, explicitly upgrade to a patched version: on RHEL use 'yum install java-1.8.0-openjdk-1.8.0.91-1.b13.el7_2' or later (or the equivalent for your distribution)
  5. After upgrade, verify the new version is in use: run 'java -version' and confirm it shows version 8u91 or later (or the equivalent patched version for Java 7)
  6. Restart any running Java applications to ensure they use the updated Java runtime
Caveat Java 6 and 7 are end-of-life; consider upgrading to Java 8 LTS or newer. Applications may require recompilation or testing for compatibility with newer Java versions.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ubuntu Linux Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,288.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-2590 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-2590 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data