Improper input validation in Google Tensorflow
CVE-2020-15192
In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes a list of strings to `dlpack.to_dlpack` there is a memory leak following an expected validation failure. The issue occurs because the `status` argument during validation failures is not properly checked. Since each of the above methods can return an error status, the `status` value must be checked before continuing. The issue is patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8 and is released in TensorFlow versions 2.2.1, or 2.3.1.
Vulnerability class: Drupalgeddon 2 (CVE-2018-7600)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L.
EPSS exploit prediction
EPSS 0.008, 58.2th 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)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (graphene-security/graphene-sample-data). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- github.com/tensorflow/tensorflow/releases/tag/v2.3.1 (Third Party Advisory)
- github.com/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8 (Patch, Third Party Advisory)
- github.com/tensorflow/tensorflow/security/advisories/GHSA-8fxw-76px-3rxv (Exploit, Third Party Advisory)
- openSUSE-SU-2020:1766 (vendor-advisory, Mailing List, Third Party Advisory)