CVE-2021-37635
Description
TensorFlow is an end-to-end open source platform for machine learning. In affected versions the implementation of sparse reduction operations in TensorFlow can trigger accesses outside of bounds of heap allocated data. The [implementation](https://github.com/tensorflow/tensorflow/blob/a1bc56203f21a5a4995311825ffaba7a670d7747/tensorflow/core/kernels/sparse_reduce_op.cc#L217-L228) fails to validate that each reduction group does not overflow and that each corresponding index does not point to outside the bounds of the input tensor. We have patched the issue in GitHub commit 87158f43f05f2720a374f3e6d22a7aaa3a33f750. 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 | <87158f43f05f2720a374f3e6d22a7aaa3a33f750||>=2.4.0,<2.4.3 | 87158f43f05f2720a374f3e6d22a7aaa3a33f750 |
| PyPI | tensorflow-cpu | <87158f43f05f2720a374f3e6d22a7aaa3a33f750||>=2.4.0,<2.4.3 | 87158f43f05f2720a374f3e6d22a7aaa3a33f750 |
| PyPI | tensorflow-gpu | <87158f43f05f2720a374f3e6d22a7aaa3a33f750||>=2.4.0,<2.4.3 | 87158f43f05f2720a374f3e6d22a7aaa3a33f750 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-cgfm-62j4-v4rf
- https://nvd.nist.gov/vuln/detail/CVE-2021-37635
- https://github.com/tensorflow/tensorflow/commit/87158f43f05f2720a374f3e6d22a7aaa3a33f750
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-548.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-746.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-257.yaml
- https://github.com/tensorflow/tensorflow
- https://security-tracker.debian.org/tracker/CVE-2021-37635
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.