Buffer overflow in Google Tensorflow
CVE-2020-15198
In Tensorflow before version 2.3.1, 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. Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1.
Vulnerability class: Buffer Overflow
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.4 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N.
EPSS exploit prediction
EPSS 0.005, 46.1th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Google Tensorflow
- Tensorflow — versions >= 2.3.0, < 2.3.1
Weakness classification (CWE)
References
- github.com/tensorflow/tensorflow/releases/tag/v2.3.1 (Third Party Advisory)
- github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02 (Patch, Third Party Advisory)
- github.com/tensorflow/tensorflow/security/advisories/GHSA-jc87-6vpp-7ff3 (Exploit, Third Party Advisory)