CVE-2020-15196Improper Restriction of Operations within the Bounds of a Memory Buffer in Intel Optimization FOR Tensorflow

Severity
9.9CRITICALNVD
CNA8.5
EPSS
0.3%
top 46.45%
CISA KEV
Not in KEV
Exploit
No known exploits
Timeline
PublishedSep 25

Description

In Tensorflow version 2.3.0, the `SparseCountSparseOutput` and `RaggedCountSparseOutput` implementations don't validate that the `weights` tensor has the same shape as the data. The check exists for `DenseCountSparseOutput`, where both tensors are fully specified. In the sparse and ragged count weights are still accessed in parallel with the data. But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the hea

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HExploitability: 3.1 | Impact: 6.0

Affected Packages3 packages

PyPIintel/optimization_for_tensorflow2.3.02.3.1+2
CVEListV5tensorflow/tensorflow= 2.3.0

Patches

🔴Vulnerability Details

4
CVEList
Heap buffer overflow in Tensorflow2020-09-25
GHSA
Heap buffer overflow in Tensorflow2020-09-25
OSV
CVE-2020-15196: In Tensorflow version 22020-09-25
OSV
Heap buffer overflow in Tensorflow2020-09-25

📋Vendor Advisories

1
Debian
CVE-2020-15196: tensorflow - In Tensorflow version 2.3.0, the `SparseCountSparseOutput` and `RaggedCountSpars...2020
CVE-2020-15196 — Intel vulnerability | cvebase