tensorflow
Affected
- introduced
0, fixed2.5.3(ecosystem)
Fixed versions
2.5.3
Fix
- Fixed version
2.5.3pip install --upgrade tensorflow==2.5.3
Advisory
Also known as: BIT-tensorflow-2022-21734, CVE-2022-21734, PYSEC-2022-113, PYSEC-2022-58, PYSEC-2026-3187
CHECK-failures in Tensorflow
Impact
The implementation of `MapStage` is vulnerable a CHECK-fail if the key tensor is not a scalar:
import tensorflow as tf
import numpy as np
tf.raw_ops.MapStage(
key = tf.constant(value=[4], shape= (1,2), dtype=tf.int64),
indices = np.array([[6]]),
values = np.array([-60]),
dtypes = [tf.int64], capacity=0, memory_limit=0,
container='', shared_name='', name=None
)
Patches
We have patched the issue in GitHub commit f57315566d7094f322b784947093406c2aea0d7d.
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, 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 Faysal Hossain Shezan from University of Virginia.
~
High Basis: The source's own band: HIGH
0, fixed 2.5.3 (ecosystem)2.5.3
2.5.3pip install --upgrade tensorflow==2.5.32.6.0, fixed 2.6.3 (ecosystem)2.6.3
2.6.3pip install --upgrade tensorflow==2.6.32.7.0, fixed 2.7.1 (ecosystem)2.7.1
2.7.1pip install --upgrade tensorflow==2.7.10, fixed 2.5.3 (ecosystem)2.5.3
2.5.3pip install --upgrade tensorflow-cpu==2.5.32.6.0, fixed 2.6.3 (ecosystem)2.6.3
2.6.3pip install --upgrade tensorflow-cpu==2.6.32.7.0, fixed 2.7.1 (ecosystem)2.7.1
2.7.1pip install --upgrade tensorflow-cpu==2.7.10, fixed 2.5.3 (ecosystem)2.5.3
2.5.3pip install --upgrade tensorflow-gpu==2.5.32.6.0, fixed 2.6.3 (ecosystem)2.6.3
2.6.3pip install --upgrade tensorflow-gpu==2.6.32.7.0, fixed 2.7.1 (ecosystem)2.7.1
2.7.1pip install --upgrade tensorflow-gpu==2.7.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