dbcve.org
JdkApplication · Oracle

CVE-2015-4760

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 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 Oracle Java SE's 2D graphics subsystem affecting versions 6u95, 7u80, and 8u45. Allows remote attackers to achieve complete compromise (C/I/A) via unknown vectors in the 2D component, enabling remote code execution.

MitigationUpdate affected Java installations to patched versions. Oracle released CPU patches for this vulnerability in July 2015.

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

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 version
    Run 'java -version' or 'java -fullversion' from command line to obtain the exact version string including update number
    Affected if Version shows 1.6.0_95, 1.7.0_80, or 1.8.0_45 (or any 1.6.0_x, 1.7.0_x, or 1.8.0_x where x is between 0 and those specific update numbers if the vendor notation differs)
  2. Check if running JDK or JRE
    Run 'java -version' and look for 'Java(TM) SE Runtime Environment' (JRE) or 'Java SE Development Kit' (JDK) in the output
    Affected if Either JDK or JRE is installed with the vulnerable version range
  3. Verify Java 2D subsystem is in use
    Confirm Java application uses 2D graphics rendering - this is enabled by default in standard Java installations and used by any application performing graphical operations (AWT, Swing, Java2D)
    Affected if Java 2D component is present and active (default state in standard Java installations)
  4. Confirm exact update version number
    Run 'java -verbose:class' or check JAVA_HOME/lib/version.txt for precise update level, or use 'java -XshowSettings:all' to view full version details
    Affected if The update number matches 6u95, 7u80, or 8u45 specifically, or falls within unpatched versions prior to July 2015 CPU release

Environment is affected if Java JDK or JRE version is 1.6.0_95, 1.7.0_80, or 1.8.0_45 (or any unpatched version within the 1.6.x, 1.7.x, or 1.8.x family prior to July 2015 patches) with Java 2D component enabled.

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

Update affected Java installations to patched versions. Oracle released CPU patches for this vulnerability in July 2015.

Recommended fix High confidence

Java SE 8u301 or later (or Java SE 11/17/21 LTS for extended support)

  1. 1. Identify all systems running Java SE JDK or JRE versions 1.6.0, 1.7.0, or 1.8.0
  2. 2. Navigate to the Oracle Java SE download page: https://www.oracle.com/java/technologies/downloads/
  3. 3. Download the latest available Java SE 8 (or Java SE 11/17/21 LTS for longer support) for your operating system
  4. 4. Install the new Java version following the installation wizard prompts
  5. 5. Set the JAVA_HOME environment variable to point to the new installation directory
  6. 6. Update any application startup scripts or build configurations to reference the new Java path
  7. 7. Verify the installed version by running 'java -version' in a command terminal
  8. 8. Test all critical applications to ensure functionality remains intact
Caveat Minor - Some deprecated APIs may require updates; verify application compatibility in non-production environment before deployment

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

Fix this in Jdk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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