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-35941, CVE-2022-35941, PYSEC-2026-1019, PYSEC-2026-3215, PYSEC-2026-3351
TensorFlow vulnerable to CHECK failure in AvgPoolOp
Impact
The `AvgPoolOp` function takes an argument ksize that must be positive but is not checked. A negative ksize can trigger a CHECK failure and crash the program.
import tensorflow as tf
import numpy as np
value = np.ones([1, 1, 1, 1])
ksize = [1, 1e20, 1, 1]
strides = [1, 1, 1, 1]
padding = 'SAME'
data_format = 'NHWC'
tf.raw_ops.AvgPool(value=value, ksize=ksize, strides=strides, padding=padding, data_format=data_format)
Patches
We have patched the issue in GitHub commit 3a6ac52664c6c095aa2b114e742b0aa17fdce78f.
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 Jingyi Shi.
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.2 (ecosystem)2.9.2
2.9.2pip install --upgrade tensorflow==2.9.20, 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.2 (ecosystem)2.9.2
2.9.2pip install --upgrade tensorflow-cpu==2.9.20, 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.2 (ecosystem)2.9.2
2.9.2pip install --upgrade tensorflow-gpu==2.9.2Fix 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