Security readout for executives and security teams
A flaw in Contiki-NG tinyDTLS can let a remote unauthenticated attacker crash affected systems by sending crafted DTLS data. The source bundle rates it critical, but affected-product metadata is sparse and no active exploitation is confirmed. Exposure is most likely in embedded, IoT, or firmware deployments that directly include Contiki-NG tinyDTLS from the affected master branch or downstream forks. The CVE data lists no CPEs, vendor, or packaged product names, so asset mapping requires dependency and firmware review. Treat this as urgent where Contiki-NG tinyDTLS is present on reachable devices, especially operational or embedded systems. The main business risk is service disruption from remote unauthenticated traffic. First priority is confirming whether the vulnerable component exists in your products or fleet. Mitigation focus: Inventory firmware and services that include Contiki-NG tinyDTLS.; Check upstream or product-vendor guidance for a fixed revision or workaround.; Prioritize remediation for internet-exposed or remotely reachable DTLS services..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2021-42147 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H3.95.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.1CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://seclists.org/fulldisclosure/2024/Jan/20CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.