CVE-2020-15198
Medium
Description
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.
SeverityMedium
CVSS5.4
Exploit probability—
Product
Google Tensorflow
PublishedSep 25, 2020
First seenSep 25, 2020
Weakness typeCWE-122CWE-122CWE-119Memory buffer bounds error
How to fix
Update
- google tensorflow2.3.1 or later
- tensorflow2.3.1 or later
- tensorflow-cpu2.3.1 or later
- tensorflow-gpu2.3.1 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| google tensorflow | 2.3.0 ≤ v < 2.3.1 | 2.3.1 |
| tensorflowPyPI | 2.3.0 ≤ v < 2.3.1, v < 2.3.1 | 2.3.1 |
| tensorflow-cpuPyPI | 2.3.0 ≤ v < 2.3.1, v < 2.3.1 | 2.3.1 |
| tensorflow-gpuPyPI | 2.3.0 ≤ v < 2.3.1, v < 2.3.1 | 2.3.1 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
In the Intelligence 360 plan
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.