dbcve.org
JdkApplication · Oracle

CVE-2015-2638

HIGH · 10.0 CVSS v2.0 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
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; JavaFX 2.2.80; and Java SE Embedded 7u75 and 8u33 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D.

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

Unspecified vulnerability in the Java SE 2D graphics subsystem affecting versions 6u95, 7u80, 8u45, JavaFX 2.2.80, and Java SE Embedded 7u75/8u33. Allows remote attackers to achieve full compromise (confidentiality, integrity, availability) via unknown vectors in the 2D rendering code.

MitigationApply Oracle Critical Patch Update (CPU) for July 2015 or later which addresses this vulnerability; alternatively upgrade to a Java version beyond those listed as affected.

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
JdkApplication
Affected:= 1.6.0= 1.7.0= 1.8.0
JreApplication
Affected:= 1.6.0= 1.7.0= 1.8.0
JavafxApplication
Affected:= 2.2.80

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 (JRE/JDK) is installed
    Run 'java -version' in a command prompt or terminal. On Windows, also check for Java installations in C:\Program Files\Java\ or C:\Program Files (x86)\Java\
    Affected if No Java installation is found, then this CVE does not apply. If Java is installed, proceed to version check.
  2. Identify the exact Java version
    Run 'java -version' and note the full version string (for example: 1.8.0_45). Also run 'javac -version' if JDK is installed to confirm the JDK version.
    Affected if The installed version matches or falls within: 1.6.0 (any subversion up to 95), 1.7.0 (any subversion up to 80), or 1.8.0 (any subversion up to 45). Versions prior to these ranges are also potentially affected if they are older patch releases of 6u, 7u, or 8u.
  3. Confirm JavaFX installation and version (if applicable)
    Check for JavaFX runtime installations. On Windows, look in the Java installation directory for javafx runtime files, or run a JavaFX application and check its runtime version.
    Affected if JavaFX 2.2.80 is installed.
  4. Verify if Java 2D graphics subsystem is in use
    This vulnerability affects the Java 2D rendering code. Any Java application using AWT, Swing, or Java2D APIs exercises this code path. Check for running Java GUI applications or services that render graphical content.
    Affected if Any Java application that uses AWT, Swing, or Java2D graphics is potentially vulnerable. This includes most Java GUI applications and any code using java.awt.Graphics2D.

The environment is affected if Java JDK or JRE version 1.6.0 through the affected patch levels (6u95, 7u80, 8u45), or JavaFX 2.2.80 is installed and the system runs or serves Java applications that utilize the 2D graphics subsystem.

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 (CPU) for July 2015 or later which addresses this vulnerability; alternatively upgrade to a Java version beyond those listed as affected.

Recommended fix High confidence

Java SE 6u101+/Java SE 7u85+/Java SE 8u51+/JavaFX 8u60+ (or latest available stable release)

  1. 1. Identify all systems running vulnerable Java/JDK versions (1.6.0, 1.7.0, 1.8.0) or JavaFX 2.2.80
  2. 2. Download the latest Java SE or JavaFX release from Oracle's official website or your distribution's package repository
  3. 3. For Java SE 6u95: upgrade to Java SE 6u101 or later
  4. 4. For Java SE 7u80: upgrade to Java SE 7u85 or later
  5. 5. For Java SE 8u45: upgrade to Java SE 8u51 or later
  6. 6. For JavaFX 2.2.80: upgrade to JavaFX 8u60 or later
  7. 7. For Java SE Embedded: upgrade to 7u85 or 8u60 or later as applicable
  8. 8. Test application functionality with the new Java version in a staging environment
Caveat Minor compatibility issues may arise in legacy applications; thorough testing in staging is recommended before production deployment

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

Fix this in Jdk Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2638 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