Safeguard
Vulnerability Analysis•

CVE-2021-42146: High Epoch Reuse in tinyDTLS

CVE-2021-42146 is a high DTLS epoch reuse flaw in Contiki-NG tinyDTLS, scored 7.5. No fixed version was confirmed, so check the project and your supplier.

Safeguard Security Team
4 min read

CVE-2021-42146 is a high severity flaw in Contiki-NG tinyDTLS, scored 7.5 by NVD. DTLS servers let the same epoch number be reused within two times the maximum segment lifetime, which RFC 6347 prohibits, and the record says this can expose application data. No fixed version was confirmed.

What's affected

The record says DTLS servers in Contiki-NG tinyDTLS through master commit 53a0d97 allow remote attackers to reuse the same epoch number within two times the TCP maximum segment lifetime, which RFC 6347 prohibits. The record states that this can let attackers obtain sensitive application data of connected clients.

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:N/A:N. 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-303.

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

  1. Find every product or firmware image that includes tinyDTLS, including the ones built by suppliers.
  2. Record which commit each one was built from, using the check above.
  3. Ask your supplier or the project whether a fixed commit exists for this CVE, and move to it when it does.
  4. 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.
  5. Subscribe to the project's issue tracker so later fixes are noticed.

Why it matters

The rule exists for a reason. An epoch number marks a set of keys, and reusing one inside the window in which old packets might still be in flight lets stale or replayed records be confused with fresh ones. The record files it as CWE-755, CWE-303: CWE-755 for the bad handling of an exceptional condition and CWE-303 for an incorrect implementation of an authentication algorithm.

This one is about confidentiality rather than availability, which is why its vector differs from its siblings in the same disclosure series. The record's claim is about data of connected clients, so the exposure is higher where one server handles many clients or where the data is sensitive.

The fix belongs in the protocol state machine, enforcing the rule from the RFC. Until a fixed commit is available, the sensible steps are to find the library in your products, keep DTLS endpoints off untrusted networks and ask the supplier about the status.

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 RFC 6347 say about this?

The record says it prohibits reusing the same epoch number within two times the TCP maximum segment lifetime. The record does not quote the RFC beyond that.

Is this an availability bug like the others?

No. The record states that attackers can obtain sensitive application data of connected clients.

Sources

Last reviewed: 19 October 2026.

Never miss an update

Weekly insights on software supply chain security, delivered to your inbox.

We email you a link to confirm, and only then add you to the list. Unsubscribe in one click. Privacy

Self-healing security runs on Safeguard.

Your first fix PR is minutes away.

No sales call required, even your agent can complete the purchase over MCP.