CVE-2022-23564: Reachable Assertion in Tensorflow
First published: Fri Feb 04 2022(Updated: )
### Impact When decoding a resource handle tensor from protobuf, a TensorFlow process can encounter cases where a `CHECK` assertion is invalidated based on user controlled arguments. This allows attackers to cause denial of services in TensorFlow processes. ### Patches We have patched the issue in GitHub commit [14fea662350e7c26eb5fe1be2ac31704e5682ee6](https://github.com/tensorflow/tensorflow/commit/14fea662350e7c26eb5fe1be2ac31704e5682ee6). 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/14fea662350e7c26eb5fe1be2ac31704e5682ee6
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-8rcj-c8pj-v3m3
- https://nvd.nist.gov/vuln/detail/CVE-2022-23564
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2022-73.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2022-128.yaml
- https://github.com/advisories/GHSA-8rcj-c8pj-v3m3 (Advisory)
Frequently Asked Questions
What is the severity of CVE-2022-23564?
CVE-2022-23564 has been classified as a denial of service vulnerability affecting TensorFlow.
How do I fix CVE-2022-23564?
To resolve CVE-2022-23564, upgrade TensorFlow to version 2.5.3, 2.6.3, or 2.7.1 or higher.
What affects CVE-2022-23564?
CVE-2022-23564 affects TensorFlow versions up to 2.5.2, between 2.6.0 and 2.6.2, and the specific version 2.7.0.
What is the impact of CVE-2022-23564?
The impact of CVE-2022-23564 is that it can lead to denial of service in TensorFlow processes due to invalidated CHECK assertions.
Who is responsible for fixing CVE-2022-23564?
The maintainers of TensorFlow, specifically Google, are responsible for addressing CVE-2022-23564 by issuing patches.
- 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-8rcj-c8pj-v3m3
- alias/CVE-2022-23564
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/author
- agent/references
- agent/description
- agent/event
- agent/softwarecombine
- 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