CVE-2021-41197: TensorFlow: integer overflow in tensor dims causes DoS
MEDIUM PoC AVAILABLEA local attacker with low privileges can crash TensorFlow processes by crafting tensors with dimensions that overflow int64_t, triggering CHECK-failures. This is a denial-of-service risk in shared ML inference environments where users can submit arbitrary inputs. Patch to TensorFlow 2.7.0, 2.6.1, 2.5.2, or 2.4.4 immediately if these versions are in your supported range.
Risk Assessment
Medium risk overall, but elevated in multi-tenant ML serving scenarios. The local attack vector and low privilege requirement limit opportunistic exploitation, but in shared inference environments (Jupyter hubs, MLflow model servers, internal APIs) any authenticated user could trigger a crash. No confidentiality or integrity impact — pure availability. Not actively exploited in the wild and not in CISA KEV.
Affected Systems
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| tensorflow | pip | — | No patch |
Do you use tensorflow? You're affected.
Severity & Risk
Attack Surface
Recommended Action
5 steps-
Patch: upgrade to TensorFlow 2.7.0, 2.6.1, 2.5.2, or 2.4.4 depending on your branch.
-
Workaround: validate tensor shape inputs at API boundaries before passing to TensorFlow ops — reject any dimension product that would exceed INT64_MAX.
-
Detection: monitor for unexpected TensorFlow process crashes or CHECK-failure stack traces in logs (grep for 'CHECK fail' or 'MultiplyWithoutOverflow').
-
Isolation: run inference workers in isolated processes/containers so a single crash does not take down the entire serving stack.
-
Confirm no public-facing endpoints accept raw tensor shapes without validation.
Classification
Compliance Impact
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2021-41197?
A local attacker with low privileges can crash TensorFlow processes by crafting tensors with dimensions that overflow int64_t, triggering CHECK-failures. This is a denial-of-service risk in shared ML inference environments where users can submit arbitrary inputs. Patch to TensorFlow 2.7.0, 2.6.1, 2.5.2, or 2.4.4 immediately if these versions are in your supported range.
Is CVE-2021-41197 actively exploited?
Proof-of-concept exploit code is publicly available for CVE-2021-41197, increasing the risk of exploitation.
How to fix CVE-2021-41197?
1. Patch: upgrade to TensorFlow 2.7.0, 2.6.1, 2.5.2, or 2.4.4 depending on your branch. 2. Workaround: validate tensor shape inputs at API boundaries before passing to TensorFlow ops — reject any dimension product that would exceed INT64_MAX. 3. Detection: monitor for unexpected TensorFlow process crashes or CHECK-failure stack traces in logs (grep for 'CHECK fail' or 'MultiplyWithoutOverflow'). 4. Isolation: run inference workers in isolated processes/containers so a single crash does not take down the entire serving stack. 5. Confirm no public-facing endpoints accept raw tensor shapes without validation.
What systems are affected by CVE-2021-41197?
This vulnerability affects the following AI/ML architecture patterns: model serving, training pipelines, inference.
What is the CVSS score for CVE-2021-41197?
CVE-2021-41197 has a CVSS v3.1 base score of 5.5 (MEDIUM). The EPSS exploitation probability is 0.02%.
Technical Details
NVD Description
TensorFlow is an open source platform for machine learning. In affected versions TensorFlow allows tensor to have a large number of dimensions and each dimension can be as large as desired. However, the total number of elements in a tensor must fit within an `int64_t`. If an overflow occurs, `MultiplyWithoutOverflow` would return a negative result. In the majority of TensorFlow codebase this then results in a `CHECK`-failure. Newer constructs exist which return a `Status` instead of crashing the binary. This is similar to CVE-2021-29584. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
Exploitation Scenario
An adversary with access to a shared ML inference environment (e.g., internal model API, Jupyter notebook server, MLflow serving endpoint) submits a POST request with a tensor shape such as [9223372036854775807, 9223372036854775807]. TensorFlow's MultiplyWithoutOverflow silently returns a negative value, triggering a CHECK-failure that crashes the TensorFlow serving process. In containerized environments without restart policies, this takes the inference service offline. In persistent notebook environments, it terminates the kernel. A low-skill attacker can automate this in a loop to maintain denial of service.
Weaknesses (CWE)
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H References
- github.com/tensorflow/tensorflow/commit/7c1692bd417eb4f9b33ead749a41166d6080af85 Patch 3rd Party
- github.com/tensorflow/tensorflow/commit/a871989d7b6c18cdebf2fb4f0e5c5b62fbc19edf Patch 3rd Party
- github.com/tensorflow/tensorflow/commit/d81b1351da3e8c884ff836b64458d94e4a157c15 Patch 3rd Party
- github.com/tensorflow/tensorflow/issues/46890 Exploit 3rd Party
- github.com/tensorflow/tensorflow/issues/51908 Exploit 3rd Party
- github.com/tensorflow/tensorflow/security/advisories/GHSA-prcg-wp5q-rv7p Patch 3rd Party
- github.com/ARPSyndicate/cvemon Exploit
- github.com/adwisatya/SnykVulndb Exploit
- github.com/gclonly/im Exploit
Timeline
Related Vulnerabilities
CVE-2020-15196 9.9 TensorFlow: heap OOB read in sparse/ragged count ops
Same package: tensorflow CVE-2020-15205 9.8 TensorFlow: heap overflow in StringNGrams, ASLR bypass
Same package: tensorflow CVE-2020-15208 9.8 TFLite: OOB read/write via tensor dimension mismatch
Same package: tensorflow CVE-2019-16778 9.8 TensorFlow: heap overflow in UnsortedSegmentSum op
Same package: tensorflow CVE-2022-23587 9.8 TensorFlow: integer overflow in Grappler enables RCE
Same package: tensorflow
AI Threat Alert