`CHECK`-failures in binary ops in Tensorflow
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Denial of service
- Confidentiality · integrity · availability
- None · None · High
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-617.
Summary
Tensorflow is an Open Source Machine Learning Framework. A malicious user can cause a denial of service by altering a `SavedModel` such that any binary op would trigger `CHECK` failures. This occurs when the protobuf part corresponding to the tensor arguments is modified such that the `dtype` no longer matches the `dtype` expected by the op. In that case, calling the templated binary operator for the binary op would receive corrupted data, due to the type confusion involved. If `Tin` and `Tout` don't match the type of data in `out` and `input_*` tensors then `flat<*>` would interpret it wrongly. In most cases, this would be a silent failure, but we have noticed scenarios where this results in a `CHECK` crash, hence a denial of service. 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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| tensorflow | 2.7.0 to before 2.7.1; 2.6.0 to before 2.6.3; before 2.5.3 | 2.7.1, 2.6.3, 2.5.3 | Patch available | CNA | |
| — | tensorflow (PyPI) | before 2.5.3 | 2.5.3 | Patch available | GHSA-gjqc-q9g6-q2j3 |
| — | tensorflow (PyPI) | 2.6.0 to before 2.6.3 | 2.6.3 | Patch available | GHSA-gjqc-q9g6-q2j3 |
| — | tensorflow (PyPI) | 2.7.0 to before 2.7.1 | 2.7.1 | Patch available | GHSA-gjqc-q9g6-q2j3 |
| — | tensorflow-cpu (PyPI) | before 2.5.3 | 2.5.3 | Patch available | GHSA-gjqc-q9g6-q2j3 |
| — | tensorflow-cpu (PyPI) | 2.6.0 to before 2.6.3 | 2.6.3 | Patch available | GHSA-gjqc-q9g6-q2j3 |
| — | tensorflow-cpu (PyPI) | 2.7.0 to before 2.7.1 | 2.7.1 | Patch available | GHSA-gjqc-q9g6-q2j3 |
| — | tensorflow-gpu (PyPI) | before 2.5.3 | 2.5.3 | Patch available | GHSA-gjqc-q9g6-q2j3 |
| — | tensorflow-gpu (PyPI) | 2.6.0 to before 2.6.3 | 2.6.3 | Patch available | GHSA-gjqc-q9g6-q2j3 |
| — | tensorflow-gpu (PyPI) | 2.7.0 to before 2.7.1 | 2.7.1 | Patch available | GHSA-gjqc-q9g6-q2j3 |
- tensorflow VendorGoogle Affected 2.7.0 to before 2.7.1; 2.6.0 to before 2.6.3; before 2.5.3 Fixed in 2.7.1, 2.6.3, 2.5.3 Patch available CNA
- tensorflow (PyPI) Vendor— Affected before 2.5.3 Fixed in 2.5.3 Patch available GHSA-gjqc-q9g6-q2j3
- tensorflow (PyPI) Vendor— Affected 2.6.0 to before 2.6.3 Fixed in 2.6.3 Patch available GHSA-gjqc-q9g6-q2j3
- tensorflow (PyPI) Vendor— Affected 2.7.0 to before 2.7.1 Fixed in 2.7.1 Patch available GHSA-gjqc-q9g6-q2j3
- tensorflow-cpu (PyPI) Vendor— Affected before 2.5.3 Fixed in 2.5.3 Patch available GHSA-gjqc-q9g6-q2j3
- tensorflow-cpu (PyPI) Vendor— Affected 2.6.0 to before 2.6.3 Fixed in 2.6.3 Patch available GHSA-gjqc-q9g6-q2j3
- tensorflow-cpu (PyPI) Vendor— Affected 2.7.0 to before 2.7.1 Fixed in 2.7.1 Patch available GHSA-gjqc-q9g6-q2j3
- tensorflow-gpu (PyPI) Vendor— Affected before 2.5.3 Fixed in 2.5.3 Patch available GHSA-gjqc-q9g6-q2j3
- tensorflow-gpu (PyPI) Vendor— Affected 2.6.0 to before 2.6.3 Fixed in 2.6.3 Patch available GHSA-gjqc-q9g6-q2j3
- tensorflow-gpu (PyPI) Vendor— Affected 2.7.0 to before 2.7.1 Fixed in 2.7.1 Patch available GHSA-gjqc-q9g6-q2j3
Remediation
- Fix · CNA tensorflow (tensorflow) Fixed in 2.7.1, 2.6.3, 2.5.3
- Fix · GHSA-gjqc-q9g6-q2j3 tensorflow (PyPI) Fixed in 2.5.3 Advisory →
- Fix · GHSA-gjqc-q9g6-q2j3 tensorflow (PyPI) Fixed in 2.6.3 Advisory →
- Fix · GHSA-gjqc-q9g6-q2j3 tensorflow (PyPI) Fixed in 2.7.1 Advisory →
- Fix · GHSA-gjqc-q9g6-q2j3 tensorflow-cpu (PyPI) Fixed in 2.5.3 Advisory →
- Fix · GHSA-gjqc-q9g6-q2j3 tensorflow-cpu (PyPI) Fixed in 2.6.3 Advisory →
- Fix · GHSA-gjqc-q9g6-q2j3 tensorflow-cpu (PyPI) Fixed in 2.7.1 Advisory →
- Fix · GHSA-gjqc-q9g6-q2j3 tensorflow-gpu (PyPI) Fixed in 2.5.3 Advisory →
- Fix · GHSA-gjqc-q9g6-q2j3 tensorflow-gpu (PyPI) Fixed in 2.6.3 Advisory →
- Fix · GHSA-gjqc-q9g6-q2j3 tensorflow-gpu (PyPI) Fixed in 2.7.1 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2022-23583
- 2026-10-03 Alias added: GHSA-gjqc-q9g6-q2j3
References
Patch 2
More Google Tensorflow vulnerabilities
- TI-2022-20241 FractionalMaxPool and FractionalAVGPool heap out-of-bounds acess in Tensorflow CVSS 3.1CRITICAL 9.8
- TI-2022-07640 Integer overflow in Tensorflow CVSS 3.1CRITICAL 9.8
- TI-2022-07627 Out of bounds read and write in Tensorflow CVSS 3.1HIGH 8.8
- TI-2022-07619 Out of bounds write in Tensorflow CVSS 3.1HIGH 8.8
- TI-2022-07613 Read and Write outside of bounds in TFLite CVSS 3.1HIGH 8.8
- TI-2022-07612 Integer overflow in TFLite CVSS 3.1HIGH 8.8
Sources
- CVE-2022-23583 · CVE Program
- CVE-2022-23583 · NVD
- FIRST EPSS
- GHSA-gjqc-q9g6-q2j3 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences