| CVE-2020-15196 | Date: (C)2020-09-28 (M)2023-12-22 |
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.
CVSS Score and Metrics +CVSS Score and Metrics -| CVSS V3 Severity: | CVSS V2 Severity: |
| CVSS Score : 9.9 | CVSS Score : 6.5 |
| Exploit Score: 3.1 | Exploit Score: 8.0 |
| Impact Score: 6.0 | Impact Score: 6.4 |
| |
| CVSS V3 Metrics: | CVSS V2 Metrics: |
| Attack Vector: NETWORK | Access Vector: NETWORK |
| Attack Complexity: LOW | Access Complexity: LOW |
| Privileges Required: LOW | Authentication: SINGLE |
| User Interaction: NONE | Confidentiality: PARTIAL |
| Scope: CHANGED | Integrity: PARTIAL |
| Confidentiality: HIGH | Availability: PARTIAL |
| Integrity: HIGH | |
| Availability: HIGH | |
| | |
