Crash in `max_pool3d` when size argument is 0 or negative
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
|
| tensorflow-gpu PyPI |
|
|
TensorFlow is an open source platform for machine learning. In affected versions the Keras pooling layers can trigger a segfault if the size of the pool is 0 or if a dimension is negative. This is due to the TensorFlow's implementation of pooling operations where the values in the sliding window are not checked to be strictly positive. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.
From the CVE record · GitHub_M
Affected TensorFlow Keras pooling layers can segfault when the pool size is zero or a dimension is negative. The pooling operations do not check that sliding-window values are strictly positive. The input does not specify whether an attacker can supply these values or whether authentication or user interaction is required.
Teams using the PyPI packages tensorflow, tensorflow-cpu, or tensorflow-gpu should check versions <2.4.4, >=2.5.0 and <2.5.2, >=2.6.0 and <2.6.1, or >=2.7.0rc0 and <2.7.0.