dbcve.org
JdkApplication · Oracle

CVE-2020-14664

HIGH · 8.3 CVSS v3.1 Published 2020-07-15
Fix available
A fix is available. Upgrade to after 11.70.2 or later.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges

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: JavaFX). The supported version that is affected is Java SE: 8u251. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Java SE. Successful attacks require human interaction from a person other than the attacker and while the vulnerability is in Java SE, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in takeover of Java SE. Note: This vulnerability applies to Java deployments, typically in clients running sandboxed Java Web Start applications or sandboxed Java applets, that load and run untrusted code (e.g., code that comes from the internet) and rely on the Java sandbox for security. This vulnerability does not apply to Java deployments, typically in servers, that load and run only trusted code (e.g., code installed by an administrator). CVSS 3.1 Base Score 8.3 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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 · high confidence

This is a JavaFX vulnerability in Java SE 8 (8u251) that allows unauthenticated attackers with network access to achieve sandbox escape and takeover Java SE. Exploitation is difficult as it requires human interaction and targets only client-side deployments running untrusted code (sandboxed Java Web Start applications or applets).

MitigationUpgrade Java SE to a patched version. This vulnerability only affects client-side deployments running untrusted code; server deployments running only trusted code are not impacted.

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
7 Mode Transition ToolApplication
Affected:all versions
Active Iq Unified ManagerApplication
Affected:>= 7.3>= 9.5
Cloud BackupApplication
Affected:all versions
Cloud Secure AgentApplication
Affected:all versions
E Series Performance AnalyzerApplication
Affected:all versions
E Series Santricity Os ControllerApplication
Affected:>= 11.0.0, <= 11.70.2

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
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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 Java SE 8 installation
    Run 'java -version' and 'java -fullversion' to check the installed Java version. On Windows, also check registry under HKLM\SOFTWARE\JavaSoft\Java Runtime Environment for version strings.
    Affected if The installed version is Java SE 8 (1.8.0_x) where x is any update version.
  2. Confirm JavaFX is loaded
    Run 'java -verbose:class' 2>&1 | grep -i javafx or inspect the jre\lib\ext directory for javafx*.jar files. JavaFX is typically bundled in Java 8 updates 191 and later, or as a separate module in earlier 8u versions.
    Affected if JavaFX runtime libraries are present and loaded by the JVM.
  3. Check for client-side deployment
    Inspect browser plugin settings and Java Control Panel (javacpl.exe). Look for 'Deploy' or 'Security' settings in the Java Control Panel. Check for any .jnlp (Java Web Start) or .jar files configured to run as applets in browsers.
    Affected if Java Web Start applications or browser applets are enabled or configured on the system.
  4. Verify sandbox configuration
    Review Java security policy files (java.policy in jre/lib/security) and the Java Control Panel security settings. Check if 'Enable Java content in the browser' is checked and security level is not set to 'Very High'.
    Affected if The Java sandbox is enabled for running untrusted code in browsers or via Java Web Start.
  5. Identify NetApp product installations
    If Java is installed as part of NetApp products (7 Mode Transition Tool, Active IQ Unified Manager, Cloud Backup, Cloud Secure Agent, or E Series), check the bundled JRE version within the product installation directories.
    Affected if Any of the listed NetApp products are installed and bundle an affected Java 8 version.

A system is affected only if it runs Java SE 8 (1.8.0) with JavaFX support AND has client-side deployments (browsers with Java plugin, Java Web Start) enabled for running untrusted code.

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 11.70.2
Interim mitigation

Upgrade Java SE to a patched version. This vulnerability only affects client-side deployments running untrusted code; server deployments running only trusted code are not impacted.

Fix this in Jdk Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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