CWE
125 908
Advisory Published
CVE Published
Updated

CVE-2020-26271: Heap out of bounds access in MakeEdge in TensorFlow

First published: Thu Dec 10 2020(Updated: )

### Impact Under certain cases, loading a saved model can result in accessing uninitialized memory while building the computation graph. The [`MakeEdge` function](https://github.com/tensorflow/tensorflow/blob/3616708cb866365301d8e67b43b32b46d94b08a0/tensorflow/core/common_runtime/graph_constructor.cc#L1426-L1438) creates an edge between one output tensor of the `src` node (given by `output_index`) and the input slot of the `dst` node (given by `input_index`). This is only possible if the types of the tensors on both sides coincide, so the function begins by obtaining the corresponding `DataType` values and comparing these for equality: ```cc DataType src_out = src->output_type(output_index); DataType dst_in = dst->input_type(input_index); //... ``` However, there is no check that the indices point to inside of the arrays they index into. Thus, this can result in accessing data out of bounds of the corresponding heap allocated arrays. In most scenarios, this can manifest as unitialized data access, but if the index points far away from the boundaries of the arrays this can be used to leak addresses from the library. ### Patches We have patched the issue in GitHub commit [0cc38aaa4064fd9e79101994ce9872c6d91f816b](https://github.com/tensorflow/tensorflow/commit/0cc38aaa4064fd9e79101994ce9872c6d91f816b) 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.

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

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.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203