tensorflow
Affected
- introduced
0, fixed2.5.3(ecosystem)
Fixed versions
2.5.3
Fix
- Fixed version
2.5.3pip install --upgrade tensorflow==2.5.3
Advisory
Also known as: BIT-tensorflow-2022-21741, CVE-2022-21741, PYSEC-2022-120, PYSEC-2022-65, PYSEC-2026-3095
Division by zero in TFLite
Impact
An attacker can craft a TFLite model that would trigger a division by zero in the implementation of depthwise convolutions.
The parameters of the convolution can be user controlled and are also used within a division operation to determine the size of the padding that needs to be added before applying the convolution. There is no check before this division that the divisor is stricly positive.
Patches
We have patched the issue in GitHub commit e5b0eec199c2d03de54fd6a7fd9275692218e2bc.
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.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 Wang Xuan of Qihoo 360 AIVul Team.
High Basis: The source's own band: HIGH
0, fixed 2.5.3 (ecosystem)2.5.3
2.5.3pip install --upgrade tensorflow==2.5.32.6.0, fixed 2.6.3 (ecosystem)2.6.3
2.6.3pip install --upgrade tensorflow==2.6.32.7.0, fixed 2.7.1 (ecosystem)2.7.1
2.7.1pip install --upgrade tensorflow==2.7.10, fixed 2.5.3 (ecosystem)2.5.3
2.5.3pip install --upgrade tensorflow-cpu==2.5.32.6.0, fixed 2.6.3 (ecosystem)2.6.3
2.6.3pip install --upgrade tensorflow-cpu==2.6.32.7.0, fixed 2.7.1 (ecosystem)2.7.1
2.7.1pip install --upgrade tensorflow-cpu==2.7.10, fixed 2.5.3 (ecosystem)2.5.3
2.5.3pip install --upgrade tensorflow-gpu==2.5.32.6.0, fixed 2.6.3 (ecosystem)2.6.3
2.6.3pip install --upgrade tensorflow-gpu==2.6.32.7.0, fixed 2.7.1 (ecosystem)2.7.1
2.7.1pip install --upgrade tensorflow-gpu==2.7.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