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-15197, CVE-2020-15197, PYSEC-2020-120, PYSEC-2020-277, PYSEC-2020-312
Denial of Service 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 rank 2. This tensor must be a matrix because code assumes its elements are accessed as elements of a matrix:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L185
However, malicious users can pass in tensors of different rank, resulting in a CHECK assertion failure and a crash. This can be used to cause denial of service in serving installations, if users are allowed to control the components of the input sparse tensor.
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