CVE-2022-35982: Segfault in `SparseBincount` in TensorFlow
TensorFlow is an open source platform for machine learning. If SparseBincount is given inputs for indices, values, and denseshape that do not make a valid sparse tensor, it results in a segfault that can be used to trigger a denial of service attack. We have patched the issue in GitHub commit 40adbe4dd15b582b0210dfbf40c243a62f5119fa. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2022-35982?
CVE-2022-35982 has a severity rating of high due to its potential for denial of service attacks.
How do I fix CVE-2022-35982?
To fix CVE-2022-35982, update TensorFlow to version 2.10-rc4 or later.
What product is affected by CVE-2022-35982?
CVE-2022-35982 affects Google TensorFlow versions prior to 2.10-rc4.
What type of vulnerability is CVE-2022-35982?
CVE-2022-35982 is a segmentation fault vulnerability that can trigger denial of service.
What are the conditions that trigger CVE-2022-35982?
CVE-2022-35982 is triggered when SparseBincount receives invalid inputs for indices, values, and dense_shape.