CWE
125 119 122
Advisory Published
CVE Published
Updated

CVE-2020-15196: Heap buffer overflow in Tensorflow

First published: Fri Sep 25 2020(Updated: )

### Impact The `SparseCountSparseOutput` and `RaggedCountSparseOutput` implementations don't validate that the `weights` tensor has the same shape as the data. The check exists for `DenseCountSparseOutput`, where both tensors are fully specified: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L110-L117 In the sparse and ragged count weights are still accessed in parallel with the data: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/core/kernels/count_ops.cc#L199-L201 But, since there is no validation, a user passing fewer weights than the values for the tensors can generate a read from outside the bounds of the heap buffer allocated for the weights. ### Patches We have patched the issue in 3cbb917b4714766030b28eba9fb41bb97ce9ee02 and will release a patch release. We recommend users to upgrade to TensorFlow 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 is a variant of [GHSA-p5f8-gfw5-33w4](https://github.com/tensorflow/tensorflow/security/advisories/GHSA-p5f8-gfw5-33w4)

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

Affected SoftwareAffected VersionHow to fix
Google TensorFlow=2.3.0
pip/tensorflow-gpu=2.3.0
2.3.1
pip/tensorflow-cpu=2.3.0
2.3.1
pip/tensorflow=2.3.0
2.3.1
=2.3.0

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-15196?

    CVE-2020-15196 is classified as a medium severity vulnerability due to improper validation of tensor shapes in TensorFlow.

  • How do I fix CVE-2020-15196?

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

  • What are the affected software versions for CVE-2020-15196?

    CVE-2020-15196 affects TensorFlow version 2.3.0 across various distributions including tensorflow-gpu and tensorflow-cpu packages.

  • What components of TensorFlow are impacted by CVE-2020-15196?

    CVE-2020-15196 impacts the SparseCountSparseOutput and RaggedCountSparseOutput implementations of TensorFlow.

  • Is CVE-2020-15196 a common vulnerability?

    CVE-2020-15196 is a known vulnerability within TensorFlow, but its prevalence will depend on the use of affected versions in projects.

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