tensorflow
Affected
- introduced
2.3.0, fixed2.3.1(ecosystem)
Fixed versions
2.3.1
Fix
- Fixed version
2.3.1pip install --upgrade tensorflow==2.3.1
Advisory
Also known as: BIT-tensorflow-2020-15198, CVE-2020-15198, PYSEC-2020-121, PYSEC-2020-278, PYSEC-2020-313
Heap buffer overflow in Tensorflow
Impact
The SparseCountSparseOutput implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the indices tensor has the same shape as the values one. The values in these tensors are always accessed in parallel:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L193-L195
Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers.
Patches
We have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release.
We recommend users to upgrade to TensorFlow 2.3.1.
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 is a variant of GHSA-p5f8-gfw5-33w4
Medium Basis: The source's own band: MODERATE
2.3.0, fixed 2.3.1 (ecosystem)2.3.1
2.3.1pip install --upgrade tensorflow==2.3.12.3.0, fixed 2.3.1 (ecosystem)2.3.1
2.3.1pip install --upgrade tensorflow-cpu==2.3.12.3.0, fixed 2.3.1 (ecosystem)2.3.1
2.3.1pip install --upgrade tensorflow-gpu==2.3.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