CVE-2021-29619: Segfault in `tf.raw_ops.SparseCountSparseOutput`
First published: Fri May 14 2021(Updated: )
### Impact Passing invalid arguments (e.g., discovered via fuzzing) to `tf.raw_ops.SparseCountSparseOutput` results in segfault. ### Patches We have patched the issue in GitHub commit [82e6203221865de4008445b13c69b6826d2b28d9](https://github.com/tensorflow/tensorflow/commit/82e6203221865de4008445b13c69b6826d2b28d9). The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range. ### 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.
Credit: security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| pip/tensorflow-gpu | >=2.4.0<2.4.2 | 2.4.2 |
| pip/tensorflow-gpu | >=2.3.0<2.3.3 | 2.3.3 |
| pip/tensorflow-gpu | >=2.2.0<2.2.3 | 2.2.3 |
| pip/tensorflow-gpu | <2.1.4 | 2.1.4 |
| pip/tensorflow-cpu | >=2.4.0<2.4.2 | 2.4.2 |
| pip/tensorflow-cpu | >=2.3.0<2.3.3 | 2.3.3 |
| pip/tensorflow-cpu | >=2.2.0<2.2.3 | 2.2.3 |
| pip/tensorflow-cpu | <2.1.4 | 2.1.4 |
| pip/tensorflow | >=2.4.0<2.4.2 | 2.4.2 |
| pip/tensorflow | >=2.3.0<2.3.3 | 2.3.3 |
| pip/tensorflow | >=2.2.0<2.2.3 | 2.2.3 |
| pip/tensorflow | <2.1.4 | 2.1.4 |
| TensorFlow Keras | <2.1.4 | |
| TensorFlow Keras | >=2.2.0<2.2.3 | |
| TensorFlow Keras | >=2.3.0<2.3.3 | |
| TensorFlow Keras | >=2.4.0<2.4.2 |
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/82e6203221865de4008445b13c69b6826d2b28d9
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-wvjw-p9f5-vq28
- https://nvd.nist.gov/vuln/detail/CVE-2021-29619
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-547.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-745.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-256.yaml
- https://github.com/advisories/GHSA-wvjw-p9f5-vq28 (Advisory)
Frequently Asked Questions
What is the severity of CVE-2021-29619?
CVE-2021-29619 has a high severity due to potential segmentation faults caused by invalid inputs.
How do I fix CVE-2021-29619?
You can fix CVE-2021-29619 by upgrading to TensorFlow version 2.4.2 or later.
Which versions of TensorFlow are affected by CVE-2021-29619?
CVE-2021-29619 affects TensorFlow versions prior to 2.1.4 and those between 2.2.0 to 2.2.3, 2.3.0 to 2.3.3, and 2.4.0 to 2.4.2.
What operation is vulnerable in CVE-2021-29619?
The vulnerability in CVE-2021-29619 is related to the `tf.raw_ops.SparseCountSparseOutput` operation.
Is CVE-2021-29619 a denial of service vulnerability?
Yes, CVE-2021-29619 can lead to denial of service conditions due to a segmentation fault.
- agent/type
- agent/remedy
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/severity
- agent/weakness
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-wvjw-p9f5-vq28
- alias/CVE-2021-29619
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/references
- agent/softwarecombine
- agent/description
- agent/event
- agent/author
- collector/github-advisory
- agent/trending
- agent/source
- agent/tags
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-index
- package-manager/pip
- vendor/google
- canonical/tensorflow keras
- version/tensorflow keras/2.2.0
- version/tensorflow keras/2.3.0
- version/tensorflow keras/2.4.0