dbcve.org
OpenjdkApplication · Oracle

CVE-2020-2816

HIGH · 7.5 CVSS v3.1 Published 2020-04-15
Fix available
A fix is available. Upgrade to after 13.0.2 or later.
See remediation →
84/100
Remediation priority · High
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
Vulnerability in the Java SE product of Oracle Java SE (component: JSSE). Supported versions that are affected are Java SE: 11.0.6 and 14. Easily exploitable vulnerability allows unauthenticated attacker with network access via HTTPS to compromise Java SE. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Java SE accessible data. 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 7.5 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).

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 · high confidence

CVE-2020-2816 is a vulnerability in Oracle Java SE's JSSE (Java Secure Socket Extension) component affecting versions 11.0.6 and 14. The flaw allows an unauthenticated remote attacker via HTTPS to create, delete, or modify critical data. Exploitation occurs through direct API usage (e.g., web services) rather than through untrusted applets or Java Web Start applications.

MitigationUpgrade to a patched version of Java SE (11.0.7+ or 14.0.1+ or later) that addresses 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
OpenjdkApplication
Affected:>= 11, <= 11.0.6>= 13, <= 13.0.2= 7= 8= 14
Ubuntu LinuxOperating system
Affected:= 16.04= 18.04= 19.10
Debian LinuxOperating system
Affected:= 10.0
JdkApplication
Affected:= 11.0.6= 14.0.0
JreApplication
Affected:= 11.0.6= 14.0.0
7 Mode Transition ToolApplication
Affected:all versions
Active Iq Unified ManagerApplication
Affected:>= 7.3>= 9.5
Cloud BackupApplication
Affected:all versions

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 installed Java runtime
    Run 'java -version' or 'java -fullversion' to display the installed Java version information
    Affected if Java is not installed or version cannot be determined
  2. Verify Java vendor and exact version
    Run 'java -version 2>&1' and check the output for the exact version number (e.g., 11.0.6, 14.0.0, or 13.0.2) and vendor (Oracle JDK, Oracle JRE, or OpenJDK)
    Affected if The installed version matches Oracle JDK 11.0.6, Oracle JDK 14.0.0, Oracle JRE 11.0.6, Oracle JRE 14.0.0, OpenJDK 11.0.6, OpenJDK 13.0.2, or OpenJDK 14 (exact version from the affected ranges list)
  3. Check for JSSE/HTTPS usage
    Review application configurations, server logs, or network traffic to determine if the Java installation uses JSSE for HTTPS connections (common in web services, REST APIs, or SSL/TLS-enabled servers)
    Affected if Applications or services use Java-based HTTPS connections through the JSSE API; the vulnerability affects direct API usage via HTTPS, not browser-based applets

A user is affected if they have Oracle JDK, Oracle JRE, or OpenJDK at exactly versions 11.0.6, 13.0.2, or 14.0.0 and their Java applications use HTTPS connections via the JSSE component.

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
Upgrade available Upgrade to a release after 13.0.2
Interim mitigation

Upgrade to a patched version of Java SE (11.0.7+ or 14.0.1+ or later) that addresses this vulnerability.

Fix this in Openjdk 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 the upgrade done

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-2020-2816 — 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-2020-2816 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