The dtls1_get_message_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before…
No fixed version listed yet.Check the vendor advisory. References ↓
The dtls1_get_message_fragment function in d1_both.c in OpenSSL, in releases before 0.9.8za, 1.0.0m and 1.0.1h, contains a flaw in handling DTLS handshake messages. An unauthenticated remote attacker can send a crafted DTLS hello message within an invalid DTLS handshake to trigger unbounded recursion and crash the client, with no user interaction or special configuration required beyond the client accepting DTLS traffic.
Official description · CVE.org
The dtls1_get_message_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h allows remote attackers to cause a denial of service (recursion and client crash) via a DTLS hello message in an invalid DTLS handshake.
- Exploited
- Not confirmed
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
Public exploit code (PoC-in-GitHub) appeared 11 years after disclosure. No confirmed exploitation is recorded.
- Disclosedday 0
- Public exploit codePoC-in-GitHub+11 yrs
What security researchers reported
Not named in any threat report yetAlso mentioned in 1 community threat pulse (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.
- Internal CVE Research9 Mar 2022