CVE-2020-15203
Description
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.
Predictions
Heuristic predictions, AS-IS, for prioritization only.
Mitigations
No mitigations published for this CVE yet.
The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or — if you've already worked around this in production — publish your fix to the community-verified tier.
✚ Propose a mitigation on Community → Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here withsource_tier=community-verified.
OS impact
Debian Fixed 2 releases
| Version | Status | Fixed in |
|---|---|---|
| sid | Fixed | 0 |
| forky | Fixed | 0 |
Package impact
| Ecosystem | Package | Vulnerable | Fixed |
|---|---|---|---|
| PyPI | tensorflow | <1.15.4 | 1.15.4 |
| PyPI | tensorflow | >=2.0.0,<2.0.3 | 2.0.3 |
| PyPI | tensorflow | >=2.1.0,<2.1.2 | 2.1.2 |
| PyPI | tensorflow | >=2.2.0,<2.2.1 | 2.2.1 |
| PyPI | tensorflow | >=2.3.0,<2.3.1 | 2.3.1 |
| PyPI | tensorflow-cpu | <1.15.4 | 1.15.4 |
| PyPI | tensorflow-cpu | >=2.0.0,<2.0.3 | 2.0.3 |
| PyPI | tensorflow-cpu | >=2.1.0,<2.1.2 | 2.1.2 |
| PyPI | tensorflow-cpu | >=2.2.0,<2.2.1 | 2.2.1 |
| PyPI | tensorflow-cpu | >=2.3.0,<2.3.1 | 2.3.1 |
| PyPI | tensorflow-gpu | <1.15.4 | 1.15.4 |
| PyPI | tensorflow-gpu | >=2.0.0,<2.0.3 | 2.0.3 |
| PyPI | tensorflow-gpu | >=2.1.0,<2.1.2 | 2.1.2 |
| PyPI | tensorflow-gpu | >=2.2.0,<2.2.1 | 2.2.1 |
| PyPI | tensorflow-gpu | >=2.3.0,<2.3.1 | 2.3.1 |
| PyPI | tensorflow-cpu | <33be22c65d86256e6826666662e40dbdfe70ee83||>=2.3.0,<2.3.1 | 33be22c65d86256e6826666662e40dbdfe70ee83 |
| PyPI | tensorflow | <33be22c65d86256e6826666662e40dbdfe70ee83||>=2.3.0,<2.3.1 | 33be22c65d86256e6826666662e40dbdfe70ee83 |
| PyPI | tensorflow-gpu | <33be22c65d86256e6826666662e40dbdfe70ee83||>=2.3.0,<2.3.1 | 33be22c65d86256e6826666662e40dbdfe70ee83 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xmq7-7fxm-rr79
- https://nvd.nist.gov/vuln/detail/CVE-2020-15203
- https://github.com/tensorflow/tensorflow/commit/33be22c65d86256e6826666662e40dbdfe70ee83
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-283.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-318.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-126.yaml
- https://github.com/tensorflow/tensorflow
- https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1
- http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html
- https://security-tracker.debian.org/tracker/CVE-2020-15203
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.