Invalid char to bool conversion when printing a tensor in Tensorflow
Key facts
- Attack vector
- Network
- Privileges required
- None
- 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 · NVD. Fix status from CNA and GitHub. Impact type from CWE-704 and the CVSS impact.
Summary
TensorFlow is an open source platform for machine learning. When printing a tensor, we get it's data as a `const char*` array (since that's the underlying storage) and then we typecast it to the element type. However, conversions from `char` to `bool` are undefined if the `char` is not `0` or `1`, so sanitizers/fuzzers will crash. The issue has been patched in GitHub commit `1be74370327`. The fix will be included in TensorFlow 2.11.0. We will also cherrypick this commit on TensorFlow 2.10.1, TensorFlow 2.9.3, and TensorFlow 2.8.4, as these are also affected and still in supported range.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- 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.10.0 to before 2.10.1; 2.9.0 to before 2.9.3; before 2.8.4 | 2.10.1, 2.9.3, 2.8.4 | Patch available | CNA | |
| — | tensorflow (PyPI) | before 2.8.4 | 2.8.4 | Patch available | GHSA-pf36-r9c6-h97j |
| — | tensorflow-cpu (PyPI) | 2.9.0 to before 2.9.3 | 2.9.3 | Patch available | GHSA-pf36-r9c6-h97j |
| — | tensorflow-gpu (PyPI) | 2.10.0 to before 2.10.1 | 2.10.1 | Patch available | GHSA-pf36-r9c6-h97j |
| — | tensorflow (PyPI) | 2.9.0 to before 2.9.3 | 2.9.3 | Patch available | GHSA-pf36-r9c6-h97j |
| — | tensorflow (PyPI) | 2.10.0 to before 2.10.1 | 2.10.1 | Patch available | GHSA-pf36-r9c6-h97j |
| — | tensorflow-cpu (PyPI) | before 2.8.4 | 2.8.4 | Patch available | GHSA-pf36-r9c6-h97j |
| — | tensorflow-gpu (PyPI) | before 2.8.4 | 2.8.4 | Patch available | GHSA-pf36-r9c6-h97j |
| — | tensorflow-gpu (PyPI) | 2.9.0 to before 2.9.3 | 2.9.3 | Patch available | GHSA-pf36-r9c6-h97j |
| — | tensorflow-cpu (PyPI) | 2.10.0 to before 2.10.1 | 2.10.1 | Patch available | GHSA-pf36-r9c6-h97j |
- tensorflow VendorGoogle Affected 2.10.0 to before 2.10.1; 2.9.0 to before 2.9.3; before 2.8.4 Fixed in 2.10.1, 2.9.3, 2.8.4 Patch available CNA
- tensorflow (PyPI) Vendor— Affected before 2.8.4 Fixed in 2.8.4 Patch available GHSA-pf36-r9c6-h97j
- tensorflow-cpu (PyPI) Vendor— Affected 2.9.0 to before 2.9.3 Fixed in 2.9.3 Patch available GHSA-pf36-r9c6-h97j
- tensorflow-gpu (PyPI) Vendor— Affected 2.10.0 to before 2.10.1 Fixed in 2.10.1 Patch available GHSA-pf36-r9c6-h97j
- tensorflow (PyPI) Vendor— Affected 2.9.0 to before 2.9.3 Fixed in 2.9.3 Patch available GHSA-pf36-r9c6-h97j
- tensorflow (PyPI) Vendor— Affected 2.10.0 to before 2.10.1 Fixed in 2.10.1 Patch available GHSA-pf36-r9c6-h97j
- tensorflow-cpu (PyPI) Vendor— Affected before 2.8.4 Fixed in 2.8.4 Patch available GHSA-pf36-r9c6-h97j
- tensorflow-gpu (PyPI) Vendor— Affected before 2.8.4 Fixed in 2.8.4 Patch available GHSA-pf36-r9c6-h97j
- tensorflow-gpu (PyPI) Vendor— Affected 2.9.0 to before 2.9.3 Fixed in 2.9.3 Patch available GHSA-pf36-r9c6-h97j
- tensorflow-cpu (PyPI) Vendor— Affected 2.10.0 to before 2.10.1 Fixed in 2.10.1 Patch available GHSA-pf36-r9c6-h97j
Remediation
- Fix · CNA tensorflow (tensorflow) Fixed in 2.10.1, 2.9.3, 2.8.4
- Fix · GHSA-pf36-r9c6-h97j tensorflow (PyPI) Fixed in 2.8.4 Advisory →
- Fix · GHSA-pf36-r9c6-h97j tensorflow-cpu (PyPI) Fixed in 2.9.3 Advisory →
- Fix · GHSA-pf36-r9c6-h97j tensorflow-gpu (PyPI) Fixed in 2.10.1 Advisory →
- Fix · GHSA-pf36-r9c6-h97j tensorflow (PyPI) Fixed in 2.9.3 Advisory →
- Fix · GHSA-pf36-r9c6-h97j tensorflow (PyPI) Fixed in 2.10.1 Advisory →
- Fix · GHSA-pf36-r9c6-h97j tensorflow-cpu (PyPI) Fixed in 2.8.4 Advisory →
- Fix · GHSA-pf36-r9c6-h97j tensorflow-gpu (PyPI) Fixed in 2.8.4 Advisory →
- Fix · GHSA-pf36-r9c6-h97j tensorflow-gpu (PyPI) Fixed in 2.9.3 Advisory →
- Fix · GHSA-pf36-r9c6-h97j tensorflow-cpu (PyPI) Fixed in 2.10.1 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2022-41911
- 2026-10-03 Alias added: GHSA-pf36-r9c6-h97j
References
Patch 3
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pf36-r9c6-h97j
- https://github.com/tensorflow/tensorflow/commit/1be743703279782a357adbf9b77dcb994fe8b508
- https://github.com/tensorflow/tensorflow/blob/807cae8a807960fd7ac2313cde73a11fc15e7942/tensorflow/core/framework/tensor.cc#L1200-L1227
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-41911 · CVE Program
- CVE-2022-41911 · NVD
- FIRST EPSS
- GHSA-pf36-r9c6-h97j · 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