LiveActive security incident?Get immediate response
CVE Record

CVE-2021-22680: NXP MQX Integer Overflow or Wraparound

NXP MQX Versions 5.1 and prior are vulnerable to integer overflow in mem_alloc, _lwmem_alloc and _partition functions. This unverified memory assignment can lead to arbitrary memory allocation, resulting in unexpected behavior such as a crash or a remote code injection/execution.

HighCVSS 7.3Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-22680 affects NXP MQX 5.1 and earlier. A memory allocation integer overflow can cause crashes or potentially allow remote code execution. Treat this as important for embedded or industrial systems that still rely on MQX, but the provided sources do not show confirmed active exploitation.

Executive priority

Prioritize discovery first, then remediation for exposed embedded systems. The business risk is operational disruption or compromise of devices running older MQX-based firmware, but urgency should be calibrated because active exploitation is not confirmed in the supplied evidence.

Technical view

The issue is CWE-190 integer overflow or wraparound in MQX mem_alloc, _lwmem_alloc, and _partition functions. The CVSS 3.1 score is 7.3 with network attack vector, low complexity, no privileges, and no user interaction. The source bundle reports possible arbitrary memory allocation, crash, or remote code injection/execution.

Likely exposure

Exposure is likely limited to products or firmware using NXP MQX versions 5.1 and prior. The source bundle does not identify specific downstream device models, deployment sectors, or CPEs, so asset owners must validate embedded firmware and supplier documentation.

Exploitation context

CISA KEV is false for this CVE in the supplied bundle. No cited source confirms exploitation in the wild or public weaponization. Risk still matters because the CVSS vector indicates unauthenticated network reachability and potential remote code execution impact.

Researcher notes

Evidence names vulnerable allocator functions and broad impact, but does not provide affected downstream devices, exploit prerequisites beyond CVSS, or fixed versions. Avoid assuming all NXP-based products are affected; validate MQX usage and version at firmware or vendor level.

Mitigation direction

  • Identify systems and firmware that include NXP MQX 5.1 or earlier.
  • Review the CISA advisory and NXP guidance for supported fixes or compensating controls.
  • Prioritize remediation for network-reachable embedded or industrial devices.
  • Limit untrusted network access to affected devices while vendor guidance is evaluated.
  • Request exposure and patch status from device vendors using MQX-based firmware.

Validation and detection

  • Check firmware bills of materials for NXP MQX and version details.
  • Confirm whether affected allocation functions are present in the deployed firmware branch.
  • Map network paths to devices running MQX 5.1 or prior.
  • Review vendor advisories for fixed firmware or supported upgrade paths.
  • Document devices where MQX presence cannot be confirmed from available evidence.
Prepared
Confidence
medium
Sources
3

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-190: 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-22680 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
7.3 (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:L

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
2Source 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
7.3CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L3.93.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.3High
CVSS 3.1 vector shape for CVE-2021-22680Attack 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:L

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
NXPMQXunspecifiedListed
Weakness

CWE details

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

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.