CVE-2021-37651
Description
TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation for `tf.raw_ops.FractionalAvgPoolGrad` can be tricked into accessing data outside of bounds of heap allocated buffers. The [implementation](https://github.com/tensorflow/tensorflow/blob/f24faa153ad31a4b51578f8181d3aaab77a1ddeb/tensorflow/core/kernels/fractional_avg_pool_op.cc#L205) does not validate that the input tensor is non-empty. Thus, code constructs an empty `EigenDoubleMatrixMap` and then accesses this buffer with indices that are outside of the empty area. We have patched the issue in GitHub commit 0f931751fb20f565c4e94aa6df58d54a003cdb30. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.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.1-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.4 | 2.3.4 |
| PyPI | tensorflow | >=2.4.0,<2.4.3 | 2.4.3 |
| PyPI | tensorflow | >=2.5.0,<2.5.1 | 2.5.1 |
| PyPI | tensorflow-cpu | <2.3.4 | 2.3.4 |
| PyPI | tensorflow-cpu | >=2.4.0,<2.4.3 | 2.4.3 |
| PyPI | tensorflow-cpu | >=2.5.0,<2.5.1 | 2.5.1 |
| PyPI | tensorflow-gpu | <2.3.4 | 2.3.4 |
| PyPI | tensorflow-gpu | >=2.4.0,<2.4.3 | 2.4.3 |
| PyPI | tensorflow-gpu | >=2.5.0,<2.5.1 | 2.5.1 |
| PyPI | tensorflow | <0f931751fb20f565c4e94aa6df58d54a003cdb30||>=2.4.0,<2.4.3 | 0f931751fb20f565c4e94aa6df58d54a003cdb30 |
| PyPI | tensorflow-cpu | <0f931751fb20f565c4e94aa6df58d54a003cdb30||>=2.4.0,<2.4.3 | 0f931751fb20f565c4e94aa6df58d54a003cdb30 |
| PyPI | tensorflow-gpu | <0f931751fb20f565c4e94aa6df58d54a003cdb30||>=2.4.0,<2.4.3 | 0f931751fb20f565c4e94aa6df58d54a003cdb30 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-hpv4-7p9c-mvfr
- https://nvd.nist.gov/vuln/detail/CVE-2021-37651
- https://github.com/tensorflow/tensorflow/commit/0f931751fb20f565c4e94aa6df58d54a003cdb30
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-564.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-762.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-273.yaml
- https://github.com/tensorflow/tensorflow
- https://security-tracker.debian.org/tracker/CVE-2021-37651
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.