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 (43.3th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 43rd percentile — 43.3% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2020-15198: held from 0.005 to 0.005.

EPSS over last 30 days · oldest: 0.005 · newest: 0.005 · change: 0.000

Affected products

Weakness classification (CWE)

References

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.