CVE-2022-23571: Reachable Assertion in Tensorflow
First published: Fri Feb 04 2022(Updated: )
### Impact When decoding a tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments, if the tensors have an invalid `dtype` and 0 elements or an invalid shape. This allows attackers to cause denial of services in TensorFlow processes. ### Patches We have patched the issue in GitHub commit [5b491cd5e41ad63735161cec9c2a568172c8b6a3](https://github.com/tensorflow/tensorflow/commit/5b491cd5e41ad63735161cec9c2a568172c8b6a3). 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.
Credit: security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| pip/tensorflow-gpu | =2.7.0 | 2.7.1 |
| pip/tensorflow-gpu | >=2.6.0<2.6.3 | 2.6.3 |
| pip/tensorflow-gpu | <2.5.3 | 2.5.3 |
| pip/tensorflow-cpu | =2.7.0 | 2.7.1 |
| pip/tensorflow-cpu | >=2.6.0<2.6.3 | 2.6.3 |
| pip/tensorflow-cpu | <2.5.3 | 2.5.3 |
| pip/tensorflow | =2.7.0 | 2.7.1 |
| pip/tensorflow | >=2.6.0<2.6.3 | 2.6.3 |
| pip/tensorflow | <2.5.3 | 2.5.3 |
| TensorFlow Keras | <=2.5.2 | |
| TensorFlow Keras | >=2.6.0<=2.6.2 | |
| TensorFlow Keras | =2.7.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/tensorflow/tensorflow/commit/5b491cd5e41ad63735161cec9c2a568172c8b6a3
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-j3mj-fhpq-qqjj
- https://nvd.nist.gov/vuln/detail/CVE-2022-23571
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2022-80.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2022-135.yaml
- https://github.com/advisories/GHSA-j3mj-fhpq-qqjj (Advisory)
Frequently Asked Questions
What is the severity of CVE-2022-23571?
CVE-2022-23571 has been classified as a high severity vulnerability.
How do I fix CVE-2022-23571?
To fix CVE-2022-23571, you should upgrade TensorFlow to version 2.7.1 or later.
Which versions of TensorFlow are affected by CVE-2022-23571?
TensorFlow versions prior to 2.6.3, between 2.6.0 and 2.6.2, and 2.7.0 are affected by CVE-2022-23571.
What kind of vulnerability is CVE-2022-23571?
CVE-2022-23571 is a denial of service vulnerability caused by invalid tensor operations.
Is there a patch for CVE-2022-23571?
Yes, a patch is available in TensorFlow version 2.7.1 and subsequent updates.
- agent/type
- agent/remedy
- collector/mitre-cve
- source/MITRE
- agent/weakness
- agent/title
- agent/severity
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-j3mj-fhpq-qqjj
- alias/CVE-2022-23571
- agent/software-canonical-lookup
- agent/references
- agent/last-modified-date
- agent/description
- agent/softwarecombine
- agent/event
- agent/author
- collector/github-advisory
- agent/trending
- agent/source
- agent/tags
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-index
- package-manager/pip
- vendor/google
- canonical/tensorflow keras
- version/tensorflow keras/2.5.2
- version/tensorflow keras/2.6.0
- version/tensorflow keras/2.6.2
- version/tensorflow keras/2.7.0