First published: Fri Sep 25 2020(Updated: )
### Impact To mimic Python's indexing with negative values, TFLite uses `ResolveAxis` to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/reduce.h#L68-L72 If the `DCHECK` does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption. ### Patches We have patched the issue in 2d88f470dea2671b430884260f3626b1fe99830a and will release patch releases for all versions between 1.15 and 2.3. We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1. ### 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 by members of the Aivul Team from Qihoo 360.
Credit: security-advisories@github.com security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
pip/tensorflow-gpu | =2.3.0 | 2.3.1 |
pip/tensorflow-gpu | =2.2.0 | 2.2.1 |
pip/tensorflow-gpu | >=2.1.0<2.1.2 | 2.1.2 |
pip/tensorflow-gpu | >=2.0.0<2.0.3 | 2.0.3 |
pip/tensorflow-gpu | <1.15.4 | 1.15.4 |
pip/tensorflow-cpu | =2.3.0 | 2.3.1 |
pip/tensorflow-cpu | =2.2.0 | 2.2.1 |
pip/tensorflow-cpu | >=2.1.0<2.1.2 | 2.1.2 |
pip/tensorflow-cpu | >=2.0.0<2.0.3 | 2.0.3 |
pip/tensorflow-cpu | <1.15.4 | 1.15.4 |
pip/tensorflow | =2.3.0 | 2.3.1 |
pip/tensorflow | =2.2.0 | 2.2.1 |
pip/tensorflow | >=2.1.0<2.1.2 | 2.1.2 |
pip/tensorflow | >=2.0.0<2.0.3 | 2.0.3 |
pip/tensorflow | <1.15.4 | 1.15.4 |
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 | =15.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2020-15207 has not been explicitly assigned a CVSS score, but it can lead to potential out-of-bounds read vulnerabilities.
To fix CVE-2020-15207, update TensorFlow to version 2.3.1 or later.
CVE-2020-15207 affects TensorFlow versions 2.3.0, 2.2.0, 2.1.0, 2.0.0, and 1.15.4.
CVE-2020-15207 affects both TensorFlow GPU and TensorFlow CPU installations.
Yes, CVE-2020-15207 potentially affects users of TensorFlow Lite due to how it handles negative indexing.