dbcve.org
GraalvmApplication · Oracle

CVE-2020-14718

HIGH · 7.2 CVSS v3.1 Published 2020-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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 Oracle GraalVM Enterprise Edition product of Oracle GraalVM (component: JVMCI). Supported versions that are affected are 19.3.2 and 20.1.0. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in takeover of Oracle GraalVM Enterprise Edition. CVSS 3.1 Base Score 7.2 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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

Vulnerability in the JVMCI (JVM Compiler Interface) component of Oracle GraalVM Enterprise Edition versions 19.3.2 and 20.1.0 allows a high-privileged attacker with network access to achieve complete takeover of the affected system. The CVSS vector indicates low-complexity exploitation requiring high privileges but no user interaction, with impact to confidentiality, integrity, and availability.

MitigationApply Oracle's patched version of GraalVM Enterprise Edition from Oracle's Critical Patch Updates. If immediate patching is not possible, restrict network access to GraalVM services and limit the high-privileged accounts that can interact with the JVMCI component.

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
GraalvmApplication
Affected:= 19.3.2= 20.1.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
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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 if GraalVM Enterprise Edition is installed
    Run 'java -version' or check for GraalVM installation directory. On Linux/Unix check /usr/lib/jvm/ or $JAVA_HOME. On Windows check Program Files/Java or Oracle directories.
    Affected if GraalVM Enterprise Edition is found on the system
  2. Determine the exact GraalVM version
    Run 'java -version' to see the version string, or run 'graalvm-native-image --version' if available. The version will be displayed in the output.
    Affected if Version displayed is exactly 19.3.2 or 20.1.0 (note: other minor versions like 19.3.x may exist but are not listed as affected in this CVE)
  3. Verify the JVMCI component is accessible
    JVMCI is typically enabled by default in GraalVM for compiler functionality. Check if the JVMCI module is present by running 'java --list-modules' and look for 'jdk.vmci' in the output, or check for presence of JVMCI-related JAR files in the GraalVM installation directory.
    Affected if JVMCI module is present and loaded by the JVM
  4. Check if high-privileged network access to GraalVM services is possible
    Review network accessibility of GraalVM services and the account privileges of users who can interact with the JVMCI component. Check for exposed network listeners or remote management interfaces.
    Affected if Network access to GraalVM exists and the attacking account has high privileges on the system

The environment is affected only if GraalVM Enterprise Edition versions 19.3.2 or 20.1.0 are installed with JVMCI enabled and accessible to a high-privileged network attacker.

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 Oracle's patched version of GraalVM Enterprise Edition from Oracle's Critical Patch Updates. If immediate patching is not possible, restrict network access to GraalVM services and limit the high-privileged accounts that can interact with the JVMCI component.

Fix this in Graalvm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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