CVE-2021-29566 json
Heap OOB access in `Dilation2DBackpropInput`
published 2021-05-14 5 y ago modified 2026-09-08 2 mo ago also BIT-tensorflow-2021-29566 , EUVD-2021-0307 , GHSA-pvrc-hg3f-58r6 , PYSEC-2021-203 , PYSEC-2021-494 , PYSEC-2021-692
- 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 10%
- public exploits
- 0
- none known
Summary
TensorFlow is an end-to-end open source platform for machine learning. An attacker can write outside the bounds of heap allocated arrays by passing invalid arguments to `tf.raw_ops.Dilation2DBackpropInput`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/afd954e65f15aea4d438d0a219136fc4a63a573d/tensorflow/core/kernels/dilation_ops.cc#L321-L322) does not validate before writing to the output array. The values for `h_out` and `w_out` are guaranteed to be in range for `out_backprop` (as they are loop indices bounded by the size of the array). However, there are no similar guarantees relating `h_in_max`/`w_in_max` and `in_backprop`. 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.20% chance of exploitation in the next 30 days, higher than 10% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pvrc-hg3f-58r6 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
-
- CWE-787 Out-of-bounds Write
References
-
github.com
/tensorflow/tensorflow/commit/3f6fe4dfef6f57e768260b48166c27d148f3015f
web, patch, third-party-advisory, advisory
-
github.com
/tensorflow/tensorflow/security/advisories/GHSA-pvrc-hg3f-58r6
web, exploit, patch, third-party-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-29566
advisory, web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-494.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-692.yaml
web
-
github.com
/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-203.yaml
web
-
github.com
/tensorflow/tensorflow
package
Sources
- CVE List CVE-2021-29566
- GitHub Advisory GHSA-pvrc-hg3f-58r6
- NVD CVE-2021-29566
- OSV BIT-tensorflow-2021-29566
- OSV PYSEC-2021-203
- OSV PYSEC-2021-494
- OSV PYSEC-2021-692
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.