CWE
471
Advisory Published
CVE Published
Updated

CVE-2020-26268: Write to immutable memory region in TensorFlow

First published: Thu Dec 10 2020(Updated: )

### Impact 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: ```python >>> 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](https://github.com/tensorflow/tensorflow/blob/c1e1fc899ad5f8c725dcbb6470069890b5060bc7/tensorflow/core/framework/typed_allocator.h#L78-L85) is [not overriden](https://github.com/tensorflow/tensorflow/blob/acdf3c04fcfa767ae8d109b9e1f727ef050dba4d/tensorflow/core/kernels/immutable_constant_op.cc). ### Patches We have patched the issue in GitHub commit [c1e1fc899ad5f8c725dcbb6470069890b5060bc7](https://github.com/tensorflow/tensorflow/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. ### 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 SoftwareAffected VersionHow to fix
Google TensorFlow<1.15.5
Google TensorFlow>=2.0.0<2.0.4
Google TensorFlow>=2.1.0<2.1.3
Google TensorFlow>=2.2.0<2.2.2
Google TensorFlow>=2.3.0<2.3.2
pip/tensorflow-gpu>=2.3.0<2.3.2
2.3.2
pip/tensorflow-gpu>=2.2.0<2.2.2
2.2.2
pip/tensorflow-gpu>=2.1.0<2.1.3
2.1.3
pip/tensorflow-gpu>=2.0.0<2.0.4
2.0.4
pip/tensorflow-gpu<1.15.5
1.15.5
pip/tensorflow-cpu>=2.3.0<2.3.2
2.3.2
pip/tensorflow-cpu>=2.2.0<2.2.2
2.2.2
pip/tensorflow-cpu>=2.1.0<2.1.3
2.1.3
pip/tensorflow-cpu>=2.0.0<2.0.4
2.0.4
pip/tensorflow-cpu<1.15.5
1.15.5
pip/tensorflow>=2.3.0<2.3.2
2.3.2
pip/tensorflow>=2.2.0<2.2.2
2.2.2
pip/tensorflow>=2.1.0<2.1.3
2.1.3
pip/tensorflow>=2.0.0<2.0.4
2.0.4
pip/tensorflow<1.15.5
1.15.5
<1.15.5
>=2.0.0<2.0.4
>=2.1.0<2.1.3
>=2.2.0<2.2.2
>=2.3.0<2.3.2

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203