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-23585, CVE-2022-23585, PYSEC-2022-149, PYSEC-2022-94, PYSEC-2026-3174
Memory leak in decoding PNG images
Impact
When decoding PNG images TensorFlow can produce a memory leak if the image is invalid.
After calling png::CommonInitDecode(..., &decode), the decode value contains allocated buffers which can only be freed by calling png::CommonFreeDecode(&decode). However, several error case in the function implementation invoke the OP_REQUIRES macro which immediately terminates the execution of the function, without allowing for the memory free to occur.
Patches
We have patched the issue in GitHub commit ab51e5b813573dc9f51efa335aebcf2994125ee9.
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.
Medium Basis: The source's own band: MODERATE
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