Vulnerabilities · 2020 · Google
CVE-2020-15201
Google Tensorflow vulnerability
In Tensorflow before version 2.3.1, the `RaggedCountSparseOutput` implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the `splits` tensor generate a valid partitioning of the `values` tensor. Hence, the code is prone to heap buffer overflow. If `split_values` does not end with a value at least `num_values` then the `while` loop condition will trigger a read outside of the bounds of `split_values` once `batch_idx` grows too large. 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-p5f8-gfw5-33w4 · Exploit
- nvd.nist.gov/vuln/detail/CVE-2020-15201
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-281.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-316.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-124.yaml
- github.com/advisories/GHSA-p5f8-gfw5-33w4
- nvd.nist.gov/vuln/detail/CVE-2020-15201
- cve.org/CVERecord?id=CVE-2020-15201
More vulnerabilities in Google products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.