NULL pointer dereference in Google Tensorflow
CVE-2020-15204
In eager mode, TensorFlow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1 does not set the session state. Hence, calling `tf.raw_ops.GetSessionHandle` or `tf.raw_ops.GetSessionHandleV2` results in a null pointer dereference In linked snippet, in eager mode, `ctx->session_state()` returns `nullptr`. Since code immediately dereferences this, we get a segmentation fault. The issue is patched in commit 9a133d73ae4b4664d22bd1aa6d654fec13c52ee1, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
Published · last modified .
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.
EPSS exploit prediction
EPSS 0.009, 60.3th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Google Tensorflow
- Tensorflow — versions < 1.15.4, >= 2.0.0, < 2.0.3, >= 2.1.0, < 2.1.2
- 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-q8gv-q7wr-9jf8 (Exploit, Third Party Advisory)
- github.com/tensorflow/tensorflow/commit/9a133d73ae4b4664d22bd1aa6d654fec13c52ee1 (Patch, Third Party Advisory)
- openSUSE-SU-2020:1766 (vendor-advisory, Mailing List, Third Party Advisory)