CVE-2021-29523 json
CHECK-fail in AddManySparseToTensorsMap
published 2021-05-14 5 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2021-29523 , EUVD-2021-0264 , GHSA-2cpx-427x-q2c6 , PYSEC-2021-160 , PYSEC-2021-451 , PYSEC-2021-649
- cvss
- 2.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 8%
- public exploits
- 0
- none known
Summary
TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.AddManySparseToTensorsMap`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/kernels/sparse_tensors_map_ops.cc#L257) takes the values specified in `sparse_shape` as dimensions for the output shape. The `TensorShape` constructor(https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L183-L188) uses a `CHECK` operation which triggers when `InitDims`(https://github.com/tensorflow/tensorflow/blob/6f9896890c4c703ae0a0845394086e2e1e523299/tensorflow/core/framework/tensor_shape.cc#L212-L296) returns a non-OK status. This is a legacy implementation of the constructor and operations should use `BuildTensorShapeBase` or `AddDimWithStatus` to prevent `CHECK`-failures in the presence of overflows. 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.
Patch / fix
- pypi tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2
- pypi tensorflow-cpu 2.1.4, 2.2.3, 2.3.3, 2.4.2
- pypi tensorflow-gpu 2.1.4, 2.2.3, 2.3.3, 2.4.2
- bitnami tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2
- google tensorflow 2.1.4, 2.2.3, 2.3.3, 2.4.2
- tensorflow Arch Linux 2.5.0-1
arch linux advisories AVG-1962
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-2cpx-427x-q2c6 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 2.5 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L |
| GitHub | 3.1 | 2.5 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L |
| NVD | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:N/A:P |
| OSV | 3.1 | 5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | tensorflow | <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 |
| pypi | tensorflow-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 |
| pypi | tensorflow-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 |
| bitnami | tensorflow | <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 |
Affected products
- tensorflow tensorflow
Classification
- Weakness
-
- CWE-190 Integer Overflow or Wraparound
References
-
github.com
/tensorflow/tensorflow/commit/69c68ecbb24dff3fa0e46da0d16c821a2dd22d7c
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-2cpx-427x-q2c6
web, exploit, patch, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-29523
advisory, web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-451.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-649.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-160.yaml
web
-
github.com
/tensorflow/tensorflow
package
Sources
- CVE List CVE-2021-29523
- GitHub Advisory GHSA-2cpx-427x-q2c6
- NVD CVE-2021-29523
- OSV BIT-tensorflow-2021-29523
- OSV PYSEC-2021-160
- OSV PYSEC-2021-451
- OSV PYSEC-2021-649
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.