tensorflow
Affected
- introduced
0, fixed2.8.4(ecosystem)
Fixed versions
2.8.4
Fix
- Fixed version
2.8.4pip install --upgrade tensorflow==2.8.4
Advisory
Also known as: BIT-tensorflow-2022-41893, CVE-2022-41893, PYSEC-2026-3118, PYSEC-2026-3284, PYSEC-2026-958
CHECK_EQ fail in tf.raw_ops.TensorListResize
Impact
If `tf.raw_ops.TensorListResize` is given a nonscalar value for input size, it results CHECK fail which can be used to trigger a denial of service attack.
import numpy as np
import tensorflow as tf
a = data_structures.tf_tensor_list_new(elements = tf.constant(value=[3, 4, 5]))
b = np.zeros([0, 2, 3, 3])
tf.raw_ops.TensorListResize(input_handle=a, size=b)
Patches
We have patched the issue in GitHub commit 888e34b49009a4e734c27ab0c43b0b5102682c56.
The fix will be included in TensorFlow 2.11. We will also cherrypick this commit on TensorFlow 2.10.1, 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 has been reported by Pattarakrit Rattankul
Medium Basis: The source's own band: MODERATE
0, fixed 2.8.4 (ecosystem)2.8.4
2.8.4pip install --upgrade tensorflow==2.8.42.9.0, fixed 2.9.3 (ecosystem)2.9.3
2.9.3pip install --upgrade tensorflow==2.9.32.10.0, fixed 2.10.1 (ecosystem)2.10.1
2.10.1pip install --upgrade tensorflow==2.10.10, fixed 2.8.4 (ecosystem)2.8.4
2.8.4pip install --upgrade tensorflow-cpu==2.8.40, fixed 2.8.4 (ecosystem)2.8.4
2.8.4pip install --upgrade tensorflow-gpu==2.8.42.9.0, fixed 2.9.3 (ecosystem)2.9.3
2.9.3pip install --upgrade tensorflow-cpu==2.9.32.9.0, fixed 2.9.3 (ecosystem)2.9.3
2.9.3pip install --upgrade tensorflow-gpu==2.9.32.10.0, fixed 2.10.1 (ecosystem)2.10.1
2.10.1pip install --upgrade tensorflow-cpu==2.10.12.10.0, fixed 2.10.1 (ecosystem)2.10.1
2.10.1pip install --upgrade tensorflow-gpu==2.10.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0