Security advisory
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2022-2576
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 4 Nov 2026, 21:29 UTC · Revision 1
Source evidence
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.
osv:CVE-2022-2576
Complete source record
{
"id": "5f8320078cc5e4fab3791261916005f3c00cfb36e63d3f76d77d0e09cbbc8a15",
"url": "https://osv.dev/vulnerability/CVE-2022-2576",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "CVE-2022-2576",
"summary": "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.",
"evidence": "osv:CVE-2022-2576",
"products": [],
"severity": "unknown",
"structured": {
"id": "CVE-2022-2576",
"aliases": [
"CVE-2022-2576",
"GHSA-qq3j-44gw-cf6r"
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/eclipse-californium/californium",
"type": "GIT",
"events": [
{
"introduced": "15a27a972d7b4dd8d28d717cedfd01e6bf860e38"
},
{
"last_affected": "7eacd991054cff2cf741b6bf44c06bbe7b2d4c91"
},
{
"introduced": "bb400ca2b6eeffa4a1d1ec3005a7391625c4ee20"
},
{
"last_affected": "7ba3019079dcfb3484eeda7a23c5ede1b63ab48c"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:eclipse:californium:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "2.0.0"
},
{
"last_affected": "2.7.2"
}
],
"source": "CPE_RANGE"
},
{
"cpe": "cpe:2.3:a:eclipse:californium:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "3.0.0"
},
{
"last_affected": "3.5.0"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"3.5.0",
"2.7.2",
"3.4.0",
"2.7.1",
"3.3.0",
"3.2.0",
"3.1.0",
"2.7.0",
"2.6.6",
"3.0.0",
"2.6.5",
"2.6.4",
"2.6.3",
"2.6.2",
"2.6.1",
"2.6.0",
"2.5.0",
"2.4.0",
"2.3.0",
"2.3.0-RC2",
"2.3.0-RC1",
"2.2.0",
"2.2.0-RC1",
"2.1.0",
"2.1.0-RC2",
"2.1.0-RC1",
"2.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-2576.json"
}
}
],
"modified": "2026-10-28T02:30:39.666075296Z",
"provider": "osv",
"references": [
"https://bugs.eclipse.org/580018",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/2xxx/CVE-2022-2576.json",
"https://nvd.nist.gov/vuln/detail/CVE-2022-2576"
],
"provider_metadata": {
"cwe_ids": [
"CWE-408"
],
"cna_assigner": "eclipse",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"introduced": "2.0.0"
},
{
"last_affected": "2.7.2"
},
{
"introduced": "3.0.0"
},
{
"last_affected": "3.5.0"
}
],
"source": "AFFECTED_FIELD",
"strategy": "SplitRange"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/2xxx/CVE-2022-2576.json"
}
},
"related_cves": [
{
"value": "CVE-2022-2576",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 507280,
"published_at": "2022-07-29T13:20:10+00:00"
}