CVE-2022-21271
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; 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 confidenceDenial of service vulnerability in Oracle Java SE and GraalVM Enterprise Edition's Libraries component. Easily exploitable via network without authentication, allowing attackers to cause partial service disruption by exploiting how the Libraries component handles certain API calls.
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= 12.2.1.3.0= 12.2.1.4.0= 20.3.4= 21.3.0= 1.7.0= 1.8.0= 11.0.13= 1.7.0= 1.8.0= 11.0.13= 8.8= 11all 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 runtimeRun 'java -version' or check for java binary in common paths (/usr/bin/java, /usr/java, etc.)Affected if No Java/JRE/JDK is installed, then the system is not affected by this specific Java vulnerability
-
Determine Oracle JDK/JRE versionRun 'java -version' and check the full version string (e.g., 1.8.0_321, 11.0.13)Affected if Version is 1.7.0, 1.8.0, or 11.0.13 specifically, or falls within the 1.7.x or 1.8.x families (older versions before the patches)
-
Determine Oracle GraalVM versionRun 'graalvm --version' or check for graalvm installation directory and version fileAffected if Version is exactly 20.3.4 or 21.3.0
-
Check Oracle HTTP Server versionConsult Oracle HTTP Server documentation or check opmnctl version output if OPMN is configuredAffected if Version is 12.2.1.3.0 or 12.2.1.4.0 (these bundle affected Java)
-
Check NetApp product Java bundlesFor NetApp 7 Mode Transition Tool or Active IQ Unified Manager, check the bundled JRE version within the product installationAffected if Any version of these NetApp products is installed (they bundle Java and are listed as affected for all versions)
A system is affected if it runs any of the listed Oracle JDK, JRE, GraalVM, HTTP Server versions, or any NetApp product that bundles a vulnerable Java version, and the Libraries component API is 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.
dbcve · scopedApply Oracle's January 2022 Critical Patch Update (CPU) for affected Java versions (7u321+, 8u311+, 11.0.13+) and GraalVM (20.3.5+, 21.3.1+). For deployments running untrusted code, ensure Java sandbox restrictions are properly enforced.
Oracle Java SE 8u321+/11.0.14+ or Oracle GraalVM Enterprise Edition 20.3.5/21.3.1
- 1. Identify the currently installed Java SE or GraalVM Enterprise Edition version using 'java -version' or checking the GraalVM installation
- 2. For Oracle Java SE: Download and install Java SE 8u321 or later (or 11.0.14 or later for Java 11) from Oracle's official JDK downloads
- 3. For Oracle GraalVM Enterprise Edition: Upgrade to version 20.3.5 or 21.3.1 from the Oracle GraalVM download page
- 4. Set the JAVA_HOME environment variable to point to the new installation directory
- 5. Update any build scripts, CI/CD pipelines, or deployment configurations that reference the old Java/GraalVM path
- 6. Verify the upgrade by running 'java -version' to confirm the new version is active
- 7. Test that dependent applications function correctly with the updated JVM
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21271 — 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-21271 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