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.
| Software | From | Fixed in |
|---|---|---|
| google / tensorflow | - | 1.15.4 |
| google / tensorflow | 2.0.0 | 2.0.3 |
| google / tensorflow | 2.1.0 | 2.1.2 |
| google / tensorflow | 2.2.0 | 2.2.1 |
| google / tensorflow | 2.3.0 | 2.3.1 |
| opensuse / leap | 15.2 | 15.2.x |
tensorflow
|
- | 1.15.4 |
tensorflow
|
2.0.0 | 2.0.3 |
tensorflow
|
2.1.0 | 2.1.2 |
tensorflow
|
2.2.0 | 2.2.0.x |
tensorflow
|
2.2.0 | 2.2.1 |
tensorflow
|
2.3.0 | 2.3.0.x |
tensorflow
|
2.3.0 | 2.3.1 |
tensorflow-cpu
|
- | 1.15.4 |
tensorflow-cpu
|
2.0.0 | 2.0.3 |
tensorflow-cpu
|
2.1.0 | 2.1.2 |
tensorflow-cpu
|
2.2.0 | 2.2.0.x |
tensorflow-cpu
|
2.2.0 | 2.2.1 |
tensorflow-cpu
|
2.3.0 | 2.3.0.x |
tensorflow-cpu
|
2.3.0 | 2.3.1 |
tensorflow-gpu
|
- | 1.15.4 |
tensorflow-gpu
|
2.0.0 | 2.0.3 |
tensorflow-gpu
|
2.1.0 | 2.1.2 |
tensorflow-gpu
|
2.2.0 | 2.2.0.x |
tensorflow-gpu
|
2.2.0 | 2.2.1 |
tensorflow-gpu
|
2.3.0 | 2.3.0.x |
tensorflow-gpu
|
2.3.0 | 2.3.1 |