Vulnerabilities · 2020 · Google
CVE-2020-15200
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. Thus, the code sets up conditions to cause a heap buffer overflow. A `BatchedMap` is equivalent to a vector where each element is a hashmap. However, if the first element of `splits_values` is not 0, `batch_idx` will never be 1, hence there will be no hashmap at index 0 in `per_batch_counts`. Trying to access that in the user code results in a segmentation fault. 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-x7rp-74x2-mjf3 · Exploit
- nvd.nist.gov/vuln/detail/CVE-2020-15200
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-280.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-315.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-123.yaml
- github.com/advisories/GHSA-x7rp-74x2-mjf3
- nvd.nist.gov/vuln/detail/CVE-2020-15200
- cve.org/CVERecord?id=CVE-2020-15200
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.