LiveActive security incident?Get immediate response
CVE Record

CVE-2021-33889: OpenThread wpantund through 2021-07-02 has a stack-based Buffer Overflow because of an inconsistency in the...

OpenThread wpantund through 2021-07-02 has a stack-based Buffer Overflow because of an inconsistency in the integer data type for metric_len.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2021-33889 is a reported stack-based buffer overflow in OpenThread wpantund through July 2, 2021. The available bundle does not provide a severity score, affected package identifiers, or confirmed impact. Treat it as relevant where wpantund is deployed, especially in operational IoT or Thread-related environments.

Executive priority

Prioritize this as an exposure-confirmation task unless wpantund is known to support critical operations. The missing severity and exploitation evidence reduce certainty, but stack-based buffer overflows can be serious when reachable in deployed services.

Technical view

The CVE describes a stack-based buffer overflow caused by inconsistent integer typing for metric_len in OpenThread wpantund. The source bundle names wpantund through 2021-07-02 but does not include CVSS, CWE mapping, exploitability details, authentication requirements, or precise affected version ranges beyond that date.

Likely exposure

Exposure is most likely limited to systems running OpenThread wpantund builds from on or before 2021-07-02. The source bundle lists no CPEs, vendor package names, or deployment scope, so asset confirmation is required before estimating business exposure.

Exploitation context

The CVE is not listed as KEV in the provided bundle, and no supplied source confirms active exploitation. The FireEye disclosure and project issue are relevant public references, but the bundle does not establish exploit maturity, public weaponization, or observed attacks.

Researcher notes

Key gaps are CVSS, affected version granularity, reachability, privileges, and fixed-version evidence. Use the CVE record, FireEye disclosure, OpenThread releases, and issue 502 to verify root cause and remediation status without assuming impact beyond the published description.

Mitigation direction

  • Inventory systems and software bills of materials for OpenThread wpantund.
  • Check OpenThread wpantund releases and issue 502 for vendor remediation guidance.
  • If affected, update or replace wpantund according to vendor guidance.
  • Retire unused wpantund deployments where operationally feasible.
  • Track the FireEye disclosure and project repository for clarification.

Validation and detection

  • Confirm whether wpantund is installed or embedded in managed products.
  • Record exact wpantund version, build date, and source commit where possible.
  • Compare findings against the CVE date and OpenThread release history.
  • Review vendor or maintainer notes for issue 502 before closure.
  • Document any systems where version evidence is unavailable.
Prepared
Confidence
medium
Sources
5

Public sources used

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.

cve · low confidence lookup

CVE-2021-33889 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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