Segfault in Tensorflow
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
< 2.4.0
|
In Tensorflow before version 2.4.0, an attacker can pass an invalid `axis` value to `tf.quantization.quantize_and_dequantize`. This results in accessing a dimension outside the rank of the input tensor in the C++ kernel implementation. However, dim_size only does a DCHECK to validate the argument and then uses it to access the corresponding element of an array. Since in normal builds, `DCHECK`-like macros are no-ops, this results in segfault and access out of bounds of the array. The issue is patched in eccb7ec454e6617738554a255d77f08e60ee0808 and TensorFlow 2.4.0 will be released containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.
From the CVE record · GitHub_M
TensorFlow before 2.4.0 does not safely handle an invalid `axis` value passed to `tf.quantization.quantize_and_dequantize`. An attacker who can supply that value can cause an out-of-bounds array access and a segmentation fault. The input does not specify network access, authentication requirements, or user interaction.
Anyone running the PyPI packages tensorflow, tensorflow-cpu, or tensorflow-gpu at versions earlier than 2.4.0 should check their installation.