CVE-2021-37647
Last modified
CVE-2021-37647 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.16% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Tensorflow | >= 2.3.0, < 2.3.4 | — | |
| Tensorflow | >= 2.4.0, < 2.4.3 | — | |
| Tensorflow | 2.5.0 | — | |
| Tensorflow | 2.6.0 | Rc0 |
References
- https://github.com/tensorflow/tensorflow/commit/02cc160e29d20631de3859c6653184e3f876b9d7Patch, Third Party Advisory
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c5x2-p679-95wcThird Party Advisory
- https://github.com/tensorflow/tensorflow/commit/02cc160e29d20631de3859c6653184e3f876b9d7Patch, Third Party Advisory
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-c5x2-p679-95wcThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2021-37647?
How severe is CVE-2021-37647?
How do I fix CVE-2021-37647?
Are you affected by CVE-2021-37647?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
