CVE-2020-2799
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 · uneditedVulnerability in the Oracle GraalVM Enterprise Edition product of Oracle GraalVM (component: GraalVM Compiler). Supported versions that are affected are 19.3.1 and 20.0.0. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise Oracle GraalVM Enterprise Edition. While the vulnerability is in Oracle GraalVM Enterprise Edition, attacks may significantly impact additional products. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle GraalVM Enterprise Edition accessible data. CVSS 3.0 Base Score 6.3 (Integrity impacts). CVSS Vector: (CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:C/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 confidenceVulnerability in the GraalVM Compiler component of Oracle GraalVM Enterprise Edition (versions 19.3.1 and 20.0.0) allows low-privileged attackers with network access to create, delete, or modify critical data. The high attack complexity and scope change (S:C) indicate the attack can impact additional products beyond the directly targeted GraalVM installation.
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= 19.3.1= 20.0.0CVSS 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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GraalVM installation and versionRun 'java -version' or 'graalvm --version' from the command line to display the installed GraalVM version information. Look for the version number in the output.Affected if The version shown is exactly 19.3.1 or exactly 20.0.0
-
Confirm GraalVM edition is EnterpriseCheck the version output for 'Enterprise Edition' or 'GraalVM Enterprise' designation. The CVE specifically affects the Enterprise Edition, not Community Edition.Affected if The installation is Oracle GraalVM Enterprise Edition (not Community Edition) and version is 19.3.1 or 20.0.0
-
Verify GraalVM Compiler component is presentCheck for the presence of the GraalVM compiler by examining the 'JAVA_HOME' directory structure or running 'ls $JAVA_HOME/lib/boot' or similar path containing compiler jars. The vulnerability is in the compiler component.Affected if The GraalVM Compiler component is installed and the version matches 19.3.1 or 20.0.0
-
Check network exposure of GraalVM servicesReview network configuration to determine if GraalVM-based applications or services are accessible over the network. The CVE requires network access for the low-privileged attacker.Affected if GraalVM compiler or GraalVM-based applications are network-accessible and running on an affected version
You are affected only if your environment runs Oracle GraalVM Enterprise Edition versions 19.3.1 or 20.0.0 specifically, with the GraalVM Compiler component present and network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the Oracle Critical Patch Update addressing CVE-2020-2799 or upgrade to a patched version of GraalVM Enterprise Edition beyond 20.0.0. Verify compiler functionality and test for regressions after applying the patch.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-2799 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-2799 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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