CVE-2020-15196
Heap buffer overflow in Tensorflow
Einstufung nach Quelle
Trivys eigenes Label ist CRITICAL. Kritisch laut NVD, Bitnami. Niedriger laut GHSA (mittel).
Beschreibung
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.
Betroffene Pakete und behobene Versionen
| Quelle | Paket | Behoben in |
|---|---|---|
| bitnami::Bitnami Vulnerability Database | tensorflow | 2.3.1 |
| pip::GitHub Security Advisory pip | tensorflow, tensorflow-cpu, tensorflow-gpu | 2.3.1 |
Alle 4 Einträge aus 2 Quellen zeigen
| Quelle | Paket | Behoben in |
|---|---|---|
| bitnami::Bitnami Vulnerability Database | tensorflow | 2.3.1 |
| pip::GitHub Security Advisory pip | tensorflow | 2.3.1 |
| pip::GitHub Security Advisory pip | tensorflow-cpu | 2.3.1 |
| pip::GitHub Security Advisory pip | tensorflow-gpu | 2.3.1 |
Referenzen
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-276.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-311.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-119.yaml
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02
- https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cph
- https://nvd.nist.gov/vuln/detail/CVE-2020-15196