dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-21360

MEDIUM · 5.3 CVSS v3.1 Published 2022-01-19
Fix available
A fix is available. Upgrade to after 15.0.5 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Vulnerability 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 · high confidence

CVE-2022-21360 is a denial-of-service vulnerability in the ImageIO component of Oracle Java SE and Oracle GraalVM Enterprise Edition. An unauthenticated remote attacker can exploit this vulnerability by supplying specially crafted image data through network-accessible APIs or by tricking users into loading untrusted code (e.g., via Java Web Start or applets), causing the affected application to become partially unavailable.

MitigationApply the Oracle Critical Patch Update (CPU) containing the fix for CVE-2022-21360, upgrading to Java SE 8u321+, 11.0.13+, 17.0.1+, or later versions; for GraalVM, upgrade to 20.3.5+ or 21.3.1+. Validate and sanitize any image input processed through ImageIO APIs to further reduce attack surface.

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
Debian LinuxOperating system
Affected:= 9.0= 10.0= 11.0
OpenjdkApplication
Affected:>= 11, <= 11.0.13>= 13, <= 13.0.9>= 15, <= 15.0.5= 7= 8= 17= 17.0.1
GraalvmApplication
Affected:= 20.3.4= 21.3.0
JdkApplication
Affected:= 1.7.0= 1.8.0= 11.0.13= 17.0.1
JreApplication
Affected:= 1.7.0= 1.8.0= 11.0.13= 17.0.1
7 Mode Transition ToolApplication
Affected:all versions
Active Iq Unified ManagerApplication
Affected:all versions
Cloud Insights Acquisition UnitApplication
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Java version
    Run 'java -version' or 'java -fullversion' from command line to obtain the JRE/JDK version number
    Affected if The version matches Oracle JDK 1.7.0, 1.8.0, 11.0.13, or 17.0.1; Oracle JRE 1.7.0, 1.8.0, 11.0.13, or 17.0.1; Oracle OpenJDK 7, 8, 11.0.13 or earlier, 13.0.9 or earlier, 15.0.5 or earlier, 17, or 17.0.1; or Oracle GraalVM 20.3.4 or 21.3.0
  2. Identify installed OpenJDK flavor and version
    Check for 'java -version' output, or inspect /usr/lib/jvm/ directory on Linux systems, or check packaging system (dpkg -l | grep openjdk or rpm -qa | grep openjdk)
    Affected if The installed OpenJDK version matches any of the vulnerable versions listed in the affected ranges for Oracle OpenJDK
  3. Check if ImageIO is used by the application
    Search application code for imports of javax.imageio or java.imageio, and look for usage of ImageIO.read() or ImageIO.write() methods processing external input
    Affected if The application imports and uses ImageIO classes to process image data, particularly from untrusted sources
  4. Determine if application accepts image input from network or untrusted sources
    Review application configuration and network-exposed endpoints for image upload/processing functionality, or examine if the application runs Java Web Start or applets
    Affected if The application accepts image data from network-accessible APIs, file uploads, or runs untrusted code via Web Start or applets
  5. Verify Debian Linux Java packages if applicable
    On Debian systems, run 'dpkg -l | grep -i openjdk' or check installed java-*-jdk packages
    Affected if Running Debian 9.0, 10.0, or 11.0 with bundled OpenJDK packages matching vulnerable version ranges

You are affected if your environment runs any of the listed Oracle Java, OpenJDK, or GraalVM versions AND processes untrusted image data through the ImageIO component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 15.0.5
Interim mitigation

Apply the Oracle Critical Patch Update (CPU) containing the fix for CVE-2022-21360, upgrading to Java SE 8u321+, 11.0.13+, 17.0.1+, or later versions; for GraalVM, upgrade to 20.3.5+ or 21.3.1+. Validate and sanitize any image input processed through ImageIO APIs to further reduce attack surface.

Recommended fix High confidence

OpenJDK 11.0.14+/17.0.2+/8u321+/7u331+; Oracle Java SE 7u331/8u321/11.0.14/17.0.2; Oracle GraalVM 20.3.5/21.3.1

  1. Identify the installed Java version by running 'java -version' or checking package manager (dpkg -l | grep -i openjdk for Debian)
  2. For Debian-based systems: Run 'apt-get update && apt-get upgrade' to apply available security patches
  3. Alternatively, manually install the fixed OpenJDK packages: OpenJDK 11.0.14+, OpenJDK 17.0.2+, OpenJDK 8u321+, or OpenJDK 7u331+
  4. For Oracle Java SE: Upgrade to Oracle Java SE 7u331, 8u321, 11.0.14, or 17.0.2 (or later)
  5. For Oracle GraalVM Enterprise Edition: Upgrade to version 20.3.5 or 21.3.1 (or later)
  6. Verify the upgrade was successful by running 'java -version' and confirming the updated version number
  7. Restart any applications or services using the Java runtime to ensure they use the patched version
Caveat Major version upgrades (e.g., Java 8 to 11 or 17) may introduce breaking API changes; test applications thoroughly before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-21360 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-21360 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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