CVE-2021-29590
Description
TensorFlow is an end-to-end open source platform for machine learning. The implementations of the `Minimum` and `Maximum` TFLite operators can be used to read data outside of bounds of heap allocated objects, if any of the two input tensor arguments are empty. This is because the broadcasting implementation(https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/maximum_minimum.h#L52-L56) indexes in both tensors with the same index but does not validate that the index is within 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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Arch Fixed 1 release
| Version | Status | Fixed in |
|---|---|---|
| — | Fixed | 2.5.0-1 |
Debian Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| sid | Fixed | 0 |
| forky | Fixed | 0 |
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| PyPI | tensorflow | >=2.3.0,<2.3.3 | 2.3.3 |
| PyPI | tensorflow | >=2.4.0,<2.4.2 | 2.4.2 |
| PyPI | tensorflow-cpu | >=2.3.0,<2.3.3 | 2.3.3 |
| PyPI | tensorflow | >=2.2.0,<2.2.3 | 2.2.3 |
| PyPI | tensorflow | <2.1.4 | 2.1.4 |
| PyPI | tensorflow-gpu | >=2.2.0,<2.2.3 | 2.2.3 |
| PyPI | tensorflow-gpu | >=2.3.0,<2.3.3 | 2.3.3 |
| PyPI | tensorflow-cpu | <2.1.4 | 2.1.4 |
| PyPI | tensorflow-cpu | >=2.2.0,<2.2.3 | 2.2.3 |
| PyPI | tensorflow-gpu | >=2.4.0,<2.4.2 | 2.4.2 |
| PyPI | tensorflow-cpu | >=2.4.0,<2.4.2 | 2.4.2 |
| PyPI | tensorflow-gpu | <2.1.4 | 2.1.4 |
| PyPI | tensorflow-cpu | <953f28dca13c92839ba389c055587cfe6c723578||>=2.4.0,<2.4.2 | 953f28dca13c92839ba389c055587cfe6c723578 |
| PyPI | tensorflow | <953f28dca13c92839ba389c055587cfe6c723578||>=2.4.0,<2.4.2 | 953f28dca13c92839ba389c055587cfe6c723578 |
| PyPI | tensorflow-gpu | <953f28dca13c92839ba389c055587cfe6c723578||>=2.4.0,<2.4.2 | 953f28dca13c92839ba389c055587cfe6c723578 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-24x6-8c7m-hv3f
- https://nvd.nist.gov/vuln/detail/CVE-2021-29590
- https://github.com/tensorflow/tensorflow/commit/953f28dca13c92839ba389c055587cfe6c723578
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-518.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-716.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-227.yaml
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/blob/0d45ea1ca641b21b73bcf9c00e0179cda284e7e7/tensorflow/lite/kernels/internal/reference/maximum_minimum.h#L52-L56
- https://security-tracker.debian.org/tracker/CVE-2021-29590
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.