CVE-2022-21305
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 Java SE, Oracle GraalVM Enterprise Edition product of Oracle Java SE (component: Hotspot). Supported versions that are affected are Oracle Java SE: 7u321, 8u311, 11.0.13, 17.0.1; Oracle GraalVM Enterprise Edition: 20.3.4 and 21.3.0. Easily exploitable vulnerability allows unauthenticated attacker with network access via multiple protocols to compromise Oracle Java SE, Oracle GraalVM Enterprise Edition. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of Oracle Java SE, Oracle GraalVM Enterprise Edition accessible data. 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 can also be exploited by using APIs in the specified Component, e.g., through a web service which supplies data to the APIs. CVSS 3.1 Base Score 5.3 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 confidenceA vulnerability in the Hotspot component of Oracle Java SE and GraalVM Enterprise Edition allows unauthenticated remote attackers to perform unauthorized update, insert, or delete operations on accessible data. The vulnerability is exploitable via network access through multiple protocols, with CVSS indicating low integrity impact but no confidentiality or availability impact. It primarily affects sandboxed Java Web Start applications, applets, or applications using affected APIs.
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= 9.0= 10.0= 11.0>= 11, <= 11.0.13>= 13, <= 13.0.9>= 15, <= 15.0.5= 7= 8= 17= 17.0.1= 20.3.4= 21.3.0= 1.7.0= 1.8.0= 11.0.13= 17.0.1= 1.7.0= 1.8.0= 11.0.13= 17.0.1all versionsall versionsall versionsCVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 installed Java or GraalVM versionRun 'java -version' or 'java -fullversion' to display the installed Java version. For GraalVM, run 'graalvm --version'. Record the exact version number shown.Affected if The version matches one of the affected versions: JDK/JRE 1.7.0, 1.8.0, 11.0.13, 17.0.1; OpenJDK 11.0.13 or earlier, 13.0.9 or earlier, 15.0.5 or earlier; GraalVM 20.3.4 or 21.3.0.
-
Confirm Hotspot JVM is in useRun 'java -version' and examine the output. The Hotspot JVM is identified by 'HotSpot' or 'OpenJDK' in the JVM description. This is the default JVM for Oracle JDK, OpenJDK, and most Oracle-provided Java distributions.Affected if The JVM implementation shown is Hotspot, as this vulnerability exists in the Hotspot component specifically.
-
Determine if Java Web Start or applets are enabledCheck Java Control Panel settings: on Windows, locate the Java configuration in Control Panel > Programs > Java. On Linux, check ~/.java/deployment/deployment.properties for 'deployment.web.start.enabled' and 'deployment.applet.enabled' settings.Affected if Java Web Start or applets are enabled (set to true), as the vulnerability primarily affects sandboxed applications using these features.
-
For NetApp products, verify product versionFor NetApp 7 Mode Transition Tool, Active IQ Unified Manager, or Cloud Insights Acquisition Unit, check the installed product version using 'product version' commands or the product's web interface under About or Settings.Affected if Any version of the listed NetApp products is installed, as the advisory states all versions are affected.
You are affected if you have Oracle Java, OpenJDK, or GraalVM matching the vulnerable versions AND the Hotspot JVM is in use, particularly with Web Start or applets enabled. For NetApp products, any version indicates exposure.
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.
dbcve · scopedApply the corresponding Oracle Java SE update (7u321, 8u311, 11.0.13, 17.0.1 or later) or GraalVM update (20.3.5+, 21.3.1+). For deployments running untrusted code, ensure the Java sandbox is properly configured and consider additional network segmentation.
Oracle Java SE 8u321+/11.0.14+/17.0.2+, Oracle GraalVM Enterprise Edition 20.3.5+/21.3.1+, or Debian OpenJDK security updates
- Identify the exact Java/JDK version currently installed by running 'java -version' or checking package manager
- For Oracle Java SE: upgrade to Oracle Java SE 8u321 or later, 11.0.14 or later, or 17.0.2 or later
- For Oracle GraalVM Enterprise Edition: upgrade to 20.3.5 or 21.3.1 or later
- For Debian systems with OpenJDK: run 'apt update && apt upgrade openjdk-*' to install the latest security patches
- For RHEL/CentOS systems: run 'yum update java-*' or 'dnf update java-*' to apply security updates
- Verify the upgrade was successful by running 'java -version' and confirming the new version number
- Restart any Java applications or services that were using the old version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21305 — 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-2022-21305 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