dbcve.org
Debian LinuxOperating system · Debian

CVE-2017-10102

CRITICAL · 9.0 CVSS v3.1 Published 2017-08-08
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
99/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
Vulnerability in the Java SE, Java SE Embedded component of Oracle Java SE (subcomponent: RMI). Supported versions that are affected are Java SE: 6u151, 7u141 and 8u131; Java SE Embedded: 8u131. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE, Java SE Embedded. While the vulnerability is in Java SE, Java SE Embedded, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Java SE, Java SE Embedded. Note: This vulnerability can only be exploited by supplying data to APIs in the specified Component without using Untrusted Java Web Start applications or Untrusted Java applets, such as through a web service. CVSS 3.0 Base Score 9.0 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H).

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

A detailed technical summary for this CVE is being prepared.

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
Debian LinuxOperating system
Affected:= 8.0= 9.0
SatelliteApplication
Affected:= 5.8
Enterprise Linux DesktopOperating system
Affected:= 6.0= 7.0
Enterprise Linux EusOperating system
Affected:= 7.3= 7.4= 7.5= 7.6= 7.7
Enterprise Linux ServerOperating system
Affected:= 6.0= 7.0
Enterprise Linux Server AusOperating system
Affected:= 7.3= 7.4= 7.6= 7.7
Enterprise Linux Server TusOperating system
Affected:= 7.3= 7.4= 7.6= 7.7
Enterprise Linux WorkstationOperating system
Affected:= 6.0= 7.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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

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 →
Recommended fix High confidence

Java SE 8u141 or later (or Java 9+/11+ for newer deployments)

  1. Identify the currently installed Java version by running 'java -version' or checking the installed packages (e.g., 'rpm -qa | grep java' on RHEL, 'dpkg -l | grep openjdk' on Debian)
  2. For Oracle Java SE: Download and install Java SE 8u141 or later, or Java SE 9 or later from Oracle's official JDK downloads
  3. For Red Hat Enterprise Linux systems: Run 'yum update java-1.8.0-openjdk' or 'yum update java-1.7.0-openjdk' to apply the latest available patched version from Red Hat's repositories
  4. For Debian systems: Run 'apt-get update && apt-get upgrade' or specifically 'apt-get install openjdk-8-jdk' to get the patched version
  5. Verify the update was successful by checking the Java version again: 'java -version'
  6. Ensure any applications or services relying on Java are restarted to load the updated JVM
Caveat Applications may have compatibility issues with newer Java versions; test thoroughly before production deployment. Java 7 reached end of life in 2015 - consider migrating to Java 8 LTS or later.

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

We can apply and verify the patch for your build — typical engagement from $2,300. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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