🛡️ CVE-2020-15196 — tensorflow

🔴 CVSS 9.5 — Critical ✅ No Known Exploit OSV
9.5
CVSS Score
0 Low4 Medium7 High9 Critical10

Description

Heap buffer overflow in Tensorflow

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.

Affected software

CVE-2020-15196 is recorded against 1 package.

  • tensorflow

Timeline and source

Published on 6 March 2024 and last revised on 20 May 2025. No public exploit is currently recorded for this entry. Record sourced from OSV.

References

github.com (Web)
github.com (Web)
github.com (Web)
nvd.nist.gov (Web)

Details

Severity CRITICAL
CVSS Score 9.5
CVSS Vector N/A
CWE N/A
Public Exploit ✅ No
Source OSV
Published 2024-03-06
Updated 2026-08-12
Modified 2025-05-20
Fix URL N/A

Affected Packages

Software From version Fixed in
tensorflow — —

Similar Threats

Exploit Protection

Are you running tensorflow?

CVE-2020-15196 carries CVSS 9.5 Critical rating. BotEraser checks your installation against this and other known CVE records, and blocks IPs associated with exploit activity.

Check My Site For CVE-2020-15196 →

No credit card required  ·  Results in minutes

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the vulnerabilities listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.