Heap buffer overflow in Tensorflow
Description
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. Hence, the code is prone to heap buffer overflow. If split_values does not end with a value at least num_values then the while loop condition will trigger a read outside of the bounds of split_values once batch_idx grows too large. The issue is patched in commit 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and is released in TensorFlow version 2.3.1.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
tensorflowPyPI | >= 2.3.0, < 2.3.1 | 2.3.1 |
tensorflow-cpuPyPI | >= 2.3.0, < 2.3.1 | 2.3.1 |
tensorflow-gpuPyPI | >= 2.3.0, < 2.3.1 | 2.3.1 |
Affected products
5- osv-coords4 versions
>= 2.3.0, < 2.3.1+ 3 more
- (no CPE)range: >= 2.3.0, < 2.3.1
- (no CPE)range: >= 2.3.0, < 2.3.1
- (no CPE)range: >= 2.3.0, < 2.3.1
- (no CPE)range: >= 2.3.0, < 2.3.1
- Range: = 2.3.0
Patches
Vulnerability mechanics
References
8- github.com/advisories/GHSA-p5f8-gfw5-33w4ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2020-15201ghsaADVISORY
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-281.yamlghsaWEB
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-316.yamlghsaWEB
- github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-124.yamlghsaWEB
- github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02ghsax_refsource_MISCWEB
- github.com/tensorflow/tensorflow/releases/tag/v2.3.1ghsax_refsource_MISCWEB
- github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4ghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.