Vulnerabilities · 2020 · Google
CVE-2020-15198
Google Tensorflow vulnerability
In Tensorflow before version 2.3.1, the `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has the same shape as the `values` one. The values in these tensors are always accessed in parallel. Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1.
Affected products
Tensorflow. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Google Tensorflow runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02 · Patch
- github.com/tensorflow/tensorflow/releases/tag/v2.3.1 · Third Party Advisory
- github.com/tensorflow/tensorflow/security/advisories/GHSA-jc87-6vpp-7ff3 · Exploit
- nvd.nist.gov/vuln/detail/CVE-2020-15198
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-278.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-313.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-121.yaml
- github.com/advisories/GHSA-jc87-6vpp-7ff3
- nvd.nist.gov/vuln/detail/CVE-2020-15198
- cve.org/CVERecord?id=CVE-2020-15198
More vulnerabilities in Google products
CVE-2026-28615CVE-2026-28587CVE-2026-28576CVE-2026-28575CVE-2026-20418CVE-2026-20417CVE-2026-20415CVE-2026-20414All 12,443
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.