LiveActive security incident?Get immediate response
CVE Record

CVE-2021-29588: Division by zero in TFLite's implementation of `TransposeConv`

TensorFlow is an end-to-end open source platform for machine learning. The optimized implementation of the `TransposeConv` TFLite operator is [vulnerable to a division by zero error](https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/optimized/optimized_ops.h#L5221-L5222). An attacker can craft a model such that `stride_{h,w}` values are 0. Code calling this function must validate these arguments. 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

A malicious or malformed TensorFlow Lite model can trigger a crash in affected TensorFlow versions by setting TransposeConv stride values to zero. The documented impact is limited availability loss, not data theft or code execution.

Executive priority

Treat as routine patching unless the organization accepts third-party TensorFlow Lite models. Prioritize higher if untrusted model ingestion is part of a customer-facing workflow.

Technical view

The optimized TFLite TransposeConv operator can divide by zero when stride_h or stride_w is 0. Code paths calling this function must validate arguments. Affected TensorFlow ranges include versions before 2.1.4 and specific 2.2.x, 2.3.x, and 2.4.x ranges.

Likely exposure

Exposure is most likely where affected TensorFlow/TFLite versions load attacker-supplied or otherwise untrusted models. Systems using only trusted, internally built models have lower practical risk.

Exploitation context

The source bundle does not indicate active exploitation, and KEV is false. CVSS rates exploitation as local, high complexity, and requiring low privileges, with no confidentiality or integrity impact.

Researcher notes

This is CWE-369 in the optimized TFLite TransposeConv implementation. Evidence supports denial-of-service risk through invalid model parameters, but not code execution or active exploitation.

Mitigation direction

  • Upgrade to TensorFlow 2.5.0 or the patched supported branch release.
  • Use TensorFlow 2.4.2, 2.3.3, 2.2.3, or 2.1.4 where applicable.
  • Reject untrusted TensorFlow Lite models unless business-required.
  • Validate TransposeConv stride values before invoking affected code paths.
  • Check TensorFlow advisory and commit guidance for integration details.

Validation and detection

  • Inventory TensorFlow and TFLite versions across applications and embedded builds.
  • Review dependency lockfiles, mobile packages, containers, and ML inference images.
  • Identify services or apps that accept externally supplied TFLite models.
  • Confirm model validation rejects zero TransposeConv stride values.
  • Verify upgraded builds use a fixed TensorFlow release.
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-369: 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-29588 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-29588Attack 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-369 · source CWE mapping

Divide By Zero

Divide By Zero represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.