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.
2020-09-25T19:15:15.713
2024-11-21T05:05:04.787
Modified
CVSSv3.1: 5.3 (MEDIUM)
AV:N/AC:L/Au:N/C:N/I:N/A:P
10.0
2.9
Type | Vendor | Product | Version/Range | Vulnerable? |
---|---|---|---|---|
Application | tensorflow | < 1.15.4 | Yes | |
Application | tensorflow | < 2.0.3 | Yes | |
Application | tensorflow | < 2.1.2 | Yes | |
Application | tensorflow | < 2.2.1 | Yes | |
Application | tensorflow | < 2.3.1 | Yes | |
Operating System | opensuse | leap | 15.2 | Yes |