CVE-2020-15196
Last modified
CVE-2020-15196 is a critical-severity vulnerability rated 9.9/10 on the CVSS scale. 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. EPSS estimates a 0.90% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Tensorflow | 2.3.0 |
References
- https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02Patch, Third Party Advisory
- https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1Third Party Advisory
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cphExploit, Third Party Advisory
- https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02Patch, Third Party Advisory
- https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1Third Party Advisory
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-pg59-2f92-5cphExploit, Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-15196?
How severe is CVE-2020-15196?
How do I fix CVE-2020-15196?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2020
- CVE-2020-15190In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 an…5.3
- CVE-2020-15191In Tensorflow before versions 2.2.1 and 2.3.1, if a user pas…5.3
- CVE-2020-15192In Tensorflow before versions 2.2.1 and 2.3.1, if a user pas…4.3
- CVE-2020-15193In Tensorflow before versions 2.2.1 and 2.3.1, the implement…7.1
- CVE-2020-15194In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 an…5.3
- CVE-2020-15195In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 an…8.8
- CVE-2020-15197In Tensorflow before version 2.3.1, the `SparseCountSparseOu…6.3
- CVE-2020-15198In Tensorflow before version 2.3.1, the `SparseCountSparseOu…5.4
- CVE-2020-15199In Tensorflow before version 2.3.1, the `RaggedCountSparseOu…5.9
- CVE-2020-1520A remote code execution vulnerability exists when the Window…7.8
- CVE-2020-15200In Tensorflow before version 2.3.1, the `RaggedCountSparseOu…5.9
- CVE-2020-15201In Tensorflow before version 2.3.1, the `RaggedCountSparseOu…4.8
Are you affected by CVE-2020-15196?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
