dbcve.org
JdkApplication · Oracle

CVE-2015-4860

HIGH · 10.0 CVSS v2.0 Published 2015-10-21
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 6u101, 7u85, and 8u60, and Java SE Embedded 8u51, allows remote attackers to affect confidentiality, integrity, and availability via vectors related to RMI, a different vulnerability than CVE-2015-4883.

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 remote code execution vulnerability in Oracle Java SE's RMI (Remote Method Invocation) subsystem affecting versions 6u101, 7u85, 8u60 and Java SE Embedded 8u51. The CVSS 10 score indicates complete compromise of confidentiality, integrity, and availability via network-based attack.

MitigationApply Oracle Critical Patch Update (CPU) October 2015 or later to upgrade vulnerable Java installations to patched versions, or migrate to newer Java release families.

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' command or check system package manager (rpm -q java, dpkg -l | grep openjdk on Linux; wmic product get name,version on Windows)
    Affected if Version is 1.6.0 through 1.6.0.101, 1.7.0 through 1.7.0.85, or 1.8.0 through 1.8.0.60 (or any 1.6.0.x, 1.7.0.x, or 1.8.0.x before the respective update numbers that contain the fix)
  2. Determine if RMI is in use
    Inspect running processes for Java applications using RMI; check application logs for RMI registry activation; look for java.rmi.server.hostname or java.rmi.registry.port system properties in use
    Affected if Any Java application uses RMI server or RMI registry functionality
  3. Check RMI network exposure
    Scan for open ports typically used by RMI (default port 1099, or custom ports configured for RMI registry); verify if the RMI registry port is accessible from network
    Affected if RMI service port is listening and accessible from network while Java version is vulnerable

Environment is affected if running a vulnerable Java version (6u101, 7u85, 8u60 or earlier) AND the RMI subsystem is enabled or accessible on the system.

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) October 2015 or later to upgrade vulnerable Java installations to patched versions, or migrate to newer Java release families.

Recommended fix High confidence

Java 6u105+ / Java 7u91+ / Java 8u65+ (Oracle CPU October 2015)

  1. 1. Identify the currently installed Java version by running 'java -version' or 'javac -version'
  2. 2. For Java 6.x users: Upgrade to Java 6u105 or later from Oracle's Java SE Downloads page
  3. 3. For Java 7.x users: Upgrade to Java 7u91 or later from Oracle's Java SE Downloads page
  4. 4. For Java 8.x users: Upgrade to Java 8u65 or later from Oracle's Java SE Downloads page
  5. 5. After upgrade, verify the new version with 'java -version'
  6. 6. Ensure any applications using this Java installation are restarted
Caveat Major Java version upgrades may require testing for API compatibility; ensure applications are compatible with the target Java version before production deployment

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

Fix this in Jdk Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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