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.
CVSS Details
- CVSS 3.1 Base Score: 5.3
- CVSS 3.1 Vector: (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L)
Covered by Rapid7
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Suse | — | Upgrade libtensorflow2Upgrade tensorflow2_2_1_2-gnu-openmpi2-hpcUpgrade tensorflow2_2_1_2-gnu-openmpi2-hpc-docUpgrade tensorflow2-gnu-hpcUpgrade tensorflow2-liteUpgrade tensorflow2-develUpgrade libtensorflow_framework2-gnu-openmpi2-hpcUpgrade tensorflow2Upgrade libtensorflow_cc2-gnu-openmpi2-hpcUpgrade libtensorflow2-gnu-openmpi2-hpcUpgrade libtensorflow_framework2-gnu-hpcUpgrade tensorflow2_2_1_2-gnu-hpcUpgrade tensorflow2_2_1_2-gnu-openmpi2-hpc-develUpgrade libtensorflow_framework2Upgrade libtensorflow_cc2Upgrade tensorflow2_2_1_2-gnu-hpc-develUpgrade tensorflow2_2_1_2-gnu-hpc-docUpgrade tensorflow2-gnu-openmpi2-hpcUpgrade tensorflow2-lite-develUpgrade libtensorflow2-gnu-hpcUpgrade libtensorflow_cc2-gnu-hpcUpgrade tensorflow2-doc | May 22, 2021 | Sep 25, 2020 |
Prioritise with Active Threat Intelligence
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub