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

> An unauthenticated attacker can modify data in Java SE and GraalVM via JNDI, affecting applications running untrusted code or using specific APIs.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** CLEANSTART-2026-TP72880, CLEANSTART-2026-XX68441, DEBIAN-CVE-2022-21496, GHSA-ph68-gfg8-7cjx, UBUNTU-CVE-2022-21496

## What is CVE-2022-21496?

CVE-2022-21496 is a medium-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: JNDI). Supported versions that are affected are Oracle Java SE: 7u331, 8u321, 11.0.14, 17.0.2, 18; Oracle GraalVM Enterprise Edition: 20.3.5, 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 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).

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

It affects 16 products.


Products: Azul Zulu, Debian Debian Linux, Netapp Active Iq Unified Manager, Netapp Bootstrap Os, Netapp Cloud Insights Acquisition Unit, Netapp Cloud Secure Agent, Netapp E-Series Santricity Os Controller, Netapp E-Series Santricity Storage Manager, Netapp E-Series Santricity Web Services, Netapp Element Software, Netapp Hci Management Node, Netapp Oncommand Insight, Netapp Santricity Unified Manager, Netapp Solidfire, Oracle Graalvm, Oracle Java Se.

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

Apply the vendor's patch.

## Is CVE-2022-21496 being exploited?

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

## Other vulnerabilities in Debian Debian Linux

- [CVE-2022-21449](https://insights.sbomify.com/CVE-2022-21449/): Other in Java SE JDK and JRE (high 7.5)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21496 is a medium-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-21496 in the wild and no public exploit code.

Affected product: Debian Debian Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-21496/ (Markdown: https://insights.sbomify.com/CVE-2022-21496/index.md)
```

## Sources

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

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