Skip to content

Eclipse Californium denial of service (DoS) via Datagram Transport Layer Security (DTLS) handshake on parameter mismatch

High severity GitHub Reviewed Published Jul 30, 2022 to the GitHub Advisory Database • Updated Apr 19, 2023

Package

maven org.eclipse.californium:californium-core (Maven)

Affected versions

>= 2.0.0, <= 2.7.2
>= 3.0.0, <= 3.5.0

Patched versions

2.7.3
3.6.0

Description

In Eclipse Californium versions 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.

References

Published by the National Vulnerability Database Jul 29, 2022
Published to the GitHub Advisory Database Jul 30, 2022
Reviewed Aug 10, 2022
Last updated Apr 19, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.095%
(42nd percentile)

Weaknesses

CVE ID

CVE-2022-2576

GHSA ID

GHSA-qq3j-44gw-cf6r

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.