Segfault in Tensorflow
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
2.3.1| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
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.
From the CVE record · GitHub_M
In eager mode, TensorFlow does not set session state, so calling tf.raw_ops.GetSessionHandle or tf.raw_ops.GetSessionHandleV2 causes a null pointer dereference and crash. The input does not establish whether an attacker can trigger this over a network or whether authentication or user interaction is required.
Check installations of the PyPI tensorflow, tensorflow-cpu, and tensorflow-gpu packages running versions before 1.15.4, 2.0.0–2.0.2, 2.1.0–2.1.1, 2.2.0, or 2.3.0.