Skip to content
Fencer Intel
low 2.5

CVE-2021-29512 json

Heap buffer overflow in `RaggedBinCount`

published 5y ago modified 2mo ago also BIT-tensorflow-2021-29512 , EUVD-2021-0253 , GHSA-4278-2v5v-65r4 , PYSEC-2021-149 , PYSEC-2021-440 , PYSEC-2021-638

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. If the `splits` argument of `RaggedBincount` does not specify a valid `SparseTensor`(https://www.tensorflow.org/api_docs/python/tf/sparse/SparseTensor), then an attacker can trigger a heap buffer overflow. This will cause a read from outside the bounds of the `splits` tensor buffer in the implementation of the `RaggedBincount` op(https://github.com/tensorflow/tensorflow/blob/8b677d79167799f71c42fd3fa074476e0295413a/tensorflow/core/kernels/bincount_op.cc#L430-L433). Before the `for` loop, `batch_idx` is set to 0. The user controls the `splits` array, making it contain only one element, 0. Thus, the code in the `while` loop would increment `batch_idx` and then try to read `splits(1)`, which is outside of bounds. 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 also affected.

Patch / fix

  • pypi tensorflow 2.3.3, 2.4.2
  • pypi tensorflow-cpu 2.3.3, 2.4.2
  • pypi tensorflow-gpu 2.3.3, 2.4.2
  • bitnami tensorflow 2.3.3, 2.4.2
  • google tensorflow 2.3.3, 2.4.2
  • tensorflow Arch Linux 2.5.0-1

arch linux advisories AVG-1962

Is CVE-2021-29512 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-4278-2v5v-65r4 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.3.0, <2.3.3
>=2.4.0, <2.4.2
2.3.3
2.4.2
pypi tensorflow-cpu
>=2.3.0, <2.3.3
>=2.4.0, <2.4.2
2.3.3
2.4.2
pypi tensorflow-gpu
>=2.3.0, <2.3.3
>=2.4.0, <2.4.2
2.3.3
2.4.2
bitnami tensorflow
>=2.3.0, <2.3.3
>=2.4.0, <2.4.2
2.3.3
2.4.2

Affected products

  • tensorflow tensorflow

Classification

Weakness
  • CWE-120 Buffer Copy without Checking Size of Input
  • CWE-787 Out-of-bounds Write

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.