NULL Pointer Dereference Affecting tensorflow/tensorflow package, versions [,1.15.4)[2.0.0,2.0.3)[2.1.0,2.1.2)[2.2.0,2.2.1)[2.3.0,2.3.1)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about NULL Pointer Dereference vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-UNMANAGED-TENSORFLOWTENSORFLOW-2333466
- published12 Jan 2022
- disclosed25 Sept 2020
- creditUnknown
Introduced: 25 Sep 2020
CVE-2020-15204 (opens in a new tab)How to fix?
Upgrade tensorflow/tensorflow to version 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1 or higher.
Overview
Affected versions of this package are vulnerable to NULL Pointer Dereference. 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.