cve.bz

CVE-2020-15200

5.9 mediumEPSS 0.9%

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

In Tensorflow before version 2.3.1, the `RaggedCountSparseOutput` implementation does not validate that the input arguments form a valid ragged tensor. In particular, there is no validation that the values in the `splits` tensor generate a valid partitioning of the `values` tensor. Thus, the code sets up conditions to cause a heap buffer overflow. A `BatchedMap` is equivalent to a vector where each element is a hashmap. However, if the first element of `splits_values` is not 0, `batch_idx` will never be 1, hence there will be no hashmap at index 0 in `per_batch_counts`. Trying to access that in the user code results in a segmentation fault. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.9% chance of exploitation in the next 30 days; higher than 58% of CVEs (scores of 2026-10-31)
CWEs
CWE-787, CWE-20, CWE-122
Published
Modified
Record from
the NVD, synced

Affected

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-x7rp-74x2-mjf3PyPItensorflow>=2.3.0 <2.3.12.3.1
GHSA-x7rp-74x2-mjf3PyPItensorflow-cpu>=2.3.0 <2.3.12.3.1
GHSA-x7rp-74x2-mjf3PyPItensorflow-gpu>=2.3.0 <2.3.12.3.1
PYSEC-2020-123PyPItensorflow<2.3.12.3.1
PYSEC-2020-280PyPItensorflow-cpu<2.3.12.3.1
PYSEC-2020-315PyPItensorflow-gpu<2.3.12.3.1

References

Check your stackJSON