Integer overflows in Tensorflow
High6.5CVE-2022-23568 · Published Feb 9, 2022 · updated Sep 10, 2026
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI | < 2.5.3 | 2.5.3 |
| >= 2.6.0, < 2.6.3 | 2.6.3 | |
| >= 2.7.0, < 2.7.1 | 2.7.1 |
Details and references
### Impact The [implementation of `AddManySparseToTensorsMap`](https://github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/sparse_tensors_map_ops.cc) is vulnerable to an integer overflow which results in a `CHECK`-fail when building new `TensorShape` objects (so, an assert failure based denial of service): ```python import tensorflow as tf import numpy as np tf.raw_ops.AddManySparseToTensorsMap( sparse_indices=[(0,0),(0,1),(0,2),(4,3),(5,0),(5,1)], sparse_values=[1,1,1,1,1,1], sparse_shape=[2**32,2**32], container='', shared_name='', name=None) ``` We are missing some validation on the shapes of the input tensors as well as directly constructing a large `TensorShape` with user-provided dimensions. The latter is an instance of [TFSA-2021-198](https://github.com/tensorflow/tensorflow/blob/master/tensorflow/security/advisory/tfsa-2021-198.md) (CVE-2021-41197) and is easily fixed by replacing a call to `TensorShape` constructor with a call to `BuildTensorShape` static helper factory. ### Patches We have patched the issue in GitHub commits [b51b82fe65ebace4475e3c54eb089c18a4403f1c](https://github.com/tensorflow/tensorflow/commit/b51b82fe65ebace4475e3c54eb089c18a4403f1c) and [a68f68061e263a88321c104a6c911fe5598050a8](https://github.com/tensorflow/tensorflow/commit/a68f68061e263a88321c104a6c911fe5598050a8). 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. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by Faysal Hossain Shezan from University of Virginia.
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-190
- Also known as
- BIT-tensorflow-2022-23568, CVE-2022-23568, PYSEC-2022-132, PYSEC-2022-77, PYSEC-2026-3114
- github.com/tensorflow/tensorflow/security/advisories/GHSA-6445-fm66-fvq2
- nvd.nist.gov/vuln/detail/CVE-2022-23568
- github.com/tensorflow/tensorflow/commit/a68f68061e263a88321c104a6c911fe5598050a8
- github.com/tensorflow/tensorflow/commit/b51b82fe65ebace4475e3c54eb089c18a4403f1c
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2022-77.yaml
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2022-132.yaml
- github.com/tensorflow/tensorflow
- github.com/tensorflow/tensorflow/blob/5100e359aef5c8021f2e71c7b986420b85ce7b3d/tensorflow/core/kernels/sparse_tensors_map_ops.cc
More TensorFlow advisories
All TensorFlow| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Feb 92022 | Out of bounds read in Tensorflow CVE-2022-21726High8.1fixed in 2.5.3, 2.6.3, 2.7.1 | High8.1 | 2.5.3, 2.6.3, 2.7.1 |
| Feb 92022 | Integer overflow in Tensorflow CVE-2022-21727High7.6fixed in 2.5.3, 2.6.3, 2.7.1 | High7.6 | 2.5.3, 2.6.3, 2.7.1 |
| Feb 92022 | Out of bounds read in Tensorflow CVE-2022-21728High8.1fixed in 2.5.3, 2.6.3, 2.7.1 | High8.1 | 2.5.3, 2.6.3, 2.7.1 |
| Feb 92022 | Out of bounds read in Tensorflow CVE-2022-21730High8.1fixed in 2.5.3, 2.6.3, 2.7.1 | High8.1 | 2.5.3, 2.6.3, 2.7.1 |
| Feb 92022 | Out of bounds read and write in Tensorflow CVE-2022-23574High8.8fixed in 2.5.3, 2.6.3, 2.7.1 | High8.8 | 2.5.3, 2.6.3, 2.7.1 |
| Feb 92022 | Memory leak in decoding PNG images CVE-2022-23585Medium4.3fixed in 2.5.3, 2.6.3, 2.7.1 | Medium4.3 | 2.5.3, 2.6.3, 2.7.1 |