CVE-2022-23595: Null pointer dereference in TensorFlow
Impact When building an XLA compilation cache, if default settings are used, TensorFlow triggers a null pointer dereference:
cc string allowedgpus = flr->configproto()->gpuoptions().visibledevicelist(); In the default scenario, all devices are allowed, so flr->configproto is nullptr. Patches We have patched the issue in GitHub commit e21af685e1828f7ca65038307df5cc06de4479e8. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, 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 Open Source Machine Learning Framework. When building an XLA compilation cache, if default settings are used, TensorFlow triggers a null pointer dereference. In the default scenario, all devices are allowed, so flr->configproto is nullptr. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2022-23595?
The severity of CVE-2022-23595 is classified as medium due to the potential for a denial of service through a null pointer dereference.
How do I fix CVE-2022-23595?
To fix CVE-2022-23595, upgrade TensorFlow to version 2.5.3, 2.6.3, or 2.7.1, depending on your currently installed version.
What versions of TensorFlow are affected by CVE-2022-23595?
CVE-2022-23595 affects TensorFlow versions 2.5.2 and earlier as well as versions from 2.6.0 to 2.6.2 and 2.7.0.
What is the impact of CVE-2022-23595?
The impact of CVE-2022-23595 includes potential denial of service due to application crashes resulting from a null pointer dereference.
Is CVE-2022-23595 remote exploitability?
CVE-2022-23595 is not considered remotely exploitable as it requires specific conditions to trigger the vulnerability.