Invalid char to bool conversion when printing a tensor

CAO 7.5CVE-2022-41911 · BIT-tensorflow-2022-41911 · GHSA-pf36-r9c6-h97j · Công bố 18/11/2022 · cập nhật 17/06/2026

Tóm tắt nhanh

CVE-2022-41911 là lỗ hổng mức CAO (CVSS 7.5) ảnh hưởng tensorflow, tensorflow-cpu, tensorflow-gpu.
Xác suất bị khai thác trong 30 ngày tới (EPSS): 0.44%, cao hơn 38.8% các lỗ hổng khác.
Cách xử lý: cập nhật lên 2.10.1, 2.9.3, 2.8.4 hoặc mới hơn.

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
tensorflow PyPI	`≥ 2.10.0, < 2.10.1≥ 2.9.0, < 2.9.3< 2.8.4`	`2.10.12.9.32.8.4`
tensorflow-cpu PyPI	`≥ 2.10.0, < 2.10.1≥ 2.9.0, < 2.9.3< 2.8.4`	`2.10.12.9.32.8.4`
tensorflow-gpu PyPI	`≥ 2.10.0, < 2.10.1≥ 2.9.0, < 2.9.3< 2.8.4`	`2.10.12.9.32.8.4`
tensorflow google	`= 2.10.0≥ 2.9.0, < 2.9.3< 2.8.4`	`2.9.32.8.4`

Mô tả

Impact

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.

Patches

We have patched the issue in GitHub commit 1be743703279782a357adbf9b77dcb994fe8b508.

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.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability was discovered via internal fuzzing.

Mô tả của NVD

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.