CVE-2021-42144 is a critical severity buffer over-read in Contiki-NG tinyDTLS, scored 9.8 by NVD. Crafted input to the function dtls_ccm_decrypt_message() can let an attacker obtain sensitive information. It affects code through master commit 53a0d97, and no fixed version was confirmed.
What's affected
The record describes a buffer over-read in Contiki-NG tinyDTLS through master commit 53a0d97, reachable through crafted input to the function dtls_ccm_decrypt_message(). The record says an attacker can obtain sensitive information. The NVD product entry is listed under the name contiki-ng_tinydtls, which is worth knowing when you search an inventory.
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-125.
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
CCM is the authenticated encryption mode used to protect DTLS records in this library. The decrypt function takes a length that comes from the packet. If the code reads more bytes than the packet holds, it reads adjacent memory, and the record says that memory can end up exposed to the attacker.
The record files it as CWE-125, out-of-bounds read. Reads past a buffer rarely crash anything, which is why they last for years in embedded code. They also expose key material, session state or other clients' data if those happen to sit next to the buffer.
The vector shows high impact on confidentiality, integrity and availability, which is why the score is 9.8, but the only effect the record names is information disclosure. Treat this as a reason to find your copies of the library and track a fix, not as a proven remote code execution flaw.
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 an over-read give an attacker?
Whatever data sits next to the buffer in memory. The record says an attacker can obtain sensitive information.
How do I find the library in my firmware?
Search your source tree and submodules for tinydtls, and check the commit with the git command in the check section. Ask suppliers for the commit if you only receive binaries.
Sources
Last reviewed: 19 October 2026.