cve.bz

CVE-2021-29591 google tensorflow: Uncontrolled Recursion

7.8 highExploit referenceEPSS 0.3%Fix available

High (7.8) in google tensorflow. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in tensorflow 2.1.4, 2.2.3, 2.3.3.

On this page
TensorFlow is an end-to-end open source platform for machine learning. TFlite graphs must not have loops between nodes. However, this condition was not checked and an attacker could craft models that would result in infinite loop during evaluation. In certain cases, the infinite loop would be replaced by stack overflow due to too many recursive calls. For example, the `While` implementation(https://github.com/tensorflow/tensorflow/blob/106d8f4fb89335a2c52d7c895b7a7485465ca8d9/tensorflow/lite/kernels/while.cc) could be tricked into a scneario where both the body and the loop subgraphs are the same. Evaluating one of the subgraphs means calling the `Eval` function for the other and this quickly exhaust all stack space. 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. Please consult our security guide(https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions.

Severity

CVSS 3.1

7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 18th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWEs
CWE-674 Uncontrolled Recursion
CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2021-29591 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-29591?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-29591?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-29591 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
google:tensorflowbefore 2.1.4
google:tensorflowfrom 2.2.0 before 2.2.3
google:tensorflowfrom 2.3.0 before 2.3.3
google:tensorflowfrom 2.4.0 before 2.4.2

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-cwv3-863g-39vxPyPItensorflow<2.1.42.1.4
GHSA-cwv3-863g-39vxPyPItensorflow>=2.2.0 <2.2.32.2.3
GHSA-cwv3-863g-39vxPyPItensorflow>=2.3.0 <2.3.32.3.3
GHSA-cwv3-863g-39vxPyPItensorflow>=2.4.0 <2.4.22.4.2
GHSA-cwv3-863g-39vxPyPItensorflow-cpu<2.1.42.1.4
GHSA-cwv3-863g-39vxPyPItensorflow-cpu>=2.2.0 <2.2.32.2.3
GHSA-cwv3-863g-39vxPyPItensorflow-cpu>=2.3.0 <2.3.32.3.3
GHSA-cwv3-863g-39vxPyPItensorflow-cpu>=2.4.0 <2.4.22.4.2
GHSA-cwv3-863g-39vxPyPItensorflow-gpu<2.1.42.1.4
GHSA-cwv3-863g-39vxPyPItensorflow-gpu>=2.2.0 <2.2.32.2.3
GHSA-cwv3-863g-39vxPyPItensorflow-gpu>=2.3.0 <2.3.32.3.3
GHSA-cwv3-863g-39vxPyPItensorflow-gpu>=2.4.0 <2.4.22.4.2
PYSEC-2021-228PyPItensorflow<2.1.4
>=2.2.0 <2.2.3
>=2.3.0 <2.3.3
>=2.4.0 <2.4.2
2.1.4, 2.2.3, 2.3.3, 2.4.2
PYSEC-2021-519PyPItensorflow-cpu<2.1.4
>=2.2.0 <2.2.3
>=2.3.0 <2.3.3
>=2.4.0 <2.4.2
2.1.4, 2.2.3, 2.3.3, 2.4.2
PYSEC-2021-717PyPItensorflow-gpu<2.1.4
>=2.2.0 <2.2.3
>=2.3.0 <2.3.3
>=2.4.0 <2.4.2
2.1.4, 2.2.3, 2.3.3, 2.4.2

Attack patterns (CAPEC)

  • CAPEC-230 Serialized Data with Nested Payloads Likelihood: Medium · Severity: High
  • CAPEC-231 Oversized Serialized Data Payloads Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON