CVE-2020-15196

Heap buffer overflow in Tensorflow

State: Published
Severity: 8.5 High
Published: Sep 25, 2020
Updated: Aug 4, 2024
Reserved: Jun 25, 2020

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 heap buffer allocated for the weights. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1.

Scores

CVSS	Score	Vector	Source
3.1	8.5 High	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H	GitHub_M

Weaknesses

CWE-119 {"CWE-119":"Improper Restriction of Operations within the Bounds of a Memory Buffer"}
CWE-122 {"CWE-122":"Heap-based Buffer Overflow"}

Affected Products

Product	Versions
tensorflowtensorflow	= 2.3.0Affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.