dbcve.org
JdkApplication · Oracle

CVE-2016-0475

MEDIUM · 5.8 CVSS v2.0 Published 2016-01-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
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 the Java SE, Java SE Embedded, and JRockit components in Oracle Java SE 8u66; Java SE Embedded 8u65; and JRockit R28.3.8 allows remote attackers to affect confidentiality and integrity via unknown vectors related to Libraries.

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

This is an unspecified vulnerability in Oracle Java SE 8u66, Java SE Embedded 8u65, and JRockit R28.3.8 affecting the Libraries component. The vulnerability allows remote attackers to impact confidentiality and integrity through unknown vectors. Oracle intentionally withheld specific technical details as part of their coordinated disclosure process.

MitigationApply the January 2016 Critical Patch Update from Oracle to obtain the fix for affected Java versions, or upgrade to a later supported Java version. Inventory all Java installations across the environment to ensure comprehensive patching.

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.8.0
JreApplication
Affected:= 1.8.0
JrockitApplication
Affected:= r28.3.8

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
Partial
Integrity
Partial
Availability
None

AV:N/AC:M/Au:N/C:P/I:P/A:N

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 Oracle JDK installation and version
    Run 'java -version' or check for java executable in JAVA_HOME/bin. On Windows, check registry or Program Files. On Linux, check /usr/lib/jvm/ or using 'which java' and 'java -version'
    Affected if The version output shows '1.8.0_66' or '8u66' exactly
  2. Identify Oracle JRE installation and version
    Run 'java -version' from JRE installation directory, or check common JRE locations: /usr/java/jre, /Library/Java/JavaVirtualMachines, or Windows Program Files. Look for jre folder under Oracle installations
    Affected if The version output shows '1.8.0_65' or '8u65' exactly
  3. Identify Oracle JRockit installation and version
    Check for JRockit installation directories: /opt/jrockit, /usr/lib/jvm/jrockit, or Oracle BEA folder. Run 'java -version' from JRockit bin directory, or check registry on Windows
    Affected if The version shows 'r28.3.8' exactly
  4. Gather all Java installations across the system
    Search for all java/javac executables on the system. On Linux: 'find / -name java -type f 2>/dev/null'. On Windows: check Program Files, Program Files (x86), and Oracle folders. Document each installation path and version
    Affected if Any of the found Java installations match the exact affected versions (8u66, 8u65, or r28.3.8)

You are affected if any Oracle JDK, JRE, or JRockit installation on your system reports exactly version 8u66, 8u65, or r28.3.8 respectively.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the January 2016 Critical Patch Update from Oracle to obtain the fix for affected Java versions, or upgrade to a later supported Java version. Inventory all Java installations across the environment to ensure comprehensive patching.

Fix this in Jdk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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