CVE-2020-15196
Summary
| CVE | CVE-2020-15196 |
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2020-09-25 19:15:00 UTC |
| Updated | 2021-11-18 17:21:00 UTC |
| Description | In Tensorflow version 2.3.0, the `SparseCountSparseOutput` and `RaggedCountSparseOutput` implementations don't validate that the `weights` tensor has the same shape as the data. The check exists for `DenseCountSparseOutput`, where both tensors are fully specified. In the sparse and ragged count weights are still accessed in parallel with the data. But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1. |
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|
| Fix multiple vulnerabilities in `tf.raw_ops.*CountSparseOutput`. · tensorflow/tensorflow@3cbb917 · GitHub |
MISC |
github.com |
Patch, Third Party Advisory |
| Heap buffer overflow in weighted sparse count ops · Advisory · tensorflow/tensorflow · GitHub |
CONFIRM |
github.com |
Exploit, Third Party Advisory |
| Release TensorFlow 2.3.1 · tensorflow/tensorflow · GitHub |
MISC |
github.com |
Third Party Advisory |
| 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.
Legacy QID Mappings
- 980049 Python (pip) Security Update for tensorflow-gpu (GHSA-pg59-2f92-5cph)