Heap buffer overflow in Tensorflow

### 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.

CVSS 3.1

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Severity from

GitHub (reviewed advisory)

Weakness

CWE-122, CWE-20, CWE-787

Also known as

BIT-tensorflow-2020-15201, CVE-2020-15201, PYSEC-2020-124, PYSEC-2020-281, PYSEC-2020-316

• github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4
• nvd.nist.gov/vuln/detail/CVE-2020-15201
• github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02
• github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-281.yaml
• github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-316.yaml
• github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-124.yaml
• github.com/tensorflow/tensorflow
• github.com/tensorflow/tensorflow/releases/tag/v2.3.1