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.
Does this matter?
Lower severity and a low EPSS score (0.54%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 5.4 MEDIUMCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
- EPSS
- 0.54% probability · 44th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-119, CWE-122
- Affected
- google/tensorflow
- Source
- security-advisories@github.com
References
- https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02Patch, Third Party Advisory
- https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1Third Party Advisory
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-jc87-6vpp-7ff3Exploit, Third Party Advisory
- https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02Patch, Third Party Advisory
- https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1Third Party Advisory
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-jc87-6vpp-7ff3Exploit, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.