Security readout for executives and security teams
Plain-English summary
A specially crafted TensorFlow Lite model can cause a vulnerable TensorFlow process to hit a divide-by-zero condition during padding calculations. The documented impact is limited availability loss, not data theft or code execution.
Executive priority
Treat as routine patching unless the business accepts untrusted ML models. Prioritize internet-facing or customer-upload model processing paths first, but the sourced severity and CVSS support low urgency.
Technical view
TFLite padding output-size computation in ComputeOutSize divided by the stride argument without first ensuring stride was nonzero. Crafted models could pass stride 0 into that path. TensorFlow fixed this for 2.5.0 and planned supported-branch cherry-picks.
Likely exposure
Exposure is most likely where applications or pipelines load untrusted, user-supplied, or third-party TFLite models using affected TensorFlow versions.
Exploitation context
No CISA KEV listing is indicated. The sources describe craftable special models but do not cite exploitation in the wild. CVSS indicates local access, high complexity, low privileges, and low availability impact.
Researcher notes
Focus review on TFLite model ingestion and version verification. The vulnerable path is ComputeOutSize in padding logic, where stride 0 was not checked before division. Sources do not provide evidence of broader product impact.
Mitigation direction
- Upgrade to TensorFlow 2.5.0 or a fixed supported branch release.
- Use 2.4.2, 2.3.3, 2.2.3, or 2.1.4 where applicable.
- Avoid processing untrusted TFLite models until vulnerable runtimes are updated.
- Check TensorFlow advisory guidance before relying on compensating controls.
Validation and detection
- Inventory TensorFlow and TFLite versions in applications, containers, and build artifacts.
- Identify workflows that load user-supplied or third-party TFLite models.
- Confirm vulnerable ranges are absent from deployed runtime environments.
- Review crash telemetry for divide-by-zero or TFLite padding failures.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2021-29585 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- 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
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L11.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
2.5LowVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mv78-g7wq-mhp4CVE reference · x_refsource_CONFIRM
- https://github.com/tensorflow/tensorflow/commit/49847ae69a4e1a97ae7f2db5e217c77721e37948CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Divide By Zero
Divide By Zero represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.