cve.bz

CVE-2020-15196

9.9 criticalEPSS 0.9%

Critical (9.9) in google tensorflow. EPSS 0.9% chance of exploitation in the next 30 days. Fixed in tensorflow 2.3.1.

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.

Severity

CVSS 3.1

9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
0.9% chance of exploitation in the next 30 days; higher than 60% of CVEs (scores of 2026-10-31)
CWEs
CWE-125, CWE-119, CWE-122
Published
Modified
Record from
the NVD, synced

Affected

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-pg59-2f92-5cphPyPItensorflow>=2.3.0 <2.3.12.3.1
GHSA-pg59-2f92-5cphPyPItensorflow-cpu>=2.3.0 <2.3.12.3.1
GHSA-pg59-2f92-5cphPyPItensorflow-gpu>=2.3.0 <2.3.12.3.1
PYSEC-2020-119PyPItensorflow<2.3.12.3.1
PYSEC-2020-276PyPItensorflow-cpu<2.3.12.3.1
PYSEC-2020-311PyPItensorflow-gpu<2.3.12.3.1

References

Check your stackJSON