# CVE-2022-21449: Other in Java SE JDK and JRE

> Unauthenticated attackers can modify or delete critical data in Java SE and GraalVM via network access, requiring immediate upgrades.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 19 Apr 2022
- **Updated:** 24 Sep 2024
- **Also known as:** BIT-java-2022-21449, BIT-java-min-2022-21449, BIT-jre-2022-21449, CLEANSTART-2026-DF88370, DEBIAN-CVE-2022-21449, GHSA-cj8x-r9fp-q656, MINI-472m-m4gg-qxxm, MINI-4wpr-qx22-gc62, MINI-64gc-5v66-4p7m, MINI-66rg-g9j2-xg9j, MINI-r8hp-f9h5-mfjm, UBUNTU-CVE-2022-21449

## What is CVE-2022-21449?

CVE-2022-21449 is a high-severity vulnerability in Debian Debian Linux, published on 19 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Vulnerability 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: 17.0.2 and 18; Oracle GraalVM Enterprise Edition: 21.3.1 and 22.0.0.2. 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 creation, deletion or modification access to critical data or all 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 7.5 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N).

## Which versions are affected by CVE-2022-21449?

3 open source packages ship an affected version, including java, java-min and jre. It affects 16 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `java` | Bitnami | From 12.0.0 | 17.0.3, 18.0.1 |
| `java-min` | Bitnami | From 12.0.0 | 17.0.3, 18.0.1 |
| `jre` | Bitnami | From 12.0.0 | 17.0.3, 18.0.1 |

Products: Azul Zulu, Debian Debian Linux, Netapp 7-Mode Transition Tool, Netapp Active Iq Unified Manager, Netapp Cloud Insights, Netapp E-Series Santricity Os Controller, Netapp E-Series Santricity Storage Manager, Netapp E-Series Santricity Web Services, Netapp Hci Compute Node, Netapp Oncommand Insight, Netapp Oncommand Workflow Automation, Netapp Santricity Unified Manager, Netapp Solidfire\, Enterprise Sds \& Hci Storage Node, Netapp Solidfire \& Hci Management Node, Oracle Graalvm, Oracle Jdk.

## How do I fix CVE-2022-21449?

Upgrade java to a fixed version for your release line: 17.0.3 or 18.0.1.

## Is CVE-2022-21449 being exploited?

There is no known exploitation of CVE-2022-21449 in the wild and no public exploit code.

Public exploit code:

- CVE-2022-21449 Proof of Concept demonstrating its usage with a client running on a vulnerable Java version and a malicious TLS server (github_poc): https://github.com/notkmhn/CVE-2022-21449-TLS-PoC
- https://github.com/jfrog/jfrog-CVE-2022-21449 (github_poc): https://github.com/jfrog/jfrog-CVE-2022-21449
- Zeek script to detect exploitation attempts of CVE-2022-21449 targeting TLS clients (github_poc): https://github.com/thack1/CVE-2022-21449
- CVE-2022-21449 Vulnerability tester (github_poc): https://github.com/jmiettinen/CVE-2022-21449-vuln-test
- Reappear-CVE-2022-21449-TLS-PoC (github_poc): https://github.com/HeyMrSalt/AIS3-2024-Project-D5Team
- Professional JWT security testing toolkit. Analyze, crack, forge, and exploit JSON Web Tokens with 15+ vulnerability checks, 100k secret wordlist, and CVE-specific attacks (CVE-2022-21449, CVE-2018-0114). (github_poc): https://github.com/fevra-dev/ClaimJumper

## Other vulnerabilities in Debian Debian Linux

- [CVE-2022-21476](https://insights.sbomify.com/CVE-2022-21476/): Information disclosure in Java SE JDK and JRE (high 7.5)
- [CVE-2022-21541](https://insights.sbomify.com/CVE-2022-21541/): Other in Java SE JDK and JRE (medium 5.9)
- [CVE-2023-21830](https://insights.sbomify.com/CVE-2023-21830/): Deserialization in Java SE JDK and JRE (medium 5.3)
- [CVE-2023-21835](https://insights.sbomify.com/CVE-2023-21835/): Denial of service in Java SE JDK and JRE (medium 5.3)
- [CVE-2022-21618](https://insights.sbomify.com/CVE-2022-21618/): Auth bypass in Java SE JDK and JRE (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-21449 and fix it if it is affected.

What it is: CVE-2022-21449 is a high-severity vulnerability in Debian Debian Linux, published on 19 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-21449 in the wild and no public exploit code.

Affected packages and fixed versions:
- java (Bitnami): affected from 12.0.0; fixed in 17.0.3, 18.0.1
- java-min (Bitnami): affected from 12.0.0; fixed in 17.0.3, 18.0.1
- jre (Bitnami): affected from 12.0.0; fixed in 17.0.3, 18.0.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-21449/ (Markdown: https://insights.sbomify.com/CVE-2022-21449/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-21449
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-21449
- OSV: https://osv.dev/vulnerability/CVE-2022-21449

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-21449/
Summaries are generated and may contain mistakes; the official description above is the record.