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-37656, CVE-2021-37656, PYSEC-2021-278, PYSEC-2021-569, PYSEC-2021-767
Reference binding to nullptr in RaggedTensorToSparse
Impact
An attacker can cause undefined behavior via binding a reference to null pointer in tf.raw_ops.RaggedTensorToSparse:
import tensorflow as tf
tf.raw_ops.RaggedTensorToSparse(
rt_nested_splits=[[0, 38, 0]],
rt_dense_values=[])
The implementation has an incomplete validation of the splits values: it does not check that they are in increasing order.
Patches
We have patched the issue in GitHub commit 1071f554dbd09f7e101324d366eec5f4fe5a3ece.
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 members of the Aivul Team from Qihoo 360.
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