LiveActive security incident?Get immediate response
CVE Record

CVE-2021-27411: Micrium OS Integer Overflow or Wraparound

Micrium OS Versions 5.10.1 and prior are vulnerable to integer wrap-around in functions Mem_DynPoolCreate, Mem_DynPoolCreateHW and Mem_PoolCreate. This unverified memory assignment can lead to arbitrary memory allocation, resulting in unexpected behavior such as very small blocks of memory being allocated instead of very large ones.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Micrium OS 5.10.1 and earlier can miscalculate requested memory sizes in specific memory pool creation functions. A system may allocate a much smaller memory block than intended, causing unexpected behavior. Business urgency is moderate: the issue is remotely scored, but the provided sources do not show active exploitation or name device-specific impact.

Executive priority

Treat this as a moderate embedded-systems risk. It deserves inventory-driven follow-up, especially for industrial or remotely reachable devices, but the provided evidence does not support emergency response language.

Technical view

CVE-2021-27411 is a CWE-190 integer wraparound in Mem_DynPoolCreate, Mem_DynPoolCreateHW, and Mem_PoolCreate. The CVSS 3.1 score is 6.5 with network attack vector, no privileges, and no user interaction. The stated impacts are limited integrity and availability, with no confidentiality impact.

Likely exposure

Exposure is most likely in embedded, IoT, or industrial products that include Micrium OS 5.10.1 or earlier. The source bundle does not identify downstream device vendors or specific firmware versions, so asset inventory and vendor confirmation are required.

Exploitation context

The bundle marks CISA KEV as false and provides no evidence of active exploitation. The CVSS vector indicates potential remote attackability, but the provided sources do not describe exploit prerequisites, reachable interfaces, or public exploit maturity.

Researcher notes

Key gaps are downstream product mapping, patch status, and reachable attack paths. Analysis should focus on firmware provenance, affected Micrium OS versions, and whether memory pool creation paths can be influenced across exposed interfaces.

Mitigation direction

  • Identify products and firmware that include Micrium OS 5.10.1 or earlier.
  • Check Silicon Labs, Micrium, and device-vendor guidance for fixed versions or mitigations.
  • Prioritize updates for network-reachable embedded or industrial devices.
  • Reduce unnecessary network exposure to affected devices while awaiting vendor guidance.
  • Document compensating controls where firmware updates are unavailable.

Validation and detection

  • Review SBOMs, firmware notes, or vendor attestations for Micrium OS usage.
  • Confirm whether affected functions are present in the shipped firmware codebase.
  • Map exposed network services on devices that may embed Micrium OS.
  • Verify vendor advisory status and remediation availability for each affected product.
  • Retest firmware version and exposure after applying vendor updates.
Prepared
Confidence
medium
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-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-27411 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
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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
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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L3.92.5Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2021-27411Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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
MicriumMicrium OSunspecifiedListed
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.