Null-dereference in Tensorflow
Moderate severity
GitHub Reviewed
Published
Feb 2, 2022
in
tensorflow/tensorflow
•
Updated Feb 3, 2023
Description
Reviewed
Feb 4, 2022
Published by the National Vulnerability Database
Feb 4, 2022
Published to the GitHub Advisory Database
Feb 9, 2022
Last updated
Feb 3, 2023
Impact
When decoding a tensor from protobuf, TensorFlow might do a null-dereference if attributes of some mutable arguments to some operations are missing from the proto. This is guarded by a
DCHECK
:However,
DCHECK
is a no-op in production builds and an assertion failure in debug builds. In the first case execution proceeds to the dereferencing of the null pointer, whereas in the second case it results in a crash due to the assertion failure.Patches
We have patched the issue in GitHub commit 8a513cec4bec15961fbfdedcaa5376522980455c.
The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, and TensorFlow 2.6.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.
References