tensorflow
Affected
- introduced
0, fixed2.3.4(ecosystem)
Fixed versions
2.3.4
Fix
- Fixed version
2.3.4pip install --upgrade tensorflow==2.3.4
Advisory
Also known as: BIT-tensorflow-2021-37673, CVE-2021-37673, PYSEC-2021-295, PYSEC-2021-586, PYSEC-2021-784
CHECK-fail in MapStage
Impact
An attacker can trigger a denial of service via a CHECK-fail in tf.raw_ops.MapStage:
import tensorflow as tf
tf.raw_ops.MapStage(
key=tf.constant([], shape=[0, 0, 0, 0], dtype=tf.int64),
indices=tf.constant((0), dtype=tf.int32),
values=[tf.constant((0), dtype=tf.int32)],
dtypes=[tf.int32,
tf.int64],
capacity=0,
memory_limit=0,
container='',
shared_name='')
The implementation does not check that the key input is a valid non-empty tensor.
Patches
We have patched the issue in GitHub commit d7de67733925de196ec8863a33445b73f9562d1d.
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.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 Ying Wang and Yakun Zhang of Baidu X-Team.
Medium Basis: The source's own band: MODERATE
0, fixed 2.3.4 (ecosystem)2.3.4
2.3.4pip install --upgrade tensorflow==2.3.42.4.0, fixed 2.4.3 (ecosystem)2.4.3
2.4.3pip install --upgrade tensorflow==2.4.32.5.0, fixed 2.5.1 (ecosystem)2.5.1
2.5.1pip install --upgrade tensorflow==2.5.10, fixed 2.3.4 (ecosystem)2.3.4
2.3.4pip install --upgrade tensorflow-cpu==2.3.42.4.0, fixed 2.4.3 (ecosystem)2.4.3
2.4.3pip install --upgrade tensorflow-cpu==2.4.32.5.0, fixed 2.5.1 (ecosystem)2.5.1
2.5.1pip install --upgrade tensorflow-cpu==2.5.10, fixed 2.3.4 (ecosystem)2.3.4
2.3.4pip install --upgrade tensorflow-gpu==2.3.42.4.0, fixed 2.4.3 (ecosystem)2.4.3
2.4.3pip install --upgrade tensorflow-gpu==2.4.32.5.0, fixed 2.5.1 (ecosystem)2.5.1
2.5.1pip install --upgrade tensorflow-gpu==2.5.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