CVE-2020-15196
Heap buffer overflow in Tensorflow
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 CVE-2020-15196
To remediate CVE-2020-15196, upgrade the affected package to a fixed version below.
- —upgrade to 2.3.1 or later
- —upgrade to 2.3.1 or later
- —upgrade to 3cbb917b4714766030b28eba9fb41bb97ce9ee02 or later
- —upgrade to 3cbb917b4714766030b28eba9fb41bb97ce9ee02 or later
- —upgrade to 2.3.1 or later
- —upgrade to 3cbb917b4714766030b28eba9fb41bb97ce9ee02 or later
- —upgrade to 2.3.1 or later
Is CVE-2020-15196 being exploited?
Low — EPSS is 0.3%, meaning exploitation activity has not been observed at scale.
Affected packages (7)
- >= 2.3.0, < 2.3.1
- >= 2.3.0, < 2.3.1
- from 0, < 3cbb917b4714766030b28eba9fb41bb97ce9ee02 | from 0, < 2.3.1
- from 0, < 3cbb917b4714766030b28eba9fb41bb97ce9ee02 | from 0, < 2.3.1
- >= 2.3.0, < 2.3.1
- from 0, < 3cbb917b4714766030b28eba9fb41bb97ce9ee02 | from 0, < 2.3.1
- >= 2.3.0, < 2.3.1
CVSS scores
| Source | Version | Severity | Vector |
|---|---|---|---|
| osv | CVSS 4.0 | — | CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:H |
| osv | CVSS 3.1 | HIGH8.5 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H |