8.6
CWE
787
Advisory Published
CVE Published
Updated

CVE-2020-15212: Out of bounds access in tensorflow-lite

First published: Fri Sep 25 2020(Updated: )

### Impact In TensorFlow Lite models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/internal/reference/reference_ops.h#L2625-L2631 Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `output_data` buffer. This might result in a segmentation fault but it can also be used to further corrupt the memory and can be chained with other vulnerabilities to create more advanced exploits. ### Patches We have patched the issue in 204945b and will release patch releases for all affected versions. We recommend users to upgrade to TensorFlow 2.2.1, or 2.3.1. ### Workarounds A potential workaround would be to add a custom `Verifier` to the model loading code to ensure that the segment ids are all positive, although this only handles the case when the segment ids are stored statically in the model. A similar validation could be done if the segment ids are generated at runtime between inference steps. If the segment ids are generated as outputs of a tensor during inference steps, then there are no possible workaround and users are advised to upgrade to patched code. ### 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 discovered from a variant analysis of [GHSA-p2cq-cprg-frvm](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p2cq-cprg-frvm).

Credit: security-advisories@github.com security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
pip/tensorflow-gpu=2.3.0
2.3.1
pip/tensorflow-gpu=2.2.0
2.2.1
pip/tensorflow-cpu=2.3.0
2.3.1
pip/tensorflow-cpu=2.2.0
2.2.1
pip/tensorflow=2.3.0
2.3.1
pip/tensorflow=2.2.0
2.2.1
Google TensorFlow>=2.2.0<2.2.1
Google TensorFlow>=2.3.0<2.3.1
TensorFlow Keras>=2.2.0<2.2.1
TensorFlow Keras>=2.3.0<2.3.1

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.

Frequently Asked Questions

  • What is the severity of CVE-2020-15212?

    CVE-2020-15212 is classified as a high severity vulnerability due to the potential for heap buffer overflows.

  • How do I fix CVE-2020-15212?

    To fix CVE-2020-15212, upgrade TensorFlow to version 2.3.1 or later.

  • Which versions of TensorFlow are affected by CVE-2020-15212?

    CVE-2020-15212 affects TensorFlow versions 2.2.0 to 2.2.1 and 2.3.0.

  • What impact does CVE-2020-15212 have on TensorFlow Lite models?

    CVE-2020-15212 can trigger writes outside of bounds in TensorFlow Lite models when using segment sum with negative segment IDs.

  • Is CVE-2020-15212 a local or remote execution vulnerability?

    CVE-2020-15212 is primarily a local execution vulnerability affecting applications using TensorFlow Lite.

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