Vulnerabilities · 2020 · Google
CVE-2020-15203
Google Tensorflow vulnerability
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, by controlling the `fill` argument of tf.strings.as_string, a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a `printf` call is constructed. This may result in segmentation fault. The issue is patched in commit 33be22c65d86256e6826666662e40dbdfe70ee83, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
Affected products
Tensorflow, Leap. 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/33be22c65d86256e6826666662e40dbdfe70ee83 · Patch
- lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html · Third Party Advisory
- github.com/tensorflow/tensorflow/releases/tag/v2.3.1 · Third Party Advisory
- github.com/tensorflow/tensorflow/security/advisories/GHSA-xmq7-7fxm-rr79 · Exploit
- nvd.nist.gov/vuln/detail/CVE-2020-15203
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-283.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-318.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-126.yaml
- nvd.nist.gov/vuln/detail/CVE-2020-15203
- cve.org/CVERecord?id=CVE-2020-15203
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.