medium
5.3
CWE
252 20 476
Advisory Published
CVE Published
Updated

CVE-2020-15191: Undefined behavior in Tensorflow

First published: Fri Sep 25 2020(Updated: )

### Impact If a user passes an invalid argument to `dlpack.to_dlpack` the expected validations will cause variables to bind to `nullptr` while setting a `status` variable to the error condition. However, this `status` argument is not properly checked: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L265-L267 Hence, code following these methods will bind references to null pointers: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/c/eager/dlpack.cc#L279-L285 This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. ### Patches We have patched the issue in 22e07fb204386768e5bcbea563641ea11f96ceb8 and will release a patch release for all affected versions. We recommend users to upgrade to TensorFlow 2.2.1 or 2.3.1. ### 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 during variant analysis of [GHSA-rjjg-hgv6-h69v](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-rjjg-hgv6-h69v).

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
TensorFlow Keras=2.2.0
TensorFlow Keras=2.3.0
SUSE Linux=15.2

Remedy

https://github.com/tensorflow/tensorflow/commit/22e07fb204386768e5bcbea563641ea11f96ceb8

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.

Read MoreStart Free Trial

Reference Links

Frequently Asked Questions

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

    CVE-2020-15191 is classified as a medium severity vulnerability.

  • How do I fix CVE-2020-15191?

    To fix CVE-2020-15191, upgrade to TensorFlow versions 2.3.1 or 2.2.1, depending on your package.

  • What are the affected versions in CVE-2020-15191?

    The affected versions in CVE-2020-15191 include TensorFlow 2.2.0 and 2.3.0.

  • What software is affected by CVE-2020-15191?

    CVE-2020-15191 affects TensorFlow, specifically the tensorflow-gpu and tensorflow-cpu packages.

  • What happens if I don't address CVE-2020-15191?

    If CVE-2020-15191 is not addressed, it may lead to potential application instability due to improper error handling.

Company

Resources

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