CVE-2021-41196: Crash in `max_pool3d` when size argument is 0 or negative
First published: Fri Nov 05 2021(Updated: )
### Impact The Keras pooling layers can trigger a segfault if the size of the pool is 0 or if a dimension is negative: ```python import tensorflow as tf pool_size = [2, 2, 0] layer = tf.keras.layers.MaxPooling3D(strides=1, pool_size=pool_size) input_tensor = tf.random.uniform([3, 4, 10, 11, 12], dtype=tf.float32) res = layer(input_tensor) ``` 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. ### Patches We have patched the issue in GitHub commit [12b1ff82b3f26ff8de17e58703231d5a02ef1b8b](https://github.com/tensorflow/tensorflow/commit/12b1ff82b3f26ff8de17e58703231d5a02ef1b8b) (merging [#51975](https://github.com/tensorflow/tensorflow/pull/51975)). 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. ### For more information Please consult [our security guide](https://github.com/tensorflow/tensorflow/blob/master/SECURITY.md) for more information regarding the security model and how to contact us with issues and questions. ### Attribution This vulnerability has been reported externally via a [GitHub issue](https://github.com/tensorflow/tensorflow/issues/51936).
Credit: security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Google TensorFlow | <2.4.4 | |
| Google TensorFlow | >=2.5.0<2.5.2 | |
| Google TensorFlow | >=2.6.0<2.6.1 | |
| pip/tensorflow-gpu | <2.4.4 | 2.4.4 |
| pip/tensorflow-gpu | >=2.5.0<2.5.2 | 2.5.2 |
| pip/tensorflow-gpu | >=2.6.0<2.6.1 | 2.6.1 |
| pip/tensorflow-cpu | <2.4.4 | 2.4.4 |
| pip/tensorflow-cpu | >=2.5.0<2.5.2 | 2.5.2 |
| pip/tensorflow-cpu | >=2.6.0<2.6.1 | 2.6.1 |
| pip/tensorflow | <2.4.4 | 2.4.4 |
| pip/tensorflow | >=2.5.0<2.5.2 | 2.5.2 |
| pip/tensorflow | >=2.6.0<2.6.1 | 2.6.1 |
| <2.4.4 | ||
| >=2.5.0<2.5.2 | ||
| >=2.6.0<2.6.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://github.com/tensorflow/tensorflow/commit/12b1ff82b3f26ff8de17e58703231d5a02ef1b8b
- https://github.com/tensorflow/tensorflow/issues/51936
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-m539-j985-hcr8
- https://nvd.nist.gov/vuln/detail/CVE-2021-41196
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-606.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-804.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-389.yaml
- https://github.com/advisories/GHSA-m539-j985-hcr8 (Advisory)
- collector/nvd-index
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/remedy
- agent/title
- agent/first-publish-date
- agent/references
- agent/description
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup
- agent/author
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-m539-j985-hcr8
- alias/CVE-2021-41196
- collector/github-advisory
- collector/nvd-api
- agent/last-modified-date
- agent/softwarecombine
- agent/tags
- agent/event
- agent/trending
- vendor/google
- canonical/google tensorflow
- version/google tensorflow/2.5.0
- version/google tensorflow/2.6.0
- package-manager/pip