DTLS server crash via cipher-state assertion
Published Jan 24, 2024 · Updated Jun 20, 2025
Improper exception handling in Contiki-NG tinyDTLS through 2018-08-30 allows remote attackers to crash a DTLS server. The check_certificate_request() function asserts that the peer cipher is TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8 instead of rejecting a CertificateRequest received in an inconsistent handshake state, causing abort() to terminate the process. No authentication or user interaction is required; the bounded impact is interruption of the affected DTLS service through process termination.
Summary
What happened
Improper exception handling in Contiki-NG tinyDTLS through 2018-08-30 allows remote attackers to crash a DTLS server. The check_certificate_request() function asserts that the peer cipher is TLS_ECDHE_ECDSA_WITH_AES_128_CCM_8 instead of rejecting a CertificateRequest received in an inconsistent handshake state, causing abort() to terminate the process. No authentication or user interaction is required; the bounded impact is interruption of the affected DTLS service through process termination.
The record
- CVE
- CVE-2021-42145
- Published
- Jan 24, 2024
- Updated
- Jun 20, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-755, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 24, 2024CVE publishedPublication date reported by the CVE source.
- Jun 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo