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-41210, CVE-2021-41210, PYSEC-2021-402, PYSEC-2021-619, PYSEC-2021-817
Heap OOB read in tf.raw_ops.SparseCountSparseOutput
Impact
The shape inference functions for `SparseCountSparseOutput` can trigger a read outside of bounds of heap allocated array:
import tensorflow as tf
@tf.function
def func():
return tf.raw_ops.SparseCountSparseOutput(
indices=[1],
values=[[1]],
dense_shape=[10],
weights=[],
binary_output= True)
func()
The function fails to check that the first input (i.e., indices) has rank 2:
auto rank = c->Dim(c->input(0), 1);
Patches
We have patched the issue in GitHub commit 701cfaca222a82afbeeb17496bd718baa65a67d2.
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.
High Basis: The source's own band: HIGH
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