Vulnerability record · CVE-2020-15190 · published 25 September 2020
CVE-2020-15190: Google tensorflow improper input validation vulnerability
Google · Tensorflow
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `tf.raw_ops.Switch` operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. However, the eager runtime traverses all tensors in the output. Since only one of the tensors is defined, the other one is `nullptr`, hence we are binding a reference to `nullptr`. This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. In this case, this results in a segmentation fault The issue is patched in commit da8558533d925694483d2c136a9220d6d49d843c, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
Description
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `tf.raw_ops.Switch` operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. However, the eager runtime traverses all tensors in the output. Since only one of the tensors is defined, the other one is `nullptr`, hence we are binding a reference to `nullptr`. This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. In this case, this results in a segmentation fault The issue is patched in commit da8558533d925694483d2c136a9220d6d49d843c, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Affected products
2 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html | Mailing ListThird Party Advisory |
| https://github.com/tensorflow/tensorflow/commit/da8558533d925694483d2c136a9220d6d49d843c | PatchThird Party Advisory |
| https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 | Third Party Advisory |
| https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4g9f-63rx-5cw4 | ExploitThird Party Advisory |
| http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html | Mailing ListThird Party Advisory |
| https://github.com/tensorflow/tensorflow/commit/da8558533d925694483d2c136a9220d6d49d843c | PatchThird Party Advisory |
| https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1 | Third Party Advisory |
| https://github.com/tensorflow/tensorflow/security/advisories/GHSA-4g9f-63rx-5cw4 | ExploitThird Party Advisory |
Track CVE-2020-15190 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2020-15190), CISA KEV, FIRST EPSS (scores of 2026-11-18). This page is refreshed as NVD updates the record.