Missing validation in `QuantizedConv2D` results in undefined behavior in TensorFlow
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
≥ 2.7.0 · < 2.7.2≥ 2.8.0 · < 2.8.1
|
| tensorflow-gpu PyPI |
|
|
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.QuantizedConv2D` does not fully validate the input arguments. In this case, references get bound to `nullptr` for each argument that is empty. Versions 2.9.0, 2.8.1, 2.7.2, and 2.6.4 contain a patch for this issue.
From the CVE record · GitHub_M
`tf.raw_ops.QuantizedConv2D` does not fully validate its inputs and binds references to `nullptr` for empty arguments. An attacker who can provide empty arguments can trigger this behavior; the input does not specify whether network access, authentication, or user interaction is required.
Check users of the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages on versions below 2.6.4, from 2.7.0 to below 2.7.2, or from 2.8.0 to below 2.8.1.