INCIDENT MAP

Browse / AI Framework and Platform Flaws / CVE-2020-15199

Denial of Service in Tensorflow

CVE-2020-15199 ยท 2020-09-25 high

Class
AI Framework and Platform Flaws (filed by a model that read the advisory)
Technique
Denial of service
Affected
tensorflow-cpu, tensorflow (PyPI)
CVSS
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.8% chance of exploitation in 30 days

How it works, in short

Passing an empty or single-element splits tensor to a ragged count op reaches an unchecked null path that aborts the process. (Our summary, written by a model. The source text is below.)

Details

Impact

The RaggedCountSparseOutput does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the splits tensor has the minimum required number of elements. Code uses this quantity to initialize a different data structure: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L241-L244

Since BatchedMap is equivalent to a vector, it needs to have at least one element to not be nullptr. If user passes a splits tensor that is empty or has exactly one element, we get a SIGABRT signal raised by the operating system.

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

References

Source: GitHub Advisory Database, used under CC BY 4.0.