LiveActive security incident?Get immediate response
CVE Record

CVE-2021-29603: Heap OOB write in TFLite

TensorFlow is an end-to-end open source platform for machine learning. A specially crafted TFLite model could trigger an OOB write on heap in the TFLite implementation of `ArgMin`/`ArgMax`(https://github.com/tensorflow/tensorflow/blob/102b211d892f3abc14f845a72047809b39cc65ab/tensorflow/lite/kernels/arg_min_max.cc#L52-L59). If `axis_value` is not a value between 0 and `NumDimensions(input)`, then the condition in the `if` is never true, so code writes past the last valid element of `output_dims->data`. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.

LowCVSS 2.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2021-29603 is a low-severity TensorFlow Lite flaw where a maliciously crafted model can cause a heap out-of-bounds write in ArgMin/ArgMax handling. Business urgency is mainly for systems that load untrusted or user-supplied TFLite models.

Executive priority

Treat as routine but real risk management. Prioritize patching where TFLite models cross trust boundaries, especially product features accepting uploaded or third-party models. Lower priority is reasonable for isolated systems using only vetted internal models.

Technical view

TensorFlow Lite ArgMin/ArgMax mishandles an out-of-range axis_value, which can lead to writes past output_dims->data. It is CWE-787 with CVSS 3.1 score 2.5. Affected ranges include TensorFlow <2.1.4, 2.2.0 to <2.2.3, 2.3.0 to <2.3.3, and 2.4.0 to <2.4.2.

Likely exposure

Exposure is most likely in applications, pipelines, or edge products that execute TFLite models from users, partners, downloaded files, or other untrusted sources. Systems using only trusted, internally generated models have lower practical exposure.

Exploitation context

The source bundle does not show known active exploitation, and KEV status is false. The advisory describes a specially crafted TFLite model as the trigger, with local, high-complexity, low-privilege CVSS conditions and availability-only impact.

Researcher notes

The issue is in TensorFlow Lite ArgMin/ArgMax dimension handling. The cited fix commit is available, but the provided sources do not establish exploitability beyond availability impact or active exploitation. Avoid assuming broader TensorFlow API exposure without local code review.

Mitigation direction

  • Upgrade TensorFlow to 2.5.0 or later where feasible.
  • Apply patched supported versions 2.4.2, 2.3.3, 2.2.3, or 2.1.4.
  • Restrict loading of untrusted TFLite models until patched.
  • Check TensorFlow vendor guidance for environment-specific remediation details.

Validation and detection

  • Inventory TensorFlow and TensorFlow Lite versions in applications and build images.
  • Identify services that load TFLite models from external or user-controlled sources.
  • Confirm deployed versions are outside the listed affected ranges.
  • Review dependency lockfiles and container images for vulnerable TensorFlow packages.
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-787: 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-29603 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
Low
CVSS
2.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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
2.5CVSS 3.1LowCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.5Low
CVSS 3.1 vector shape for CVE-2021-29603Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
tensorflowtensorflow< 2.1.4, >= 2.2.0, < 2.2.3, >= 2.3.0, < 2.3.3, >= 2.4.0, < 2.4.2Listed
Weakness

CWE details

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

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.