CVE-2020-26268Medium· 4.4▾ SunlitWrite to immutable memory region in TensorFlow
▾ Sunlit zone — Low / medium · no exploitation signal
impact 24.2 · likelihood 0 · 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 Sep 12.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.2%
The tf.raw_ops.ImmutableConst operation returns a constant tensor created from a memory mapped file which is assumed immutable. However, if the type of the tensor is not an integral type, the operation crashes the Python interpreter as it tries to write to the memory area:
>>> import tensorflow as tf
>>> with open('/tmp/test.txt','w') as f: f.write('a'*128)
>>> tf.raw_ops.ImmutableConst(dtype=tf.string,shape=2,
memory_region_name='/tmp/test.txt')
If the file is too small, TensorFlow properly returns an error as the memory area has fewer bytes than what is needed for the tensor it creates. However, as soon as there are enough bytes, the above snippet causes a segmentation fault.
This is because the alocator used to return the buffer data is not marked as returning an opaque handle since the needed virtual method is not overriden.
We have patched the issue in GitHub commit c1e1fc899ad5f8c725dcbb6470069890b5060bc7 and will release TensorFlow 2.4.0 containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.
Since this issue also impacts TF versions before 2.4, we will patch all releases between 1.15 and 2.3 inclusive.
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.5tensorflow >= 2.0.0, < 2.0.4tensorflow >= 2.1.0, < 2.1.3tensorflow >= 2.2.0, < 2.2.2tensorflow >= 2.3.0, < 2.3.2tensorflow-cpu < 1.15.5tensorflow-cpu >= 2.0.0, < 2.0.4tensorflow-cpu >= 2.1.0, < 2.1.3tensorflow-cpu >= 2.2.0, < 2.2.2tensorflow-cpu >= 2.3.0, < 2.3.2tensorflow-gpu < 1.15.5tensorflow-gpu >= 2.0.0, < 2.0.4tensorflow-gpu >= 2.1.0, < 2.1.3tensorflow-gpu >= 2.2.0, < 2.2.2tensorflow-gpu >= 2.3.0, < 2.3.2Upgrade to a patched release:
tensorflow 1.15.5tensorflow 2.0.4tensorflow 2.1.3tensorflow 2.2.2tensorflow 2.3.2tensorflow-cpu 1.15.5tensorflow-cpu 2.0.4tensorflow-cpu 2.1.3tensorflow-cpu 2.2.2tensorflow-cpu 2.3.2tensorflow-gpu 1.15.5tensorflow-gpu 2.0.4tensorflow-gpu 2.1.3tensorflow-gpu 2.2.2tensorflow-gpu 2.3.2Connected by shared product, vendor, weakness, or advisory.
CVE-2021-29541Low· 2.5Null pointer dereference in `StringNGrams`
CVE-2021-29525Low· 2.5Division by 0 in `Conv2DBackpropInput`
CVE-2021-29527Low· 2.5Division by 0 in `QuantizedConv2D`
CVE-2021-29524Low· 2.5Division by 0 in `Conv2DBackpropFilter`
CVE-2020-15207High· 8.7Segfault and data corruption in tensorflow-lite
CVE-2021-29535Low· 2.5Heap buffer overflow in `QuantizedMul`