Denial of Service in Tensorflow
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
2.3.1| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
In Tensorflow before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, the `SparseFillEmptyRowsGrad` implementation has incomplete validation of the shapes of its arguments. Although `reverse_index_map_t` and `grad_values_t` are accessed in a similar pattern, only `reverse_index_map_t` is validated to be of proper shape. Hence, malicious users can pass a bad `grad_values_t` to trigger an assertion failure in `vec`, causing denial of service in serving installations. The issue is patched in commit 390611e0d45c5793c7066110af37c8514e6a6c54, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1."
From the CVE record · GitHub_M
TensorFlow's SparseFillEmptyRowsGrad incompletely validates argument shapes. A malicious user who can supply a malformed grad_values_t can trigger an assertion failure, causing denial of service in serving installations. The input does not specify whether authentication or other user interaction is required.
Operators using PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu versions below 1.15.4, or in the 2.0.x, 2.1.x, 2.2.x, or 2.3.x lines before 2.0.3, 2.1.2, 2.2.1, or 2.3.1, respectively, should check their installations.