CVE-2020-15198
September 25, 2020
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.
Affected Packages
tensorflow (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-gpu (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
LOW
Subsequent System Integrity
LOW
Subsequent System Availability
NONE
CVSS v3
Base Score:
5.4
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
CHANGED
Confidentiality
LOW
Integrity
LOW
Availability
NONE
CVSS v2
Base Score:
5.8
Access Vector
NETWORK
Access Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
NONE
Weakness Type (CWE)
EPSS
Base Score:
0.17
