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.
Configurations

Configuration 1 (hide)

cpe:2.3:a:google:tensorflow:*:*:*:*:-:*:*:*

History

18 Nov 2021, 17:22

Type Values Removed Values Added
CWE CWE-122

17 Aug 2021, 13:21

Type Values Removed Values Added
CPE cpe:2.3:a:tensorflow:tensorflow:*:*:*:*:-:*:*:* cpe:2.3:a:google:tensorflow:*:*:*:*:-:*:*:*

Information

Published : 2020-09-25 19:15

Updated : 2023-12-10 13:41


NVD link : CVE-2020-15198

Mitre link : CVE-2020-15198

CVE.ORG link : CVE-2020-15198


JSON object : View

Products Affected

google

  • tensorflow
CWE
CWE-119

Improper Restriction of Operations within the Bounds of a Memory Buffer

CWE-122

Heap-based Buffer Overflow