First published: Fri Feb 04 2022(Updated: )
### Impact The implementation of `Range` suffers from integer overflows. These can trigger undefined behavior or, in some scenarios, extremely large allocations. ### Patches We have patched the issue in GitHub commit [f0147751fd5d2ff23251149ebad9af9f03010732](https://github.com/tensorflow/tensorflow/commit/f0147751fd5d2ff23251149ebad9af9f03010732) (merging [#51733](https://github.com/tensorflow/tensorflow/pull/51733)). The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, 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/52676).
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Google TensorFlow | <=2.5.2 | |
Google TensorFlow | >=2.6.0<=2.6.2 | |
Google TensorFlow | =2.7.0 | |
pip/tensorflow-gpu | =2.7.0 | 2.7.1 |
pip/tensorflow-gpu | >=2.6.0<2.6.3 | 2.6.3 |
pip/tensorflow-gpu | <2.5.3 | 2.5.3 |
pip/tensorflow-cpu | =2.7.0 | 2.7.1 |
pip/tensorflow-cpu | >=2.6.0<2.6.3 | 2.6.3 |
pip/tensorflow-cpu | <2.5.3 | 2.5.3 |
pip/tensorflow | =2.7.0 | 2.7.1 |
pip/tensorflow | >=2.6.0<2.6.3 | 2.6.3 |
pip/tensorflow | <2.5.3 | 2.5.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.