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-23576, CVE-2022-23576, PYSEC-2022-140, PYSEC-2022-85, PYSEC-2026-3254
Integer overflow in Tensorflow
Impact
The implementation of `OpLevelCostEstimator::CalculateOutputSize` is vulnerable to an integer overflow if an attacker can create an operation which would involve tensors with large enough number of elements:
for (const auto& dim : output_shape.dim()) {
output_size *= dim.size();
}
Here, we can have a large enough number of dimensions in output_shape.dim() or just a small number of dimensions being large enough to cause an overflow in the multiplication.
Patches
We have patched the issue in GitHub commit b9bd6cfd1c50e6807846af9a86f9b83cafc9c8ae.
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.
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