dbcve.org
GraalvmApplication · Oracle

CVE-2024-20919

MEDIUM · 5.9 CVSS v3.1 Published 2024-02-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/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
Vulnerability in the Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Hotspot). Supported versions that are affected are Oracle Java SE: 8u391, 8u391-perf, 11.0.21, 17.0.9, 21.0.1; Oracle GraalVM for JDK: 17.0.9, 21.0.1; Oracle GraalVM Enterprise Edition: 20.3.12, 21.3.8 and 22.3.4. Difficult to exploit vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all Oracle Java SE, Oracle GraalVM for JDK, Oracle GraalVM Enterprise Edition 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.1 Base Score 5.9 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/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

A flaw in the Hotspot component of Oracle Java SE and GraalVM allows unauthenticated remote attackers with network access to achieve unauthorized creation, deletion, or modification of critical data through specific API calls without using untrusted Java Web Start or applets. The vulnerability has high integrity impact despite requiring difficult exploitation.

MitigationApply Oracle Critical Patch Updates for the affected Java SE and GraalVM versions (8u391+, 11.0.21+, 17.0.9+, 21.0.1+ for JDK; 20.3.12+, 21.3.8+, 22.3.4+ for GraalVM Enterprise Edition). Network access restriction may help limit exposure given the difficulty of exploitation.

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:= 20.3.12= 21.3.8= 22.3.4
Graalvm For JdkApplication
Affected:= 17.0.9= 21.0.1
JdkApplication
Affected:= 1.8.0= 11.0.21= 17.0.9= 21.0.1
JreApplication
Affected:= 1.8.0= 11.0.21= 17.0.9= 21.0.1

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

CVSS:3.1/AV:N/AC:H/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 JDK or JRE version
    Run 'java -version' or 'java -fullversion' from the command line to obtain the exact version string
    Affected if The version matches 1.8.0, 11.0.21, 17.0.9, or 21.0.1
  2. Identify installed GraalVM version
    Run 'java -version' or check the graalvm home directory for version files if GraalVM is installed
    Affected if The version matches 20.3.12, 21.3.8, 22.3.4, 17.0.9 (GraalVM for JDK), or 21.0.1 (GraalVM for JDK)
  3. Confirm Java Hotspot VM is in use
    Run 'java -version' and look for 'HotSpot' in the output, or run 'java -showversion' to see VM details
    Affected if The JVM implementation is Oracle Java Hotspot (this is the affected component)
  4. Verify network accessibility to the Java instance
    Review network binding configurations and firewall rules for systems running the affected Java version
    Affected if The Java application or service is network-accessible from untrusted sources (required for remote exploitation)
  5. Check for exposed Java API endpoints
    Review application configurations and running services that expose Java-level API calls to network
    Affected if The environment exposes Java APIs directly to network without authentication (required for the specific API call exploitation path)

A system is affected if it runs any of the exact Oracle JDK, JRE, or GraalVM versions listed (1.8.0, 11.0.21, 17.0.9, 21.0.1, 20.3.12, 21.3.8, 22.3.4) with Oracle Java Hotspot and has network-accessible Java APIs.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Oracle Critical Patch Updates for the affected Java SE and GraalVM versions (8u391+, 11.0.21+, 17.0.9+, 21.0.1+ for JDK; 20.3.12+, 21.3.8+, 22.3.4+ for GraalVM Enterprise Edition). Network access restriction may help limit exposure given the difficulty of exploitation.

Recommended fix Moderate confidence

Oracle Java SE 8u401+, 11.0.22+, 17.0.10+, 21.0.2+ / GraalVM for JDK 17.0.10+, 21.0.2+ / GraalVM Enterprise Edition 20.3.13+, 21.3.9+, 22.3.5+

  1. Identify the exact JDK/JRE/GraalVM version currently installed using 'java -version' or 'java -fullversion'
  2. For Oracle Java SE 8u391: upgrade to Oracle Java SE 8u401 or later
  3. For Oracle Java SE 11.0.21: upgrade to Oracle Java SE 11.0.22 or later
  4. For Oracle Java SE 17.0.9: upgrade to Oracle Java SE 17.0.10 or later
  5. For Oracle Java SE 21.0.1: upgrade to Oracle Java SE 21.0.2 or later
  6. For GraalVM for JDK 17.0.9: upgrade to GraalVM for JDK 17.0.10 or later
  7. For GraalVM for JDK 21.0.1: upgrade to GraalVM for JDK 21.0.2 or later
  8. For GraalVM Enterprise Edition 20.3.12: upgrade to 20.3.13 or later
Caveat Oracle Critical Patch Updates are generally backward-compatible but test your applications thoroughly; some deprecated APIs or behaviors may change

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Graalvm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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