CVE-2022-23587High· 8.8▾ TwilightInteger overflow in TensorFlow
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 48.4 · likelihood 0.2 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 13.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.9%
0.9% → 0.9%
Under certain scenarios, Grappler component of TensorFlow is vulnerable to an integer overflow during cost estimation for crop and resize. Since the cropping parameters are user controlled, a malicious person can trigger undefined behavior.
We have patched the issue in GitHub commit 0aaaae6eca5a7175a193696383f582f53adab23f.
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
tensorflow < 2.5.3tensorflow >= 2.6.0, < 2.6.3tensorflow >= 2.7.0, < 2.7.1tensorflow-cpu < 2.5.3tensorflow-cpu >= 2.6.0, < 2.6.3tensorflow-cpu >= 2.7.0, < 2.7.1tensorflow-gpu < 2.5.3tensorflow-gpu >= 2.6.0, < 2.6.3tensorflow-gpu >= 2.7.0, < 2.7.1Upgrade to a patched release:
tensorflow 2.5.3tensorflow 2.6.3tensorflow 2.7.1tensorflow-cpu 2.5.3tensorflow-cpu 2.6.3tensorflow-cpu 2.7.1tensorflow-gpu 2.5.3tensorflow-gpu 2.6.3tensorflow-gpu 2.7.1Connected by shared product, vendor, weakness, or advisory.
CVE-2021-29541Low· 2.5Null pointer dereference in `StringNGrams`
CVE-2021-29525Low· 2.5Division by 0 in `Conv2DBackpropInput`
CVE-2021-29527Low· 2.5Division by 0 in `QuantizedConv2D`
CVE-2021-29524Low· 2.5Division by 0 in `Conv2DBackpropFilter`
CVE-2020-15207High· 8.7Segfault and data corruption in tensorflow-lite
CVE-2021-29535Low· 2.5Heap buffer overflow in `QuantizedMul`