CVE-2021-29547 json
Heap out of bounds in `QuantizedBatchNormWithGlobalNormalization`
published 2021-05-14 5 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2021-29547 , EUVD-2021-0288 , GHSA-4fg4-p75j-w5xj , PYSEC-2021-184 , PYSEC-2021-475 , PYSEC-2021-673
- 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 8%
- public exploits
- 0
- none known
Summary
TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a segfault and denial of service via accessing data outside of bounds in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/55a97caa9e99c7f37a0bbbeb414dc55553d3ae7f/tensorflow/core/kernels/quantized_batch_norm_op.cc#L176-L189) assumes the inputs are not empty. If any of these inputs is empty, `.flat<T>()` is an empty buffer, so accessing the element at index 0 is accessing data outside of bounds. 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.19% chance of exploitation in the next 30 days, higher than 8% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4fg4-p75j-w5xj 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 | 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.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
-
- CWE-125 Out-of-bounds Read
References
-
github.com
/tensorflow/tensorflow/commit/d6ed5bcfe1dcab9e85a4d39931bd18d99018e75b
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-4fg4-p75j-w5xj
web, exploit, patch, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-29547
advisory, web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-475.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-673.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-184.yaml
web
-
github.com
/tensorflow/tensorflow
package
Sources
- CVE List CVE-2021-29547
- GitHub Advisory GHSA-4fg4-p75j-w5xj
- NVD CVE-2021-29547
- OSV BIT-tensorflow-2021-29547
- OSV PYSEC-2021-184
- OSV PYSEC-2021-475
- OSV PYSEC-2021-673
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.