CVE-2021-29619: Segfault in `tf.raw_ops.SparseCountSparseOutput`
Impact Passing invalid arguments (e.g., discovered via fuzzing) to tf.rawops.SparseCountSparseOutput results in segfault.
Patches We have patched the issue in GitHub 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 for more information regarding the security model and how to contact us with issues and questions.
Other sources
TensorFlow is an end-to-end open source platform for machine learning. Passing invalid arguments (e.g., discovered via fuzzing) to tf.rawops.SparseCountSparseOutput results in segfault. 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.
Affected Software
Remediation
Event History
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.