dbcve.org
GraalvmApplication · Oracle

CVE-2023-21835

MEDIUM · 5.3 CVSS v3.1 Published 2023-01-18
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click Patch available

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 Enterprise Edition product of Oracle Java SE (component: JSSE). Supported versions that are affected are Oracle Java SE: 11.0.17, 17.0.5, 19.0.1; Oracle GraalVM Enterprise Edition: 20.3.8, 21.3.4 and 22.3.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via DTLS to compromise Oracle Java SE, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of Oracle Java SE, Oracle GraalVM Enterprise Edition. 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 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

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

A detailed technical summary for this CVE is being prepared.

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.8= 21.3.4= 22.3.0
JdkApplication
Affected:= 11.0.17= 17.0.5= 19.0.1
JreApplication
Affected:= 11.0.17= 17.0.5= 19.0.1
ZuluApplication
Affected:= 11.60= 13.52= 15.44= 17.38= 19.30

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
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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
Patch available Apply the vendor patch
Vendor patch www.oracle.com →
Recommended fix High confidence

Oracle Java SE 11.0.18+/17.0.6+/19.0.2+, Oracle GraalVM Enterprise Edition versions higher than 20.3.8/21.3.4/22.3.0, or Zulu OpenJDK 11.0.18+/17.0.6+/19.0.2+

  1. 1. Identify the exact Java/JDK/JRE or GraalVM version currently installed by running 'java -version' or checking the product documentation
  2. 2. For Oracle Java SE: upgrade to Java SE 11.0.18 or later, Java SE 17.0.6 or later, or Java SE 19.0.2 or later
  3. 3. For Oracle GraalVM Enterprise Edition: upgrade to a version higher than 20.3.8, 21.3.4, or 22.3.0 (refer to Oracle's January 2023 CPU for exact fixed versions)
  4. 4. For Zulu OpenJDK: upgrade to version 11.0.18+, 17.0.6+, or 19.0.2+ as applicable
  5. 5. Download the updated JDK/JRE from Oracle Technology Network, GraalVM downloads, or your vendor (Azul Systems for Zulu)
  6. 6. Install the new version and update JAVA_HOME path environment variable to point to the new installation
  7. 7. Restart any Java applications or services using the affected JVM
  8. 8. Verify the fix by confirming the new version is active: java -version
Caveat Java 19 reached end of life in September 2023 - consider upgrading to Java 17 LTS or Java 21 LTS for long-term support; verify application compatibility with the newer Java version before production deployment

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

We can apply and verify the patch for your build — typical engagement from $1,600. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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