CVE-2021-41202: Overflow/crash in `tf.range`
First published: Fri Nov 05 2021(Updated: )
### Impact While calculating the size of the output within the `tf.range` kernel, there is a conditional statement of type `int64 = condition ? int64 : double`. Due to C++ implicit conversion rules, both branches of the condition will be cast to `double` and the result would be truncated before the assignment. This result in overflows: ```python import tensorflow as tf tf.sparse.eye(num_rows=9223372036854775807, num_columns=None) ``` Similarly, `tf.range` would result in crashes due to overflows if the start or end point are too large. ```python import tensorflow as tf tf.range(start=-1e+38, limit=1) ``` ### Patches We have patched the issue in GitHub commits [6d94002a09711d297dbba90390d5482b76113899](https://github.com/tensorflow/tensorflow/commit/6d94002a09711d297dbba90390d5482b76113899) (merging [#51359](https://github.com/tensorflow/tensorflow/pull/51359)) and [1b0e0ec27e7895b9985076eab32445026ae5ca94](https://github.com/tensorflow/tensorflow/commit/1b0e0ec27e7895b9985076eab32445026ae5ca94) (merging [#51711](https://github.com/tensorflow/tensorflow/pull/51711)). 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 [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46912), [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46899) and [GitHub issue](https://github.com/tensorflow/tensorflow/issues/46889).
Credit: security-advisories@github.com security-advisories@github.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| 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 |
| TensorFlow Keras | >=2.4.0<2.4.4 | |
| TensorFlow Keras | >=2.6.0<2.6.1 | |
| TensorFlow Keras | =2.7.0-rc0 | |
| TensorFlow Keras | =2.7.0-rc1 |
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/1b0e0ec27e7895b9985076eab32445026ae5ca94
- https://github.com/tensorflow/tensorflow/commit/6d94002a09711d297dbba90390d5482b76113899
- https://github.com/tensorflow/tensorflow/issues/46889
- https://github.com/tensorflow/tensorflow/issues/46912
- https://github.com/tensorflow/tensorflow/security/advisories/GHSA-xrqm-fpgr-6hhx
- https://nvd.nist.gov/vuln/detail/CVE-2021-41202
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-cpu/PYSEC-2021-612.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow-gpu/PYSEC-2021-810.yaml
- https://github.com/pypa/advisory-database/tree/main/vulns/tensorflow/PYSEC-2021-395.yaml
- https://github.com/advisories/GHSA-xrqm-fpgr-6hhx (Advisory)
Frequently Asked Questions
What is the severity of CVE-2021-41202?
CVE-2021-41202 has a severity rating that indicates a moderate risk of exploitation due to improper size calculations in the tf.range kernel.
Which versions of TensorFlow are affected by CVE-2021-41202?
CVE-2021-41202 affects TensorFlow versions from 2.4.0 to 2.4.4, 2.6.0 to 2.6.1, and certain release candidates of 2.7.0.
How do I fix CVE-2021-41202?
To fix CVE-2021-41202, upgrade TensorFlow to version 2.4.4, 2.5.2, or 2.6.1 as applicable.
What causes the vulnerability in CVE-2021-41202?
The vulnerability in CVE-2021-41202 is caused by C++ implicit conversion rules affecting size calculations in the tf.range kernel.
Is CVE-2021-41202 a critical security issue?
CVE-2021-41202 is not classified as critical, but it poses a risk that should be addressed by updating the affected software.
- agent/type
- agent/remedy
- collector/mitre-cve
- source/MITRE
- agent/severity
- agent/weakness
- agent/title
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-xrqm-fpgr-6hhx
- alias/CVE-2021-41202
- agent/software-canonical-lookup
- agent/author
- agent/references
- agent/description
- agent/softwarecombine
- agent/event
- collector/github-advisory
- agent/last-modified-date
- agent/trending
- agent/source
- agent/tags
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-api
- collector/nvd-index
- package-manager/pip
- vendor/google
- canonical/tensorflow keras
- version/tensorflow keras/2.4.0
- version/tensorflow keras/2.5.0
- version/tensorflow keras/2.6.0
- version/tensorflow keras/2.7.0-rc0
- version/tensorflow keras/2.7.0-rc1