Headline
GHSA-2p9q-h29j-3f5v: Missing validation causes `TensorSummaryV2` to crash
Impact
The implementation of tf.raw_ops.TensorSummaryV2 does not fully validate the input arguments. This results in a CHECK-failure which can be used to trigger a denial of service attack:
import numpy as np
import tensorflow as tf
tf.raw_ops.TensorSummaryV2(
tag=np.array('test'),
tensor=np.array(3),
serialized_summary_metadata=tf.io.encode_base64(np.empty((0))))
The code assumes axis is a scalar but there is no validation for this.
const Tensor& serialized_summary_metadata_tensor = c->input(2);
// ...
ParseFromTString(serialized_summary_metadata_tensor.scalar<tstring>()(),
v->mutable_metadata());
Patches
We have patched the issue in GitHub commit 290bb05c80c327ed74fae1d089f1001b1e2a4ef7.
The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.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.
Attribution
This vulnerability has been reported by Neophytos Christou from Secure Systems Lab at Brown University and Hong Jin from Singapore Management University.
Impact
The implementation of tf.raw_ops.TensorSummaryV2 does not fully validate the input arguments. This results in a CHECK-failure which can be used to trigger a denial of service attack:
import numpy as np import tensorflow as tf
tf.raw_ops.TensorSummaryV2( tag=np.array(‘test’), tensor=np.array(3), serialized_summary_metadata=tf.io.encode_base64(np.empty((0))))
The code assumes axis is a scalar but there is no validation for this.
const Tensor& serialized\_summary\_metadata\_tensor = c->input(2);
// ...
ParseFromTString(serialized\_summary\_metadata\_tensor.scalar<tstring>()(),
v->mutable\_metadata());
Patches
We have patched the issue in GitHub commit 290bb05c80c327ed74fae1d089f1001b1e2a4ef7.
The fix will be included in TensorFlow 2.9.0. We will also cherrypick this commit on TensorFlow 2.8.1, TensorFlow 2.7.2, and TensorFlow 2.6.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.
Attribution
This vulnerability has been reported by Neophytos Christou from Secure Systems Lab at Brown University and Hong Jin from Singapore Management University.
References
- GHSA-2p9q-h29j-3f5v
- https://nvd.nist.gov/vuln/detail/CVE-2022-29193
- tensorflow/tensorflow@290bb05
- https://github.com/tensorflow/tensorflow/blob/f3b9bf4c3c0597563b289c0512e98d4ce81f886e/tensorflow/core/kernels/summary_tensor_op.cc#L33-L58
- https://github.com/tensorflow/tensorflow/releases/tag/v2.6.4
- https://github.com/tensorflow/tensorflow/releases/tag/v2.7.2
- https://github.com/tensorflow/tensorflow/releases/tag/v2.8.1
- https://github.com/tensorflow/tensorflow/releases/tag/v2.9.0
Related news
TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, the implementation of `tf.raw_ops.TensorSummaryV2` does not fully validate the input arguments. This results in a `CHECK`-failure which can be used to trigger a denial of service attack. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.
TensorFlow is an open source platform for machine learning. Prior to versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4, multiple TensorFlow operations misbehave in eager mode when the resource handle provided to them is invalid. In graph mode, it would have been impossible to perform these API calls, but migration to TF 2.x eager mode opened up this vulnerability. If the resource handle is empty, then a reference is bound to a null pointer inside TensorFlow codebase (various codepaths). This is undefined behavior. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.