Skip to content
Fencer Intel
low 3.6

CVE-2021-29611 json

Incomplete validation in `SparseReshape`

published 5y ago modified 2mo ago also BIT-tensorflow-2021-29611 , EUVD-2021-0352 , GHSA-9rpc-5v9q-5r7f , PYSEC-2021-248 , PYSEC-2021-539 , PYSEC-2021-737

cvss
3.6
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 10%
public exploits
0
none known

Summary

TensorFlow is an end-to-end open source platform for machine learning. Incomplete validation in `SparseReshape` results in a denial of service based on a `CHECK`-failure. The implementation(https://github.com/tensorflow/tensorflow/blob/e87b51ce05c3eb172065a6ea5f48415854223285/tensorflow/core/kernels/sparse_reshape_op.cc#L40) has no validation that the input arguments specify a valid sparse tensor. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2 and TensorFlow 2.3.3, as these are the only affected versions.

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

Is CVE-2021-29611 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9rpc-5v9q-5r7f referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 3.6 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L
GitHub 3.1 3.6 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/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.3.0, <2.3.3
>=2.4.0, <2.4.2
<2.1.4
>=2.2.0, <2.2.3
2.3.3
2.4.2
2.1.4
2.2.3
pypi tensorflow-cpu
>=2.3.0, <2.3.3
>=2.4.0, <2.4.2
<2.1.4
>=2.2.0, <2.2.3
2.3.3
2.4.2
2.1.4
2.2.3
pypi tensorflow-gpu
>=2.3.0, <2.3.3
>=2.4.0, <2.4.2
<2.1.4
>=2.2.0, <2.2.3
2.3.3
2.4.2
2.1.4
2.2.3
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-665 Improper Initialization
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel 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.