CONTENTUM.COMA specialist. A plan. A result.

Vulnerabilities · 2020 · Google

CVE-2020-15191
Google Tensorflow vulnerability

In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to `dlpack.to_dlpack` the expected validations will cause variables to bind to `nullptr` while setting a `status` variable to the error condition. However, this `status` argument is not properly checked. Hence, code following these methods will bind references to null pointers. This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. The issue is patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8 and is released in TensorFlow versions 2.2.1, or 2.3.1.

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.