# CVE-2022-2576: Eclipse Californium denial of service (DoS) via Datagram Transport Layer Security (DTLS) handshake on parameter mismatch

> Attackers can cause denial of service via message amplification and high CPU load in Eclipse Californium when DTLS resumption verification is enabled.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/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:** 29 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-qq3j-44gw-cf6r

## What is CVE-2022-2576?

CVE-2022-2576 is a high-severity denial of service vulnerability in The Eclipse Foundation Eclipse Californium, published on 29 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Eclipse Californium version 2.0.0 to 2.7.2 and 3.0.0-3.5.0 a DTLS resumption handshake falls back to a DTLS full handshake on a parameter mismatch without using a HelloVerifyRequest. Especially, if used with certificate based cipher suites, that results in message amplification (DDoS other peers) and high CPU load (DoS own peer). The misbehavior occurs only with DTLS_VERIFY_PEERS_ON_RESUMPTION_THRESHOLD values larger than 0.

Weakness: CWE-408 (Incorrect Behavior Order: Early Amplification)

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

4 open source packages ship an affected version, including org.eclipse.californium:californium-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.eclipse.californium:californium-core` | Maven | From 2.0.0 | 2.7.3 |
| `org.eclipse.californium:californium-core` | Maven | From 2.0.0 | 2.7.3 |
| `org.eclipse.californium:californium-core` | Maven | From 3.0.0 | 3.6.0 |
| `org.eclipse.californium:californium-core` | Maven | From 3.0.0 | 3.6.0 |

Products: Eclipse Californium.

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

Upgrade org.eclipse.californium:californium-core to a fixed version for your release line: 2.7.3 or 3.6.0.

## Is CVE-2022-2576 being exploited?

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

## Other vulnerabilities in The Eclipse Foundation Eclipse Californium

- [CVE-2022-39368](https://insights.sbomify.com/CVE-2022-39368/): Californium Failing DTLS handshakes causes Data Loss due to throttling blocking processing of records (high 8.2)
- [CVE-2021-34433](https://insights.sbomify.com/CVE-2021-34433/): Auth bypass in Eclipse Californium (high 7.5)
- [CVE-2020-27222](https://insights.sbomify.com/CVE-2020-27222/): Denial of service in Eclipse Californium (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-2576 is a high-severity denial of service vulnerability in The Eclipse Foundation Eclipse Californium, published on 29 Jul 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-2576 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.eclipse.californium:californium-core (Maven): affected from 2.0.0; fixed in 2.7.3
- org.eclipse.californium:californium-core (Maven): affected from 2.0.0; fixed in 2.7.3
- org.eclipse.californium:californium-core (Maven): affected from 3.0.0; fixed in 3.6.0
- org.eclipse.californium:californium-core (Maven): affected from 3.0.0; fixed in 3.6.0

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

## Sources

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

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