NULL pointer dereference in Google Tensorflow

CVE-2020-15191

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.

Vulnerability class: Drupalgeddon 2 (CVE-2018-7600)

EPSS: 0.009 (56.0th percentile) — read the EPSS interpretation.

CVSS v3 metric

CVSS v3 base score 5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2020-15191?
CVE-2020-15191 is a medium-severity vulnerability in Google Tensorflow, classified under Improper Input Validation. CVSS score: 5.3/10. Published 2020-09-25.
How severe is CVE-2020-15191?
Medium severity. CVSS v3 base score is 5.3 out of 10.