CVE-2021-42145 is a high severity assertion failure in Contiki-NG tinyDTLS, scored 7.5 by NVD. The function check_certificate_request() can be made to fail an assertion, which allows denial of service. It affects code through master commit 53a0d97, and no fixed version was confirmed.
What's affected
The record describes an assertion failure discovered in check_certificate_request() in Contiki-NG tinyDTLS through master commit 53a0d97, which allows attackers to cause denial of service. The vector is the standard network one with no privileges and no interaction, and the impact is availability only, which is why the score is 7.5 rather than higher.
The record's affected range is Contiki-NG tinyDTLS through master branch commit 53a0d97. The vector is CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. I found no fixed version in the pages I could load, so the advisory and the project's issue tracker should be checked for the current state. A maintainer comment on the project's issue tracker points to the Eclipse tinyDTLS project, which suggests the code is also tracked upstream there.
The record was published to NVD in January 2024, although the underlying reports on the project's tracker date from October 2021. The NVD severity is the one used here, and the disclosure text I could load does not give a separate vendor rating.
Weakness class: CWE-755.
How to check if you're exposed
tinyDTLS is usually compiled into firmware, so there is no package manager to ask. The record's affected range is the master branch through commit 53a0d97, so the check is which commit your copy of the library is at.
If the library is a git submodule or a vendored clone with history, this prints a message when your copy is at or before that commit:
git -C path/to/tinydtls merge-base --is-ancestor HEAD 53a0d97 && echo "at or before 53a0d97"
To find where the library lives in a larger tree, run git submodule status | grep -i dtls and find . -maxdepth 6 -iname '*tinydtls*'. If you only have a release archive without history, compare the files against the project at that commit, or ask whoever supplied the SDK which commit it was cut from.
What to do now
- Find every product or firmware image that includes tinyDTLS, including the ones built by suppliers.
- Record which commit each one was built from, using the check above.
- Ask your supplier or the project whether a fixed commit exists for this CVE, and move to it when it does.
- Where DTLS is exposed on a network you do not control, add rate limiting and monitoring in front of the device until the fix is in place.
- Subscribe to the project's issue tracker so later fixes are noticed.
Why it matters
An assertion is a check that a developer expects to always hold. When untrusted input can make it fail, the program stops, because assertions are meant to catch bugs, not hostile data. In a build that keeps assertions enabled, a single crafted message can crash the whole process or reboot the device. The record files it as CWE-755, improper handling of exceptional conditions.
Certificate request handling happens on the client side of a handshake, when a server asks the client for a certificate. The exposure therefore depends on how your device uses DTLS. A device that only acts as a server may never reach this function, while a device that connects out to servers it does not control might.
Reading the code path tells you more than the score. If your product never uses certificate based client authentication, ask your supplier whether this function is compiled in. Reachability analysis answers that kind of question for application dependencies, and the same thinking applies to firmware.
This CVE is not listed in the CISA Known Exploited Vulnerabilities catalog, and none of the pages I read state that it is exploited in the wild. That is a statement about what is known, not a reason to delay the fix.
Quick check
Is a high score fair for a crash?
The score is availability only, 7.5. A crash of a networked device that cannot recover on its own can matter a lot in practice.
Does it affect servers or clients?
The function name suggests the client handling of a certificate request, but the record does not say. Ask your supplier whether the code is reachable in your build.
Sources
Last reviewed: 19 October 2026.