CVE-2022-41910 Heap out of bounds read in `QuantizeAndDequantizeV2` in Tensorflow
An attacker can trigger a heap out-of-bounds read in TensorFlow's QuantizeAndDequantizeV2 operation, causing a crash or potential information disclosure.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2022-41910?
CVE-2022-41910 is a medium-severity memory corruption vulnerability in Google Tensorflow, published on 6 Dec 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
TensorFlow is an open source platform for machine learning. The function MakeGrapplerFunctionItem takes arguments that determine the sizes of inputs and outputs. If the inputs given are greater than or equal to the sizes of the outputs, an out-of-bounds memory read or a crash is triggered. We have patched the issue in GitHub commit a65411a1d69edfb16b25907ffb8f73556ce36bb7. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.8.4, 2.9.3, and 2.10.1.
Weakness: CWE-125
Which versions are affected by CVE-2022-41910?
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.8.4, 2.9.3, 2.10.1 |
tensorflow PyPI | All versions | 2.8.4, 2.9.3, 2.10.1 |
tensorflow PyPI | All versions | 2.8.4 |
tensorflow PyPI | All versions | 2.8.4 |
tensorflow PyPI | From 2.10.0 | 2.10.1 |
tensorflow PyPI | From 2.10.0 | 2.10.1 |
16 more packages
tensorflow PyPI | From 2.9.0 | 2.9.3 |
tensorflow PyPI | From 2.9.0 | 2.9.3 |
tensorflow-cpu PyPI | All versions | 2.8.4, 2.9.3, 2.10.1 |
tensorflow-cpu PyPI | All versions | 2.8.4 |
tensorflow-cpu PyPI | All versions | 2.8.4 |
tensorflow-cpu PyPI | From 2.10.0 | 2.10.1 |
tensorflow-cpu PyPI | From 2.10.0 | 2.10.1 |
tensorflow-cpu PyPI | From 2.9.0 | 2.9.3 |
tensorflow-cpu PyPI | From 2.9.0 | 2.9.3 |
tensorflow-gpu PyPI | All versions | 2.8.4, 2.9.3, 2.10.1 |
tensorflow-gpu PyPI | All versions | 2.8.4 |
tensorflow-gpu PyPI | All versions | 2.8.4 |
tensorflow-gpu PyPI | From 2.10.0 | 2.10.1 |
tensorflow-gpu PyPI | From 2.10.0 | 2.10.1 |
tensorflow-gpu PyPI | From 2.9.0 | 2.9.3 |
tensorflow-gpu PyPI | From 2.9.0 | 2.9.3 |
Products include Google Tensorflow.
How do I fix CVE-2022-41910?
Upgrade tensorflow to a fixed version for your release line: 2.8.4, 2.9.3 or 2.10.1.
Upgrade to the fixed version. Memory-safe languages, compiler hardening and fuzzing prevent most new cases. More about Memory corruption.
Is CVE-2022-41910 being exploited?
There is no known exploitation of CVE-2022-41910 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-41910, GHSA-frqp-wp83-qggv, PYSEC-2026-3178, PYSEC-2026-3323, PYSEC-2026-992.