tensorflow
Affected
- introduced
2.6.0, fixed2.6.1(ecosystem)
Fixed versions
2.6.1
Fix
- Fixed version
2.6.1pip install --upgrade tensorflow==2.6.1
Advisory
Also known as: BIT-tensorflow-2021-41224, CVE-2021-41224, PYSEC-2021-416, PYSEC-2021-633, PYSEC-2021-831
SparseFillEmptyRows heap OOB
Impact
The implementation of SparseFillEmptyRows can be made to trigger a heap OOB access:
import tensorflow as tf
data=tf.raw_ops.SparseFillEmptyRows(
indices=[[0,0],[0,0],[0,0]],
values=['sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss'],
dense_shape=[5,3],
default_value='o')
This occurs whenever the size of indices does not match the size of values.
Patches
We have patched the issue in GitHub commit 67bfd9feeecfb3c61d80f0e46d89c170fbee682b.
The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.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
2.6.0, fixed 2.6.1 (ecosystem)2.6.1
2.6.1pip install --upgrade tensorflow==2.6.12.5.0, fixed 2.5.2 (ecosystem)2.5.2
2.5.2pip install --upgrade tensorflow==2.5.20, fixed 2.4.4 (ecosystem)2.4.4
2.4.4pip install --upgrade tensorflow==2.4.42.6.0, fixed 2.6.1 (ecosystem)2.6.1
2.6.1pip install --upgrade tensorflow-cpu==2.6.12.5.0, fixed 2.5.2 (ecosystem)2.5.2
2.5.2pip install --upgrade tensorflow-cpu==2.5.20, fixed 2.4.4 (ecosystem)2.4.4
2.4.4pip install --upgrade tensorflow-cpu==2.4.42.6.0, fixed 2.6.1 (ecosystem)2.6.1
2.6.1pip install --upgrade tensorflow-gpu==2.6.12.5.0, fixed 2.5.2 (ecosystem)2.5.2
2.5.2pip install --upgrade tensorflow-gpu==2.5.20, fixed 2.4.4 (ecosystem)2.4.4
2.4.4pip install --upgrade tensorflow-gpu==2.4.4Fix 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