CVE-2020-15202
Description
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `Shard` API in TensorFlow expects the last argument to be a function taking two `int64` (i.e., `long long`) arguments. However, there are several places in TensorFlow where a lambda taking `int` or `int32` arguments is being used. In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption. The issue is patched in commits 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575, 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 | <ca8c013b5e97b1373b3bb1c97ea655e69f31a575||>=2.3.0,<2.3.1 | 27b417360cbd671ef55915e4bb6bb06af8b8a832 |
| PyPI | tensorflow | <ca8c013b5e97b1373b3bb1c97ea655e69f31a575||>=2.3.0,<2.3.1 | 27b417360cbd671ef55915e4bb6bb06af8b8a832 |
| PyPI | tensorflow-gpu | <ca8c013b5e97b1373b3bb1c97ea655e69f31a575||>=2.3.0,<2.3.1 | 27b417360cbd671ef55915e4bb6bb06af8b8a832 |
References
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-h6fg-mjxg-hqq4
- https://nvd.nist.gov/vuln/detail/CVE-2020-15202
- https://github.com/tensorflow/tensorflow/commit/27b417360cbd671ef55915e4bb6bb06af8b8a832
- https://github.com/tensorflow/tensorflow/commit/ca8c013b5e97b1373b3bb1c97ea655e69f31a575
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-282.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-317.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-125.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-15202
Community-verified mitigations for this CVE will appear above when contributors publish them.
Verify integrity in audit chain (admin only). AS-IS.