Vulnerability in Google Tensorflow
CVE-2020-15193
In Tensorflow before versions 2.2.1 and 2.3.1, the implementation of `dlpack.to_dlpack` can be made to use uninitialized memory resulting in further memory corruption. This is because the pybind11 glue code assumes that the argument is a tensor. However, there is nothing stopping users from passing in a Python object instead of a tensor. The uninitialized memory address is due to a `reinterpret_cast` Since the `PyObject` is a Python object, not a TensorFlow Tensor, the cast to `EagerTensor` fails. The issue is patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8 and is released in TensorFlow versions 2.2.1, or 2.3.1.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.1 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L.
EPSS exploit prediction
EPSS 0.008, 58.1th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Google Tensorflow — versions 2.2.0, 2.3.0
- Tensorflow — versions = 2.2.0, = 2.3.0
- openSUSE Leap — versions 15.2
Weakness classification (CWE)
References
- github.com/tensorflow/tensorflow/releases/tag/v2.3.1 (Third Party Advisory)
- github.com/tensorflow/tensorflow/security/advisories/GHSA-rjjg-hgv6-h69v (Exploit, Third Party Advisory)
- github.com/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8 (Patch, Third Party Advisory)
- openSUSE-SU-2020:1766 (vendor-advisory, Mailing List, Third Party Advisory)