CVE-2022-21365
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: ImageIO). 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 · moderate confidenceCVE-2022-21365 is an ImageIO component vulnerability in Oracle Java SE (versions 7u321, 8u311, 11.0.13, 17.0.1) and Oracle GraalVM Enterprise Edition (20.3.4, 21.3.0). The flaw allows unauthenticated remote attackers to cause a partial denial of service via specially crafted image data processed through ImageIO APIs, typically exploitable through sandboxed Java Web Start applications or applets loading untrusted code from the internet.
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 Java installation and versionRun 'java -version' or 'java -fullversion' from command line to obtain the installed Java version stringAffected if The reported version matches any of the affected versions: 7u321, 8u311, 11.0.13, 17.0.1, or falls within the ranges >= 11 <= 11.0.13, >= 13 <= 13.0.9, >= 15 <= 15.0.5, or version 17 for Oracle OpenJDK; or versions 20.3.4, 21.3.0 for GraalVM; or 1.7.0, 1.8.0 for JDK/JRE
-
Confirm ImageIO component is accessibleVerify the Java installation includes the javax.imageio package by checking if ImageIO classes are available: 'java javax.imageio.ImageIO' or inspect the JAR file for imageio classesAffected if ImageIO classes are present in the Java installation and the version is among the affected versions
-
Determine if application processes untrusted image dataReview application code or configuration for usage of ImageIO read methods (ImageIO.read()) on data from untrusted sources such as network endpoints, user uploads, or web start/applet contextsAffected if The environment loads or processes image data from untrusted sources through ImageIO APIs, making it potentially exploitable
-
Check if running in sandboxed execution contextInspect Java security policy settings and determine if code is running in sandboxed mode via Web Start, applets, or restricted security manager configurationsAffected if The Java environment runs sandboxed code (Web Start applications or applets) loading untrusted images from the internet, which is the typical exploitation vector for this CVE
You are affected if your installed Java/JRE/JDK version matches the affected versions AND your application or sandboxed code processes untrusted image data through ImageIO 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's Critical Patch Update (CPU) for affected Java versions. For deployments using sandboxed code execution, ensure the Java sandbox security restrictions remain enforced and consider restricting network access to untrusted endpoints.
Oracle Java SE 8u321+/11.0.14+/17.0.2+, OpenJDK 11.0.14+/17.0.2+, or GraalVM Enterprise Edition 20.3.5+/21.3.1+
- 1. Identify the exact Java/OpenJDK version installed by running 'java -version' or 'openjdk-version'
- 2. For Oracle Java SE: upgrade to Java SE 7u331 or later, 8u321 or later, 11.0.14 or later, or 17.0.2 or later
- 3. For OpenJDK: upgrade to OpenJDK 11.0.14 or later, 13.0.10 or later, 15.0.6 or later, or 17.0.2 or later
- 4. For Oracle GraalVM Enterprise Edition: upgrade to 20.3.5 or later, or 21.3.1 or later
- 5. Verify the upgrade was successful by running 'java -version' and confirming the new version number
- 6. Test application functionality to ensure compatibility with the new Java version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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 $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-21365 — 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-21365 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