Skip to content
Fencer Vulns
low 2.5

CVE-2021-29583 json

Heap buffer overflow and undefined behavior in `FusedBatchNorm`

published 2021-05-14 5 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2021-29583 , EUVD-2021-0324 , GHSA-9xh4-23q4-v6wr , PYSEC-2021-220 , PYSEC-2021-511 , PYSEC-2021-709

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. The implementation of `tf.raw_ops.FusedBatchNorm` is vulnerable to a heap buffer overflow. If the tensors are empty, the same implementation can trigger undefined behavior by dereferencing null pointers. The implementation(https://github.com/tensorflow/tensorflow/blob/57d86e0db5d1365f19adcce848dfc1bf89fdd4c7/tensorflow/core/kernels/fused_batch_norm_op.cc) fails to validate that `scale`, `offset`, `mean` and `variance` (the last two only when required) all have the same number of elements as the number of channels of `x`. This results in heap out of bounds reads when the buffers backing these tensors are indexed past their boundary. If the tensors are empty, the validation mentioned in the above paragraph would also trigger and prevent the undefined behavior. 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.0rc0, 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.0rc0, 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.0rc0, 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

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9xh4-23q4-v6wr 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.0rc0
>=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.2.0rc0
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.0rc0
>=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.2.0rc0
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.0rc0
>=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.2.0rc0
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 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.