Insecure functionality In tensorflow
Description
TensorFlow vulnerable to CHECK fail in FakeQuantWithMinMaxVarsGradient
Impact
When tf.quantization.fake_quant_with_min_max_vars_gradient receives input min or max that is nonscalar, it gives a CHECK fail that can trigger a denial of service attack.
import tensorflow as tf import numpy as np arg_0=tf.constant(value=np.random.random(size=(2, 2)), shape=(2, 2), dtype=tf.float32) arg_1=tf.constant(value=np.random.random(size=(2, 2)), shape=(2, 2), dtype=tf.float32) arg_2=tf.constant(value=np.random.random(size=(2, 2)), shape=(2, 2), dtype=tf.float32) arg_3=tf.constant(value=np.random.random(size=(2, 2)), shape=(2, 2), dtype=tf.float32) arg_4=8 arg_5=False...
Patches
We have patched the issue in GitHub commit f3cf67ac5705f4f04721d15e485e192bb319feed.
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.
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
刘力源, Information System & Security and Countermeasures Experiments Center, Beijing Institute of Technology
Neophytos Christou, Secure Systems Labs, Brown University
Mitigation
Update Impact
Minimal update. May introduce new vulnerabilities or breaking changes.
Ecosystem | Component | Affected version | Patched versions |
|---|---|---|---|
pypi | 2.7.2, 2.8.1, 2.9.1 | ||
pypi | 2.7.2, 2.8.1, 2.9.1 | ||
pypi | 2.7.2, 2.8.1, 2.9.1 |
Aliases
References