# CVE-2022-21653: Hash collision in typelevel jawn

> Attackers can cause denial of service in applications using Jawn JSON parser via hash collision attacks if specific traits are not overridden.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Jan 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-vc89-hccf-rq55, UBUNTU-CVE-2022-21653, openSUSE-SU-2022:0011-1, openSUSE-SU-2022:0045-1, openSUSE-SU-2022:0106-1, openSUSE-SU-2024:11718-1

## What is CVE-2022-21653?

CVE-2022-21653 is a medium-severity denial of service vulnerability in typelevel jawn, published on 5 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jawn is an open source JSON parser. Extenders of the `org.typelevel.jawn.SimpleFacade` and `org.typelevel.jawn.MutableFacade` who don't override `objectContext()` are vulnerable to a hash collision attack which may result in a denial of service. Most applications do not implement these traits directly, but inherit from a library. `jawn-parser-1.3.1` fixes this issue and users are advised to upgrade. For users unable to upgrade override `objectContext()` to use a collision-safe collection.

Weakness: CWE-326 (Inadequate Encryption Strength), CWE-400 (Uncontrolled Resource Consumption)

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

36 open source packages ship an affected version, including org.typelevel:jawn-parser_0.25, org.typelevel:jawn-parser_0.27 and org.typelevel:jawn-parser_2.10. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.typelevel:jawn-parser_0.25` | Maven | All versions | None |
| `org.typelevel:jawn-parser_0.25` | Maven | All versions | None |
| `org.typelevel:jawn-parser_0.27` | Maven | All versions | None |
| `org.typelevel:jawn-parser_0.27` | Maven | All versions | None |
| `org.typelevel:jawn-parser_2.10` | Maven | All versions | None |
| `org.typelevel:jawn-parser_2.10` | Maven | All versions | None |
| `org.typelevel:jawn-parser_2.11` | Maven | All versions | None |
| `org.typelevel:jawn-parser_2.11` | Maven | All versions | None |
| `org.typelevel:jawn-parser_2.12` | Maven | All versions | 1.3.2 |
| `org.typelevel:jawn-parser_2.12` | Maven | All versions | 1.3.2 |
| `org.typelevel:jawn-parser_2.13` | Maven | All versions | 1.3.2 |
| `org.typelevel:jawn-parser_2.13` | Maven | All versions | 1.3.2 |
| `org.typelevel:jawn-parser_2.13.0-M5` | Maven | All versions | None |
| `org.typelevel:jawn-parser_2.13.0-M5` | Maven | All versions | None |
| `org.typelevel:jawn-parser_2.13.0-RC1` | Maven | All versions | None |
| `org.typelevel:jawn-parser_2.13.0-RC1` | Maven | All versions | None |
| `org.typelevel:jawn-parser_2.13.0-RC2` | Maven | All versions | None |
| `org.typelevel:jawn-parser_2.13.0-RC2` | Maven | All versions | None |
| `org.typelevel:jawn-parser_2.13.0-RC3` | Maven | All versions | None |
| `org.typelevel:jawn-parser_2.13.0-RC3` | Maven | All versions | None |
| `org.typelevel:jawn-parser_3` | Maven | All versions | 1.3.2 |
| `org.typelevel:jawn-parser_3` | Maven | All versions | 1.3.2 |
| `org.typelevel:jawn-parser_3.0.0-M1` | Maven | All versions | None |
| `org.typelevel:jawn-parser_3.0.0-M1` | Maven | All versions | None |
| `org.typelevel:jawn-parser_3.0.0-M2` | Maven | All versions | None |
| `org.typelevel:jawn-parser_3.0.0-M2` | Maven | All versions | None |
| `org.typelevel:jawn-parser_3.0.0-M3` | Maven | All versions | None |
| `org.typelevel:jawn-parser_3.0.0-M3` | Maven | All versions | None |
| `org.typelevel:jawn-parser_3.0.0-RC1` | Maven | All versions | None |
| `org.typelevel:jawn-parser_3.0.0-RC1` | Maven | All versions | None |
| `org.typelevel:jawn-parser_3.0.0-RC2` | Maven | All versions | None |
| `org.typelevel:jawn-parser_3.0.0-RC2` | Maven | All versions | None |
| `org.typelevel:jawn-parser_3.0.0-RC3` | Maven | All versions | None |
| `org.typelevel:jawn-parser_3.0.0-RC3` | Maven | All versions | None |
| `org.typelevel:jawn-parserg` | Maven | All versions | None |
| `org.typelevel:jawn-parserg` | Maven | All versions | None |
| `jawn` | SUSE:Package Hub 15 SP2 | All versions | 0.14.1-bp152.2.3.1 |
| `jawn` | SUSE:Package Hub 15 SP3 | All versions | 0.14.1-bp153.2.3.1 |
| `jawn` | openSUSE:Leap 15.3 | All versions | 0.14.1-3.3.1 |
| `jawn` | openSUSE:Leap 15.3 | All versions | 0.14.1-bp153.2.3.1 |

Products: Typelevel Jawn.

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

Upgrade to a fixed version.

## Is CVE-2022-21653 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-21653 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2022-21653 is a medium-severity denial of service vulnerability in typelevel jawn, published on 5 Jan 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-21653 exists.

Affected packages and fixed versions:
- org.typelevel:jawn-parser_0.25 (Maven): affected all versions; no fix listed
- org.typelevel:jawn-parser_0.25 (Maven): affected all versions; no fix listed
- org.typelevel:jawn-parser_0.27 (Maven): affected all versions; no fix listed
- org.typelevel:jawn-parser_0.27 (Maven): affected all versions; no fix listed
- org.typelevel:jawn-parser_2.10 (Maven): affected all versions; no fix listed
- org.typelevel:jawn-parser_2.10 (Maven): affected all versions; no fix listed
- org.typelevel:jawn-parser_2.11 (Maven): affected all versions; no fix listed
- org.typelevel:jawn-parser_2.11 (Maven): affected all versions; no fix listed
- org.typelevel:jawn-parser_2.12 (Maven): affected all versions; fixed in 1.3.2
- org.typelevel:jawn-parser_2.12 (Maven): affected all versions; fixed in 1.3.2
- org.typelevel:jawn-parser_2.13 (Maven): affected all versions; fixed in 1.3.2
- org.typelevel:jawn-parser_2.13 (Maven): affected all versions; fixed in 1.3.2

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

## Sources

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

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