CVE-2022-21340
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: Libraries). 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 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 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 (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 · high confidenceThis is a denial of service vulnerability in the Java SE Libraries component. An unauthenticated remote attacker can exploit this vulnerability through network access to cause partial denial of service. The vulnerability affects Java deployments running sandboxed Web Start applications or applets that load untrusted code from the internet, or through APIs that use the affected Libraries 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= 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
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 versionRun 'java -version' or 'java -fullversion' from the command line to determine the exact Java version installedAffected if The version matches Oracle Jdk 1.7.0, 1.8.0, 11.0.13, or 17.0.1; Oracle Openjdk 7, 8, 11.0.13 or lower, 13.0.9 or lower, 15.0.5 or lower, 17, or 17.0.1; or Oracle Graalvm 20.3.4 or 21.3.0
-
Determine if Web Start or applets are in useCheck for Java Web Start (.jnlp files) or Java applet usage in the environment. Look for javaws command, browser plugins, or enterprise applications using legacy Java web deploymentAffected if Sandboxed Web Start applications or applets that load untrusted code from the internet are running or configured
-
Verify Java sandbox security configurationInspect the Java Control Panel security settings or java.policy files. Check if the security manager is enabled and review deployment.properties for sandbox settingsAffected if The Java security sandbox is not properly enforced or is configured to allow untrusted code execution
-
Check for NetApp product installationsFor NetApp products, identify which are installed: 7 Mode Transition Tool, Active IQ Unified Manager, or Cloud Insights Acquisition UnitAffected if Any of these NetApp products are running (all versions are affected)
-
Check Debian Linux Java packagesOn Debian systems, run 'dpkg -l | grep -i openjdk' or check /usr/lib/jvm/ for installed Java packagesAffected if Running Debian 9.0, 10.0, or 11.0 with OpenJDK packages installed
Your environment is affected if you are running any of the listed Java versions AND using Java Web Start, applets, or APIs that load untrusted code, or if you have any of the NetApp products installed.
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 Oracle Java SE update (7u321, 8u311, 11.0.13, 17.0.1 or later) or Oracle GraalVM Enterprise Edition update (20.3.4+, 21.3.0+) from the January 2022 Critical Patch Update. For Java deployments loading untrusted code, ensure the Java sandbox security model is enforced.
Oracle Java SE 8u321+/11.0.14+/17.0.2+; Oracle GraalVM Enterprise Edition 20.3.5+/21.3.1+; Debian OpenJDK latest security updates
- 1. Identify the exact Java/JDK version currently installed: java -version
- 2. For Oracle Java SE: upgrade to Java 8u321 or higher, Java 11.0.14 or higher, or Java 17.0.2 or higher
- 3. For Oracle GraalVM Enterprise Edition: upgrade to 20.3.5 or higher, or 21.3.1 or higher
- 4. For Debian OpenJDK packages: run 'apt-get update && apt-get upgrade openjdk-*' to install latest security patches
- 5. Verify the upgrade by running 'java -version' and confirming the new version number
- 6. Test any Java applications to ensure compatibility with the upgraded version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21340 — 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-21340 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