CVE-2021-29538 json
Division by zero in `Conv2DBackpropFilter`
published 2021-05-14 5 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2021-29538 , EUVD-2021-0279 , GHSA-j8qc-5fqr-52fp , PYSEC-2021-175 , PYSEC-2021-466 , PYSEC-2021-664
- 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 division by zero to occur in `Conv2DBackpropFilter`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/1b0296c3b8dd9bd948f924aa8cd62f87dbb7c3da/tensorflow/core/kernels/conv_grad_filter_ops.cc#L513-L522) computes a divisor based on user provided data (i.e., the shape of the tensors given as arguments). If all shapes are empty then `work_unit_size` is 0. Since there is no check for this case before division, this results in a runtime exception, with potential to be abused for a denial of service. 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-j8qc-5fqr-52fp 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-369 Divide By Zero
References
-
github.com
/tensorflow/tensorflow/commit/c570e2ecfc822941335ad48f6e10df4e21f11c96
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-j8qc-5fqr-52fp
web, exploit, patch, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-29538
advisory, web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-466.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-664.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-175.yaml
web
-
github.com
/tensorflow/tensorflow
package
Sources
- CVE List CVE-2021-29538
- GitHub Advisory GHSA-j8qc-5fqr-52fp
- NVD CVE-2021-29538
- OSV BIT-tensorflow-2021-29538
- OSV PYSEC-2021-175
- OSV PYSEC-2021-466
- OSV PYSEC-2021-664
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.