LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32771: Buffer overflow in contiki-ng

Contiki-NG is an open-source, cross-platform operating system for IoT devices. In affected versions it is possible to cause a buffer overflow when copying an IPv6 address prefix in the RPL-Classic implementation in Contiki-NG. In order to trigger the vulnerability, the Contiki-NG system must have joined an RPL DODAG. After that, an attacker can send a DAO packet with a Target option that contains a prefix length larger than 128 bits. The problem was fixed after the release of Contiki-NG 4.7. Users unable to upgrade may apply the patch in Contiki-NG PR #1615.

HighCVSS 8.1Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-32771 affects Contiki-NG, an IoT operating system. A malformed RPL-Classic network message can trigger a buffer overflow after a device has joined an RPL DODAG. The issue is rated high because memory corruption may affect confidentiality, integrity, and availability of constrained devices.

Executive priority

Prioritize affected IoT deployments that participate in RPL networks, especially where devices support safety, operations, or sensitive telemetry. This is high severity but not currently evidenced as actively exploited in the provided sources.

Technical view

Affected Contiki-NG versions before 4.8 can overflow a buffer while copying an IPv6 address prefix in RPL-Classic. The vulnerable condition involves a DAO Target option with a prefix length greater than 128 bits after DODAG membership. The vendor fixed it after 4.7; PR #1615 contains the patch.

Likely exposure

Most exposure is in IoT firmware or products built on Contiki-NG before 4.8 that use RPL-Classic and join RPL DODAGs. Generic enterprise systems are unlikely to be directly affected unless they embed or manage such devices.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. Exploitation requires network reachability in the relevant RPL context and a device state where it has joined an RPL DODAG, which matches the CVSS high attack complexity.

Researcher notes

Key constraints matter: the vulnerable path is in RPL-Classic, requires DODAG membership, and involves improper handling of an IPv6 prefix length above 128 bits. Evidence supports versions before 4.8 and the PR #1615 patch; no broader product list is provided.

Mitigation direction

  • Upgrade Contiki-NG-based builds to version 4.8 or later.
  • If upgrade is not possible, apply the vendor patch from PR #1615.
  • Confirm device vendors have incorporated the fixed Contiki-NG code.
  • Rebuild and redeploy affected firmware after applying the fix.
  • Check vendor guidance for product-specific remediation and rollout constraints.

Validation and detection

  • Inventory products, firmware, and SBOMs for Contiki-NG usage.
  • Identify Contiki-NG versions before 4.8 or forks missing PR #1615.
  • Confirm whether RPL-Classic is enabled in affected builds.
  • Verify deployed devices can join RPL DODAGs in their operating environment.
  • Track remediation evidence from firmware release notes or vendor advisories.
Prepared
Confidence
high
Sources
6

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-32771 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.1 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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
5Source 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.1CVSS 3.1HighCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H2.25.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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.8Listed
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.