dbcve.org
JdkApplication · Oracle

CVE-2015-0460

HIGH · 9.3 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 allows remote attackers to affect confidentiality, integrity, and availability via unknown vectors related to Hotspot.

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

A critical unspecified vulnerability in the Oracle Java SE Hotspot component (JIT compiler) affecting versions 5.0u81, 6u91, 7u76, and 8u40 allows remote attackers to achieve complete compromise of confidentiality, integrity, and availability through unknown vectors. The high CVSS (9.3) indicates likely arbitrary code execution at the JVM level.

MitigationApply Oracle Critical Patch Update (CPU) for April 2015 or upgrade to a patched Java version beyond 8u40 to remediate this vulnerability.

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

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

AV:N/AC:M/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' from command line and note the full version string including update number (e.g., 1.8.0_40). On Windows, also check registry under HKLM\SOFTWARE\JavaSoft\Java Development Kit for CurrentVersion and Version keys.
    Affected if The version matches exactly 1.5.0_81, 1.6.0_91, 1.7.0_76, or 1.8.0_40 (or their JRE equivalents)
  2. Confirm Java vendor is Oracle
    Run 'java -verbose' or check the Java installation directory for Oracle branding. Oracle JDK/JRE is required; OpenJDK builds may have different patch status.
    Affected if The JRE/JDK is Oracle-produced (not OpenJDK, IBM J9, or other variants)
  3. Verify Hotspot JIT compiler is in use
    Run 'java -version -verbose' and look for 'HotSpot' in the output, or check the JVM library files in the JRE\bin\server directory for hotspotjvm.dll (Windows) or libjvm.so (Linux).
    Affected if The JVM implementation is Oracle Hotspot (the JIT compiler component specifically targeted by this CVE)
  4. Check for multiple Java installations
    On Windows, scan registry HKLM\SOFTWARE\JavaSoft\Java Development Kit and HKLM\SOFTWARE\JavaSoft\Java Runtime Environment for all entries. On Linux/Unix, run 'find /usr -name java -type f' and check all found installations.
    Affected if Any installed Oracle Java version matches the affected versions listed, regardless of whether it is the primary system Java

A system is affected if any Oracle JDK or JRE installation on the host matches versions 1.5.0_81, 1.6.0_91, 1.7.0_76, or 1.8.0_40 and uses the Hotspot JIT compiler.

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

Apply Oracle Critical Patch Update (CPU) for April 2015 or upgrade to a patched Java version beyond 8u40 to remediate this vulnerability.

Recommended fix High confidence

Java SE 5.0u81, 6u91, 7u76, or 8u40 (depending on major version line in use)

  1. 1. Identify the current Java version installed by running 'java -version' or 'javac -version'
  2. 2. For Java 1.5.0, upgrade to JDK/JRE 5.0u81 or later
  3. 3. For Java 1.6.0, upgrade to JDK/JRE 6u91 or later
  4. 4. For Java 1.7.0, upgrade to JDK/JRE 7u76 or later
  5. 5. For Java 1.8.0, upgrade to JDK/JRE 8u40 or later
  6. 6. Download the appropriate Java SE patch from Oracle's official Java SE download page (.oracle.com/java/technologies/downloads/)
  7. 7. Install the new Java version following standard installation procedures for your OS
  8. 8. Verify the installation by running 'java -version' and confirming it shows the patched version
Caveat Patches may include behavior changes; test critical application functionality after upgrading, especially for older Java versions

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
  • Testing8.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,680
Get help mitigating

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-0460 — 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-0460 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