CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2020 · Google

CVE-2020-15202
Google Tensorflow vulnerability

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.

High priority: this vulnerability is rated critical and can be attacked over the network without a login.

Affected products

Tensorflow, Leap. The exact versions are in the references.

What to do now

  • Check your exposureFind out whether Google Tensorflow runs anywhere in your environment, including systems of suppliers.
  • UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
  • Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.

References

More vulnerabilities in Google products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.