CVE-2020-15201
Published:September 25, 2020
Updated:May 17, 2026
In Tensorflow before version 2.3.1, the "RaggedCountSparseOutput" implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the "splits" tensor generate a valid partitioning of the "values" tensor. Hence, the code is prone to heap buffer overflow. If "split_values" does not end with a value at least "num_values" then the "while" loop condition will trigger a read outside of the bounds of "split_values" once "batch_idx" grows too large. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1.
Affected Packages
tensorflow-gpu (PYTHON):
Affected version(s) =2.3.0 <2.3.1Fix Suggestion:
Update to version 2.3.1tensorflow-cpu (PYTHON):
Affected version(s) =2.3.0 <2.3.1Fix Suggestion:
Update to version 2.3.1tensorflow (PYTHON):
Affected version(s) =2.3.0 <2.3.1Fix Suggestion:
Update to version 2.3.1Additional Notes
The description of this vulnerability differs from MITRE.
Related Resources (8)
Do you need more information?
Contact UsCVSS v4
Base Score:
6.3
Attack Vector
NETWORK
Attack Complexity
HIGH
Attack Requirements
NONE
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
LOW
Vulnerable System Integrity
LOW
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
4.8
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
LOW
Availability
NONE
Weakness Type (CWE)
EPSS
Base Score:
0.19