CVE-2021-29607
Summary
| CVE | CVE-2021-29607 |
|---|---|
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2021-05-14 20:15:00 UTC |
| Updated | 2021-05-18 15:08:00 UTC |
| Description | TensorFlow is an end-to-end open source platform for machine learning. Incomplete validation in `SparseAdd` results in allowing attackers to exploit undefined behavior (dereferencing null pointers) as well as write outside of bounds of heap allocated data. The implementation(https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/sparse_sparse_binary_op_shared.cc) has a large set of validation for the two sparse tensor inputs (6 tensors in total), but does not validate that the tensors are not empty or that the second dimension of `*_indices` matches the size of corresponding `*_shape`. This allows attackers to send tensor triples that represent invalid sparse tensors to abuse code assumptions that are not protected by validation. 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. |
Risk And Classification
Problem Types: CWE-754
NVD Known Affected Configurations (CPE 2.3)
| Type | Vendor | Product | Version | Update | Edition | Language |
|---|---|---|---|---|---|---|
| Application | Tensorflow | All | All | All | All |
References
| Reference | Source | Link | Tags |
|---|---|---|---|
| Incomplete validation in `SparseSparseMinimum` · Advisory · tensorflow/tensorflow · GitHub | CONFIRM | github.com | |
| Validate that a and b are proper sparse tensors · tensorflow/tensorflow@f6fde89 · GitHub | MISC | github.com | |
| Fix OOB issue with `tf.raw_ops.SparseSparseMinimum`. · tensorflow/tensorflow@ba6822b · GitHub | MISC | github.com | |
| CVE Program record | CVE.ORG | www.cve.org | canonical |
| NVD vulnerability detail | NVD | nvd.nist.gov | canonical, analysis |
No vendor comments have been submitted for this CVE.
There are currently no legacy QID mappings associated with this CVE.