CVE-2020-15198: Heap buffer overflow in Tensorflow
First published: Fri Sep 25 2020(Updated: )
### Impact The `SparseCountSparseOutput` implementation does not validate that the input arguments form a valid sparse tensor. In particular, there is no validation that the `indices` tensor has the same shape as the `values` one. The values in these tensors are always accessed in parallel: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L193-L195 Thus, a shape mismatch can result in accesses outside the bounds of heap allocated buffers. ### Patches We have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release. We recommend users to upgrade to TensorFlow 2.3.1. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)
Credit: security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google TensorFlow | >=2.3.0<2.3.1 | |
| pip/tensorflow-gpu | =2.3.0 | 2.3.1 |
| pip/tensorflow-cpu | =2.3.0 | 2.3.1 |
| pip/tensorflow | =2.3.0 | 2.3.1 |
| >=2.3.0<2.3.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/tensorflow/tensorflow/commit/3cbb917b4714766030b28eba9fb41bb97ce9ee02
- https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-jc87-6vpp-7ff3
- https://nvd.nist.gov/vuln/detail/CVE-2020-15198
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2020-278.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2020-313.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2020-121.yaml
- https://github.com/advisories/GHSA-jc87-6vpp-7ff3 (Advisory)
Frequently Asked Questions
What is the severity of CVE-2020-15198?
CVE-2020-15198 has a medium severity rating due to the risk of unexpected behavior in TensorFlow implementations.
How do I fix CVE-2020-15198?
To fix CVE-2020-15198, update TensorFlow to version 2.3.1 or later.
Which versions of TensorFlow are affected by CVE-2020-15198?
CVE-2020-15198 affects TensorFlow versions 2.3.0 and below.
What is the main issue with CVE-2020-15198 in TensorFlow?
The main issue with CVE-2020-15198 is the lack of validation for the shape of input tensors during sparse tensor operations.
Can I use any substitute for TensorFlow to avoid CVE-2020-15198?
While there are alternatives to TensorFlow, the best approach is to update TensorFlow to mitigate CVE-2020-15198.
- collector/nvd-index
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/remedy
- agent/severity
- agent/weakness
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-jc87-6vpp-7ff3
- alias/CVE-2020-15198
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/references
- agent/description
- agent/first-publish-date
- agent/author
- agent/softwarecombine
- agent/event
- collector/nvd-cve
- source/NVD
- collector/github-advisory
- agent/trending
- agent/tags
- agent/source
- vendor/google
- canonical/google tensorflow
- version/google tensorflow/2.3.0
- package-manager/pip