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, by controlling the `fill` argument of tf.strings.as_string, a malicious attacker is able to trigger a format string vulnerability due to the way the internal format use in a `printf` call is constructed. This may result in segmentation fault. The issue is patched in commit 33be22c65d86256e6826666662e40dbdfe70ee83, 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 constructs an internal printf format from the fill argument of tf.strings.as_string. An attacker who can control that argument can trigger a format-string vulnerability that may cause a segmentation fault. The input does not specify network access, authentication, or user-interaction requirements.
Check PyPI tensorflow, tensorflow-cpu, and tensorflow-gpu installations on affected release lines: versions below 1.15.4, 2.0.0–2.0.2, 2.1.0–2.1.1, 2.2.0, and 2.3.0.