Segfault in Tensorflow
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `tf.raw_ops.Switch` operation takes as input a tensor and a boolean and outputs two tensors. Depending on the boolean value, one of the tensors is exactly the input tensor whereas the other one should be an empty tensor. However, the eager runtime traverses all tensors in the output. Since only one of the tensors is defined, the other one is `nullptr`, hence we are binding a reference to `nullptr`. This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. In this case, this results in a segmentation fault The issue is patched in commit da8558533d925694483d2c136a9220d6d49d843c, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
Timeline
- CVE published
- Record last updated
Affected versions
- tensorflow tensorflow
fixed in 1.15.4; From 2.0.0 · fixed in 2.0.3; From 2.1.0 · fixed in 2.1.2; From 2.2.0 · fixed in 2.2.1; From 2.3.0 · fixed in 2.3.1
- tensorflow-gpuPyPI
fixed in 1.15.4; From 2.0.0 · fixed in 2.0.3; From 2.1.0 · fixed in 2.1.2; From 2.2.0 · fixed in 2.2.1; From 2.3.0 · fixed in 2.3.1
- tensorflowPyPI
fixed in 1.15.4; From 2.0.0 · fixed in 2.0.3; From 2.1.0 · fixed in 2.1.2; From 2.2.0 · fixed in 2.2.1; From 2.3.0 · fixed in 2.3.1
- tensorflow-cpuPyPI
fixed in 1.15.4; From 2.0.0 · fixed in 2.0.3; From 2.1.0 · fixed in 2.1.2; From 2.2.0 · fixed in 2.2.1; From 2.3.0 · fixed in 2.3.1
- tensorflowPyPI
fixed in 1.15.4
- tensorflowPyPI
From 2.0.0 · fixed in 2.0.3
- tensorflowPyPI
From 2.1.0 · fixed in 2.1.2
- tensorflowPyPI
From 2.2.0 · fixed in 2.2.1
- tensorflowPyPI
From 2.3.0 · fixed in 2.3.1
- tensorflow-cpuPyPI
fixed in 1.15.4
- tensorflow-cpuPyPI
From 2.0.0 · fixed in 2.0.3
- tensorflow-cpuPyPI
From 2.1.0 · fixed in 2.1.2
- tensorflow-cpuPyPI
From 2.2.0 · fixed in 2.2.1
- tensorflow-cpuPyPI
From 2.3.0 · fixed in 2.3.1
- tensorflow-gpuPyPI
fixed in 1.15.4
- tensorflow-gpuPyPI
From 2.0.0 · fixed in 2.0.3
- tensorflow-gpuPyPI
From 2.1.0 · fixed in 2.1.2
- tensorflow-gpuPyPI
From 2.2.0 · fixed in 2.2.1
- tensorflow-gpuPyPI
From 2.3.0 · fixed in 2.3.1