CVE-2022-23591 Stack overflow in Tensorflow
Attackers can cause a stack overflow and denial of service by loading a maliciously crafted SavedModel with self-recursive functions in TensorFlow.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-23591?
CVE-2022-23591 is a high-severity denial of service vulnerability in Google Tensorflow, published on 4 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Tensorflow is an Open Source Machine Learning Framework. The `GraphDef` format in TensorFlow does not allow self recursive functions. The runtime assumes that this invariant is satisfied. However, a `GraphDef` containing a fragment such as the following can be consumed when loading a `SavedModel`. This would result in a stack overflow during execution as resolving each `NodeDef` means resolving the function itself and its nodes. 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.
Which versions are affected by CVE-2022-23591?
22 open source packages ship an affected version, including tensorflow, tensorflow-cpu and tensorflow-gpu. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
tensorflow Bitnami | All versions | 2.5.3, 2.6.3, 2.7.1 |
tensorflow PyPI | All versions | 2.5.3, 2.6.3, 2.7.1 |
tensorflow PyPI | All versions | 2.5.3 |
tensorflow PyPI | All versions | 2.5.3 |
tensorflow PyPI | From 2.6.0 | 2.6.3 |
tensorflow PyPI | From 2.6.0 | 2.6.3 |
16 more packages
tensorflow PyPI | From 2.7.0 | 2.7.1 |
tensorflow PyPI | From 2.7.0 | 2.7.1 |
tensorflow-cpu PyPI | All versions | 2.5.3, 2.6.3 |
tensorflow-cpu PyPI | All versions | 2.5.3 |
tensorflow-cpu PyPI | All versions | 2.5.3 |
tensorflow-cpu PyPI | From 2.6.0 | 2.6.3 |
tensorflow-cpu PyPI | From 2.6.0 | 2.6.3 |
tensorflow-cpu PyPI | From 2.7.0 | 2.7.1 |
tensorflow-cpu PyPI | From 2.7.0 | 2.7.1 |
tensorflow-gpu PyPI | All versions | 2.5.3, 2.6.3 |
tensorflow-gpu PyPI | All versions | 2.5.3 |
tensorflow-gpu PyPI | All versions | 2.5.3 |
tensorflow-gpu PyPI | From 2.6.0 | 2.6.3 |
tensorflow-gpu PyPI | From 2.6.0 | 2.6.3 |
tensorflow-gpu PyPI | From 2.7.0 | 2.7.1 |
tensorflow-gpu PyPI | From 2.7.0 | 2.7.1 |
Products include Google Tensorflow.
How do I fix CVE-2022-23591?
Upgrade tensorflow to a fixed version for your release line: 2.5.3, 2.6.3 or 2.7.1.
Upgrade, then put limits on request size, rate and nesting depth so one client cannot exhaust the service. More about Denial of service.
Is CVE-2022-23591 being exploited?
There is no known exploitation of CVE-2022-23591 in the wild and no public exploit code.
Other vulnerabilities in Google Tensorflow
- CVE-2023-25668 TensorFlow vulnerable to heap out-of-buffer read in the QuantizeAndDequantize operation
- CVE-2018-7575 Integer Overflow or Wraparound in Google TensorFlow
- CVE-2021-37678 Arbitrary code execution due to YAML deserialization
- CVE-2021-35958 Path traversal in n/a
- CVE-2020-15202 Integer truncation in Shard API usage
Sources
Also known as BIT-tensorflow-2022-23591, GHSA-247x-2f9f-5wp7, PYSEC-2022-100, PYSEC-2022-155, PYSEC-2026-3084.