CVE-2020-15198
low-risk
Published 2020-09-25
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.
Do I need to act?
-
0.17% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
5
CVSS 5.4/10
Medium
NETWORK
/ HIGH complexity
Affected Products (1)
Affected Vendors
References (6)
Third Party Advisory
https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1
Third Party Advisory
https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1
23
/ 100
low-risk
Severity
17/34 · Moderate
Exploitability
1/34 · Minimal
Exposure
5/34 · Minimal