CVE-2020-15196
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.
How to fix
- tensorflow2.3.1 or later
- tensorflow-cpu2.3.1 or later
- tensorflow-gpu2.3.1 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| google tensorflow | 2.3.0 | — |
| tensorflowPyPI | 2.3.0 ≤ v < 2.3.1, v < 2.3.1 | 2.3.1 |
| tensorflow-cpuPyPI | 2.3.0 ≤ v < 2.3.1, v < 2.3.1 | 2.3.1 |
| tensorflow-gpuPyPI | 2.3.0 ≤ v < 2.3.1, v < 2.3.1 | 2.3.1 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.