Vulnerability in Google Tensorflow

CVE-2020-15202

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.

Published · last modified .

CVSS v3 metric

CVSS v3 base score 9.0 (Critical). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.013 (69.0th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 69th percentile — 69.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2020-15202: held from 0.013 to 0.013.

EPSS over last 30 days · oldest: 0.013 · newest: 0.013 · change: 0.000

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2020-15202?
CVE-2020-15202 is a critical-severity vulnerability in Google Tensorflow, classified under CWE-197. CVSS score: 9.0/10. Published 2020-09-25.
How severe is CVE-2020-15202?
Critical severity. CVSS v3 base score is 9.0 out of 10.