CVE-2020-15202Critical· 9.0▾ MidnightInteger truncation in Shard API usage
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 49.5 · likelihood 0.3 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Exploit-prediction probability, daily snapshots since Jul 8.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
1.2%
1.2% → 1.3%
The Shard API in TensorFlow expects the last argument to be a function taking two int64 (i.e., long long) arguments:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/util/work_sharder.h#L59-L60
However, there are several places in TensorFlow where a lambda taking int or int32 arguments is being used:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/random_op.cc#L204-L205
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/random_op.cc#L317-L318
In these cases, if the amount of work to be parallelized is large enough, integer truncation occurs. Depending on how the two arguments of the lambda are used, this can result in segfaults, read/write outside of heap allocated arrays, stack overflows, or data corruption.
We have patched the issue in 27b417360cbd671ef55915e4bb6bb06af8b8a832 and ca8c013b5e97b1373b3bb1c97ea655e69f31a575. We 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.
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.
This vulnerability has been reported by members of the Aivul Team from Qihoo 360.
tensorflow < 1.15.4tensorflow >= 2.0.0, < 2.0.3tensorflow >= 2.1.0, < 2.1.2tensorflow >= 2.2.0, < 2.2.1tensorflow >= 2.3.0, < 2.3.1tensorflow-cpu < 1.15.4tensorflow-cpu >= 2.0.0, < 2.0.3tensorflow-cpu >= 2.1.0, < 2.1.2tensorflow-cpu >= 2.2.0, < 2.2.1tensorflow-cpu >= 2.3.0, < 2.3.1tensorflow-gpu < 1.15.4tensorflow-gpu >= 2.0.0, < 2.0.3tensorflow-gpu >= 2.1.0, < 2.1.2tensorflow-gpu >= 2.2.0, < 2.2.1tensorflow-gpu >= 2.3.0, < 2.3.1Upgrade to a patched release:
tensorflow 1.15.4tensorflow 2.0.3tensorflow 2.1.2tensorflow 2.2.1tensorflow 2.3.1tensorflow-cpu 1.15.4tensorflow-cpu 2.0.3tensorflow-cpu 2.1.2tensorflow-cpu 2.2.1tensorflow-cpu 2.3.1tensorflow-gpu 1.15.4tensorflow-gpu 2.0.3tensorflow-gpu 2.1.2tensorflow-gpu 2.2.1tensorflow-gpu 2.3.1Connected by shared product, vendor, weakness, or advisory.
CVE-2020-15207High· 8.7Segfault and data corruption in tensorflow-lite
CVE-2020-15203High· 7.5Denial of Service in Tensorflow
CVE-2020-15210Medium· 6.5Segmentation fault in tensorflow-lite
CVE-2020-15206Critical· 9.0Denial of Service in Tensorflow
CVE-2020-15193High· 7.1Memory corruption in Tensorflow
CVE-2020-15209Medium· 5.9Null pointer dereference in tensorflow-lite