dbcve.org
JdkApplication · Oracle

CVE-2015-0459

HIGH · 10.0 CVSS v2.0 Published 2015-04-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 5.0u81, 6u91, 7u76, and 8u40, and JavaFX 2.2.76, allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to 2D, a different vulnerability than CVE-2015-0491.

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

Critical-severity vulnerability in Oracle Java SE and JavaFX affecting the 2D graphics subsystem. The vulnerability is remotely exploitable and allows complete compromise of confidentiality, integrity, and availability. The specific attack vector and technical details are not disclosed in the advisory.

MitigationUpgrade to Java versions beyond 8u40 (such as 8u45+ or later JDK 8 releases) and apply subsequent Oracle Critical Patch Updates. For legacy systems requiring Java 5/6, consider migration to supported Java versions as these releases are end-of-life.

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.5.0= 1.6.0= 1.7.0= 1.8.0
JreApplication
Affected:= 1.5.0= 1.6.0= 1.7.0= 1.8.0
JavafxApplication
Affected:= 2.2.76
Suse Linux Enterprise DesktopOperating system
Affected:= 11.0
OpensuseOperating system
Affected:= 13.2

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. Identify installed Java JDK or JRE version
    Run 'java -version' or 'java -fullversion' from command line to obtain the exact version string
    Affected if Version matches 1.5.0, 1.6.0, 1.7.0, or 1.8.0 series (prior to 8u40) and the 2D graphics subsystem is in use
  2. Verify JavaFX version if installed
    Check for JavaFX runtime installation; on affected systems inspect the javafx runtime version via 'java -jar' or check installed packages
    Affected if JavaFX version is 2.2.76 or earlier and JavaFX 2D rendering is used
  3. Confirm 2D graphics subsystem usage
    Identify whether Java applications invoke java.awt.Graphics2D, Java2D API, or any 2D rendering operations; review application code or runtime behavior
    Affected if Any Java application rendering 2D graphics using the Java 2D API is potentially vulnerable
  4. Check OS package versions on Linux
    On SUSE Linux Enterprise Desktop 11.0 or openSUSE 13.2, query installed Java packages via package manager (zypper or rpm)
    Affected if System-installed Java packages are the affected Oracle JRE/JDK versions listed

The environment is affected if Oracle Java JDK/JRE versions 1.5.0 through 1.8.0 (prior to 8u40) or JavaFX 2.2.76 are installed AND the Java 2D graphics subsystem is being used by any running application.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Java versions beyond 8u40 (such as 8u45+ or later JDK 8 releases) and apply subsequent Oracle Critical Patch Updates. For legacy systems requiring Java 5/6, consider migration to supported Java versions as these releases are end-of-life.

Recommended fix High confidence

Java 5.0u85+/Java 6u95+/Java 7u80+/Java 8u45+ (or migrate to Java 11/17 LTS for long-term support)

  1. 1. Identify the currently installed Java version by running 'java -version' or 'javac -version'
  2. 2. For Java 5.0: Upgrade to Java 5.0u85 or later (contact Oracle for extended support if on Java 5)
  3. 3. For Java 6: Upgrade to Java 6u95 or later (contact Oracle for extended support if on Java 6)
  4. 4. For Java 7: Upgrade to Java 7u80 or later
  5. 5. For Java 8: Upgrade to Java 8u45 or later (Java 8 reached end of public updates in January 2019; consider migrating to newer LTS version like Java 11 or 17
  6. 6. For JavaFX 2.2: Upgrade to JavaFX 2.2.80 or later, or migrate to newer JavaFX versions
  7. 7. Download fixed versions from Oracle's official Java SE download page (https://www.oracle.com/java/technologies/downloads/)
  8. 8. Install the new Java version and update JAVA_HOME environment variable to point to the new installation
Caveat Java 5 and 6 are End-of-Life; Java 8 public updates ended January 2019 - consider migrating to Java 11 or 17 LTS for continued support; verify application compatibility with newer Java versions before upgrading

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

Fix this in Jdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0459 — 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-0459 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