CVE-2022-21291
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 confidenceVulnerability in Oracle Java SE and GraalVM Enterprise Edition's Hotspot component allows unauthenticated remote attackers to perform unauthorized update, insert or delete operations on accessible data. The flaw impacts Java deployments running sandboxed Web Start applications or applets that load untrusted code from the internet, 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= 10.0= 11.0>= 11, <= 11.0.13>= 13, <= 13.0.9>= 15, <= 15.0.5= 17= 17.0.1= 34= 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 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 runtime versionRun 'java -version' or 'java -fullversion' to obtain the exact Java version. For Debian/Fedora, also check installed packages with 'dpkg -l | grep -i java' or 'rpm -qa | grep -i java'. For Oracle JDK/JRE, check the version from the installation directory.Affected if The version matches any of the affected ranges: Oracle JDK/JRE 1.7.0, 1.8.0, 11.0.13, 17.0.1; OpenJDK 11.0.13 or lower, 13.0.9 or lower, 15.0.5 or lower, 17 or 17.0.1; or GraalVM 20.3.4 or 21.3.0.
-
Check if Java Web Start is enabledLook for javaws binary: run 'which javaws' or check for Web Start in Java Control Panel under the Security tab. On Linux, check for /usr/bin/javaws or in the Java installation's bin directory.Affected if Web Start is installed and enabled, as the vulnerability specifically impacts sandboxed Web Start applications loading untrusted code from the internet.
-
Check for applet usage in running applicationsSearch deployment descriptors and application configurations for <applet> tags, or check if applications use the Java Applet API. Look in WAR/EAR files, web.xml, or application configuration files.Affected if Applications use Java applets that load untrusted code from the network, as this is one of the primary attack vectors for this vulnerability.
-
Identify if running Oracle GraalVMRun 'graalvm --version' or check for graalvm installation paths. On affected systems, check if the graalvm package is installed via system package manager.Affected if GraalVM Enterprise Edition version 20.3.4 or 21.3.0 is installed.
-
Check NetApp product installationsIdentify any NetApp 7-Mode Transition Tool or Active IQ Unified Manager installations. Use 'rpm -qa' or 'dpkg -l' to list installed NetApp packages, or check common installation directories.Affected if Any version of the NetApp products listed (7-Mode Transition Tool or Active IQ Unified Manager) is installed, as these include affected Java components.
You are affected if you have any Oracle Java SE, OpenJDK, or GraalVM installation matching the vulnerable versions AND your deployment runs sandboxed Web Start applications, applets loading untrusted code, or uses the affected Hotspot APIs.
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 Critical Patch Update January 2022 (or later) which includes the fix for this Hotspot vulnerability. Upgrade to Java SE 7u321+/8u311+/11.0.13+/17.0.1+ or GraalVM Enterprise Edition 20.3.4+/21.3.0+ as appropriate.
Oracle Java SE 7u331+/8u321+/11.0.14+/17.0.2+, Oracle GraalVM Enterprise Edition 20.3.5+/21.3.1+, or distribution-provided patched packages
- Identify the currently installed Java version using 'java -version'
- For Oracle Java SE: upgrade to Java SE 7 Update 331 or later, 8 Update 321 or later, 11.0.14 or later, or 17.0.2 or later
- For Oracle GraalVM Enterprise Edition: upgrade to 20.3.5 or later, or 21.3.1 or later
- On Debian/Ubuntu: run 'apt-get update && apt-get upgrade openjdk-*' or 'apt-get update && apt-get upgrade java-*'
- On Fedora: run 'dnf update java-*' or 'dnf upgrade'
- On systems using JDK/JRE packages: update to versions beyond 1.7.0_331, 1.8.0_321, 11.0.14, and 17.0.2
- Verify the upgrade by running 'java -version' and confirming the version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21291 — 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-21291 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