CVE-2021-42142 is a critical severity flaw in Contiki-NG tinyDTLS, scored 9.8 by NVD. DTLS servers mishandle the early use of a large epoch number, which allows denial of service and false positive packet drops. It affects code through master commit 53a0d97, and no fixed version was confirmed.
What's affected
The record says DTLS servers in Contiki-NG tinyDTLS mishandle the early use of a large epoch number, which lets remote attackers cause denial of service and false positive packet drops. The project's issue #24 describes it for master commit 53a0d97: two handshakes are completed in a row, the first with a larger epoch number than the second, and the server still lets both complete.
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:H/I:H/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, CWE-770.
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
The epoch number in DTLS tells a receiver which set of keys protects a packet. If a server accepts a large epoch too early, its later view of what counts as old or new is skewed. Legitimate packets then look out of date and are dropped, which is the false positive packet drop the record mentions.
The record lists two weaknesses, CWE-755, CWE-770. CWE-755 is improper handling of exceptional conditions and CWE-770 is allocation of resources without limits. Together they describe a state that was not bounded or validated.
Issue #24 carries a maintainer comment from February 2024 that points to the Eclipse tinyDTLS project's tracker, so check both places for a fix. For devices that cannot be updated, rate limiting handshakes at the network edge helps, because the attack depends on completing handshakes.
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
What does false positive packet drop mean here?
Valid packets are treated as out of date because the server accepted a large epoch number too early, so it discards traffic that should have been accepted.
Where should I look for a fix?
Check the Contiki-NG tinyDTLS issue tracker and the Eclipse tinyDTLS project that a maintainer comment points to, plus your device supplier.
Sources
Last reviewed: 19 October 2026.