CVE-2021-29591 Stack overflow due to looping TFLite subgraph

High 7.3 Published Updated

An attacker can cause a denial of service via stack overflow by crafting a malicious TFLite model with loops, affecting TensorFlow users.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
Available

What is CVE-2021-29591?

CVE-2021-29591 is a high-severity denial of service vulnerability in Google Tensorflow, published on 14 May 2021. It can only be exploited from the same machine or local network, with no action from the victim.

Official description

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.

Weakness: CWE-674, CWE-835

Which versions are affected by CVE-2021-29591?

28 open source packages ship an affected version, including tensorflow, tensorflow-cpu and tensorflow-gpu. It affects 1 product.

PackageAffectedFixed in
tensorflow BitnamiAll versions2.1.4, 2.2.3, 2.3.3, 2.4.2
tensorflow PyPIAll versions2.1.4, 2.2.3, 2.3.3, 2.4.2
tensorflow PyPIAll versions2.1.4
tensorflow PyPIAll versions2.1.4
tensorflow PyPIFrom 2.2.02.2.3
tensorflow PyPIFrom 2.2.02.2.3
22 more packages
tensorflow PyPIFrom 2.3.02.3.3
tensorflow PyPIFrom 2.3.02.3.3
tensorflow PyPIFrom 2.4.02.4.2
tensorflow PyPIFrom 2.4.02.4.2
tensorflow-cpu PyPIAll versions2.1.4, 2.2.3, 2.3.3, 2.4.2
tensorflow-cpu PyPIAll versions2.1.4
tensorflow-cpu PyPIAll versions2.1.4
tensorflow-cpu PyPIFrom 2.2.02.2.3
tensorflow-cpu PyPIFrom 2.2.02.2.3
tensorflow-cpu PyPIFrom 2.3.02.3.3
tensorflow-cpu PyPIFrom 2.3.02.3.3
tensorflow-cpu PyPIFrom 2.4.02.4.2
tensorflow-cpu PyPIFrom 2.4.02.4.2
tensorflow-gpu PyPIAll versions2.1.4, 2.2.3, 2.3.3, 2.4.2
tensorflow-gpu PyPIAll versions2.1.4
tensorflow-gpu PyPIAll versions2.1.4
tensorflow-gpu PyPIFrom 2.2.02.2.3
tensorflow-gpu PyPIFrom 2.2.02.2.3
tensorflow-gpu PyPIFrom 2.3.02.3.3
tensorflow-gpu PyPIFrom 2.3.02.3.3
tensorflow-gpu PyPIFrom 2.4.02.4.2
tensorflow-gpu PyPIFrom 2.4.02.4.2

Products include Google Tensorflow.

How do I fix CVE-2021-29591?

Upgrade tensorflow to a fixed version for your release line: 2.1.4, 2.2.3, 2.3.3 or 2.4.2.

Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.

Is CVE-2021-29591 being exploited?

There is no known exploitation of CVE-2021-29591 in the wild and no public exploit code.

All Google Tensorflow vulnerabilities

Sources

Also known as BIT-tensorflow-2021-29591, GHSA-cwv3-863g-39vx, PYSEC-2021-228, PYSEC-2021-519, PYSEC-2021-717.

Is CVE-2021-29591 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free