In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors. The issue is patched in commit 8ee24e7949a203d234489f9da2c5bf45a7d5157d, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Suse | — | Upgrade tensorflow2-develUpgrade libtensorflow_framework2-gnu-openmpi2-hpcUpgrade tensorflow2_2_1_2-gnu-hpc-develUpgrade tensorflow2_2_1_2-gnu-openmpi2-hpcUpgrade tensorflow2Upgrade tensorflow2_2_1_2-gnu-openmpi2-hpc-develUpgrade tensorflow2-docUpgrade tensorflow2_2_1_2-gnu-openmpi2-hpc-docUpgrade tensorflow2-lite-develUpgrade libtensorflow_cc2-gnu-openmpi2-hpcUpgrade tensorflow2-gnu-openmpi2-hpcUpgrade tensorflow2-gnu-hpcUpgrade libtensorflow2Upgrade libtensorflow2-gnu-openmpi2-hpcUpgrade libtensorflow_cc2-gnu-hpcUpgrade libtensorflow_framework2-gnu-hpcUpgrade libtensorflow_cc2Upgrade libtensorflow_framework2Upgrade libtensorflow2-gnu-hpcUpgrade tensorflow2-liteUpgrade tensorflow2_2_1_2-gnu-hpc-docUpgrade tensorflow2_2_1_2-gnu-hpc | May 20, 2021 | Sep 25, 2020 |
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