tensorflow
Affected
- introduced
0, fixed2.7.2(ecosystem)
Fixed versions
2.7.2
Fix
- Fixed version
2.7.2pip install --upgrade tensorflow==2.7.2
Advisory
Also known as: BIT-tensorflow-2022-35993, CVE-2022-35993, PYSEC-2026-1044, PYSEC-2026-3255, PYSEC-2026-3378
TensorFlow vulnerable to CHECK fail in SetSize
Impact
When SetSize receives an input set_shape that is not a 1D tensor, it gives a CHECK fails that can be used to trigger a denial of service attack.
import tensorflow as tf
arg_0=1
arg_1=[1,1]
arg_2=1
arg_3=True
arg_4=''
tf.raw_ops.SetSize(set_indices=arg_0, set_values=arg_1, set_shape=arg_2,
validate_indices=arg_3, name=arg_4)
Patches
We have patched the issue in GitHub commit cf70b79d2662c0d3c6af74583641e345fc939467.
The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, 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 刘力源, Information System & Security and Countermeasures Experiments Center, Beijing Institute of Technology.
Medium Basis: The source's own band: MODERATE
0, fixed 2.7.2 (ecosystem)2.7.2
2.7.2pip install --upgrade tensorflow==2.7.22.8.0, fixed 2.8.1 (ecosystem)2.8.1
2.8.1pip install --upgrade tensorflow==2.8.12.9.0, fixed 2.9.1 (ecosystem)2.9.1
2.9.1pip install --upgrade tensorflow==2.9.10, fixed 2.7.2 (ecosystem)2.7.2
2.7.2pip install --upgrade tensorflow-cpu==2.7.22.8.0, fixed 2.8.1 (ecosystem)2.8.1
2.8.1pip install --upgrade tensorflow-cpu==2.8.12.9.0, fixed 2.9.1 (ecosystem)2.9.1
2.9.1pip install --upgrade tensorflow-cpu==2.9.10, fixed 2.7.2 (ecosystem)2.7.2
2.7.2pip install --upgrade tensorflow-gpu==2.7.22.8.0, fixed 2.8.1 (ecosystem)2.8.1
2.8.1pip install --upgrade tensorflow-gpu==2.8.12.9.0, fixed 2.9.1 (ecosystem)2.9.1
2.9.1pip install --upgrade tensorflow-gpu==2.9.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