CVE-2020-15202
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2020
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
Integer truncation in Shard API usage
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
tensorflow
- Vendor
- tensorflow
- Product
- tensorflow
- Platforms
- Unknown
- Default status
Unknown
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| < 1.15.4 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 2.0.0, < 2.0.3 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 2.1.0, < 2.1.2 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 2.2.0, < 2.2.1 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 2.3.0, < 2.3.1 | affected | Unavailable | Unavailable | Unavailable | None listed |