tensorflow
Affected
- introduced
0, fixed2.4.3(ecosystem)
Fixed versions
2.4.3
Fix
- Fixed version
2.4.3pip install --upgrade tensorflow==2.4.3
Advisory
Also known as: BIT-tensorflow-2021-37645, CVE-2021-37645, PYSEC-2021-267, PYSEC-2021-558, PYSEC-2021-756
Integer overflow due to conversion to unsigned
Impact
The implementation of tf.raw_ops.QuantizeAndDequantizeV4Grad is vulnerable to an integer overflow issue caused by converting a signed integer value to an unsigned one and then allocating memory based on this value.
import tensorflow as tf
tf.raw_ops.QuantizeAndDequantizeV4Grad(
gradients=[1.0,2.0],
input=[1.0,1.0],
input_min=[0.0],
input_max=[10.0],
axis=-100)
The implementation uses the axis value as the size argument to absl::InlinedVector constructor. But, the constructor uses an unsigned type for the argument, so the implicit conversion transforms the negative value to a large integer.
Patches
We have patched the issue in GitHub commit 96f364a1ca3009f98980021c4b32be5fdcca33a1.
The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, and TensorFlow 2.4.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 members of the Aivul Team from Qihoo 360.
Medium Basis: The source's own band: MODERATE
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.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.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