LiveActive security incident?Get immediate response
CVE Record

CVE-2021-21282: Buffer overflow in RPL source routing header processing

Contiki-NG is an open-source, cross-platform operating system for internet of things devices. In versions prior to 4.5, buffer overflow can be triggered by an input packet when using either of Contiki-NG's two RPL implementations in source-routing mode. The problem has been patched in Contiki-NG 4.5. Users can apply the patch for this vulnerability out-of-band as a workaround.

HighCVSS 8.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Contiki-NG IoT devices before version 4.5 can overflow memory while processing certain RPL source-routing packets. An attacker with network reachability to an affected RPL deployment could cause serious availability impact and limited confidentiality or integrity impact. The public bundle says the issue is patched in Contiki-NG 4.5.

Executive priority

Treat this as a high-priority embedded systems patching issue where Contiki-NG is present. The main business risk is disruption of IoT devices or low-power mesh networks. Urgency is highest for exposed or operationally critical RPL deployments.

Technical view

CVE-2021-21282 is a CWE-120 buffer overflow in Contiki-NG RPL source routing header processing. It affects Contiki-NG versions before 4.5 when either bundled RPL implementation is used in source-routing mode. CVSS 3.1 is 8.6: network, low complexity, no privileges, no user interaction, unchanged scope.

Likely exposure

Exposure is likely limited to IoT products or firmware built on Contiki-NG before 4.5 and configured to use RPL source routing. Organizations may need vendor firmware bills of materials or supplier confirmation to identify affected embedded deployments.

Exploitation context

The source bundle does not indicate CISA KEV listing or active exploitation. The CVSS vector shows the bug is network-reachable, requires no authentication, and mainly threatens availability. Public sources provided do not establish exploit maturity beyond the vulnerability description and patch reference.

Researcher notes

Key evidence is narrow: affected product is Contiki-NG before 4.5, specifically RPL source-routing mode. Do not generalize to all IoT devices or all RPL stacks. The available bundle names a patch and pull request but does not provide active exploitation evidence.

Mitigation direction

  • Upgrade affected Contiki-NG deployments to version 4.5 or later.
  • Apply the vendor-referenced out-of-band patch where upgrade is not immediately possible.
  • Confirm whether deployed firmware uses Contiki-NG RPL source-routing mode.
  • Ask device vendors for fixed firmware if Contiki-NG is embedded.
  • Limit untrusted network reachability to affected IoT/RPL networks where feasible.

Validation and detection

  • Inventory IoT firmware for Contiki-NG versions before 4.5.
  • Confirm whether either Contiki-NG RPL implementation runs in source-routing mode.
  • Verify the 4.5 fix or vendor patch is present in deployed firmware.
  • Review vendor advisories or SBOMs for CVE-2021-21282 applicability.
  • Monitor affected networks for unexplained device crashes or resets.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CWE-120: 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 lookup
cve · low confidence lookup

CVE-2021-21282 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.6 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
8.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H3.94.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.6High
CVSS 3.1 vector shape for CVE-2021-21282Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
contiki-ngcontiki-ng< 4.5Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.