First published: Fri Sep 25 2020(Updated: )
### Impact The `RaggedCountSparseOutput` implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the `splits` tensor generate a valid partitioning of the `values` tensor. Hence, this code is prone to heap buffer overflow: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L248-L251 If `split_values` does not end with a value at least `num_values` then the `while` loop condition will trigger a read outside of the bounds of `split_values` once `batch_idx` grows too large. ### 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](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Google TensorFlow | =2.3.0 | |
pip/tensorflow-gpu | =2.3.0 | 2.3.1 |
pip/tensorflow-cpu | =2.3.0 | 2.3.1 |
pip/tensorflow | =2.3.0 | 2.3.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-15201 has a medium severity level due to potential vulnerabilities in tensor validation during operations.
To fix CVE-2020-15201, upgrade TensorFlow to version 2.3.1 or later.
CVE-2020-15201 affects TensorFlow version 2.3.0.
CVE-2020-15201 could lead to invalid tensor operations, potentially causing application crashes or unexpected behavior.
Yes, CVE-2020-15201 specifically affects tensorflow-gpu, tensorflow-cpu, and the main tensorflow package all at version 2.3.0.