CVE-2021-37647
Description
TensorFlow is an end-to-end open source platform for machine learning. When a user does not supply arguments that determine a valid sparse tensor, `tf.raw_ops.SparseTensorSliceDataset` implementation can be made to dereference a null pointer. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L240-L251) has some argument validation but fails to consider the case when either `indices` or `values` are provided for an empty sparse tensor when the other is not. If `indices` is empty, then [code that performs validation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/data/sparse_tensor_slice_dataset_op.cc#L260-L261) (i.e., checking that the indices are monotonically increasing) results in a null pointer dereference. If `indices` as provided by the user is empty, then `indices` in the C++ code above is backed by an empty `std::vector`, hence calling `indices->dim_size(0)` results in null pointer dereferencing (same as calling `std::vector::at()` on an empty vector). We have patched the issue in GitHub commit 02cc160e29d20631de3859c6653184e3f876b9d7. 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-cpu | <02cc160e29d20631de3859c6653184e3f876b9d7||>=2.4.0,<2.4.3 | 02cc160e29d20631de3859c6653184e3f876b9d7 |
| PyPI | tensorflow | <02cc160e29d20631de3859c6653184e3f876b9d7||>=2.4.0,<2.4.3 | 02cc160e29d20631de3859c6653184e3f876b9d7 |
| PyPI | tensorflow-gpu | <02cc160e29d20631de3859c6653184e3f876b9d7||>=2.4.0,<2.4.3 | 02cc160e29d20631de3859c6653184e3f876b9d7 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c5x2-p679-95wc
- https://nvd.nist.gov/vuln/detail/CVE-2021-37647
- https://github.com/tensorflow/tensorflow/commit/02cc160e29d20631de3859c6653184e3f876b9d7
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-560.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-758.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-269.yaml
- https://github.com/tensorflow/tensorflow
- https://security-tracker.debian.org/tracker/CVE-2021-37647
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.