Skip to content
Fencer Intel
low 2.5

CVE-2021-29558 json

Heap buffer overflow in `SparseSplit`

published 5y ago modified 2mo ago also BIT-tensorflow-2021-29558 , EUVD-2021-0299 , GHSA-mqh2-9wrp-vx84 , PYSEC-2021-195 , PYSEC-2021-486 , PYSEC-2021-684

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 11%
public exploits
0
none known

Summary

TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a heap buffer overflow in `tf.raw_ops.SparseSplit`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/699bff5d961f0abfde8fa3f876e6d241681fbef8/tensorflow/core/util/sparse/sparse_tensor.h#L528-L530) accesses an array element based on a user controlled offset. 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.0rc0, 2.3.3, 2.3.4, 2.4.2, 2.4.3
  • pypi tensorflow-cpu 2.1.4, 2.2.3, 2.3.0rc0, 2.3.3, 2.3.4, 2.4.2, 2.4.3
  • pypi tensorflow-gpu 2.1.4, 2.2.3, 2.3.0rc0, 2.3.3, 2.3.4, 2.4.2, 2.4.3
  • 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-29558 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.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-mqh2-9wrp-vx84 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 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 4.6 AV:L/AC:L/Au:N/C:P/I:P/A:P
OSV 3.1 7.8 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.2.0, <2.3.0rc0
>=2.3.0, <2.3.4
>=2.4.0, <2.4.3
2.1.4
2.2.3
2.3.3
2.4.2
2.3.0rc0
2.3.4
2.4.3
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.2.0, <2.3.0rc0
>=2.3.0, <2.3.4
>=2.4.0, <2.4.3
2.1.4
2.2.3
2.3.3
2.4.2
2.3.0rc0
2.3.4
2.4.3
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.2.0, <2.3.0rc0
>=2.3.0, <2.3.4
>=2.4.0, <2.4.3
2.1.4
2.2.3
2.3.3
2.4.2
2.3.0rc0
2.3.4
2.4.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

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.