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
EPSS: 0.005 (42.3th percentile) — read the EPSS interpretation.
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.
Affected products
- Google Tensorflow
- Tensorflow — versions >= 2.3.0, < 2.3.1
Weakness classification (CWE)
References
- security-advisories@github.com (Third Party Advisory, x_refsource_MISC)
- security-advisories@github.com (Patch, Third Party Advisory, x_refsource_MISC)
- security-advisories@github.com (x_refsource_CONFIRM, Exploit, Third Party Advisory)
Frequently asked questions
- What is CVE-2020-15198?
- CVE-2020-15198 is a medium-severity vulnerability in Google Tensorflow, classified under Improper Restriction of Operations within the Bounds of a Memory Buffer. CVSS score: 5.4/10. Published 2020-09-25.
- How severe is CVE-2020-15198?
- Medium severity. CVSS v3 base score is 5.4 out of 10.