CVE-2020-15193CWE-908

Memory corruption in Tensorflow

High · published September 25, 2020

CVSS v3.1
7.1
EPSS
1%
Percentile
57.1
In the wild
Unconfirmed
What it is

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.

The record
Technical detail
CVSS v3.1
7.1 · HIGH
Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
CVSS v4.0
Not supplied
EPSS
0.00830 · 57.1th percentile
Weakness
CWE-908 · Use of Uninitialized Resource
Published
2020-09-25T18:40Z
EPSS history
Timeline
  • 25 SEP 18:40Z
    Memory corruption in Tensorflow
    cvelistv5