CVE-2021-37682: Use of unitialized value in TensorFlow Lite

Published Aug 12, 2021
·
Updated

Impact All TFLite operations that use quantization can be made to use unitialized values. For example:

cc const auto affinequantization = reinterpretcast<TfLiteAffineQuantization>( filter->quantization.params);

The issue stems from the fact that quantization.params is only valid if quantization.type is different that kTfLiteNoQuantization. However, these checks are missing in large parts of the code.

Patches We have patched the issue in GitHub commits 537bc7c723439b9194a358f64d871dd326c18887, 4a91f2069f7145aab6ba2d8cfe41be8a110c18a5 and 8933b8a21280696ab119b63263babdb54c298538.

The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

For more information Please consult our security guide 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.

Other sources

TensorFlow is an end-to-end open source platform for machine learning. In affected versions all TFLite operations that use quantization can be made to use unitialized values. For example. The issue stems from the fact that quantization.params is only valid if quantization.type is different that kTfLiteNoQuantization. However, these checks are missing in large parts of the code. We have patched the issue in GitHub commits 537bc7c723439b9194a358f64d871dd326c18887, 4a91f2069f7145aab6ba2d8cfe41be8a110c18a5 and 8933b8a21280696ab119b63263babdb54c298538. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

MITRE

Affected Software

15 affected componentsFixes available
pip/tensorflow-gpu=2.5.0
2.5.1
pip/tensorflow-gpu>=2.4.0<2.4.3
2.4.3
pip/tensorflow-gpu<2.3.4
2.3.4
pip/tensorflow-cpu=2.5.0
2.5.1
pip/tensorflow-cpu>=2.4.0<2.4.3
2.4.3
pip/tensorflow-cpu<2.3.4
2.3.4
pip/tensorflow=2.5.0
2.5.1
pip/tensorflow>=2.4.0<2.4.3
2.4.3
pip/tensorflow<2.3.4
2.3.4
Google TensorFlow>=2.3.0<2.3.4
Google TensorFlow>=2.4.0<2.4.3
Google TensorFlow=2.5.0
Google TensorFlow=2.6.0-rc0
Google TensorFlow=2.6.0-rc1
Google TensorFlow=2.6.0-rc2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade pip/tensorflow-gpu to a version that resolves this vulnerability.

    Fixed in 2.5.1
  2. Upgrade

    Upgrade pip/tensorflow-gpu to a version that resolves this vulnerability.

    Fixed in 2.4.3
  3. Upgrade

    Upgrade pip/tensorflow-gpu to a version that resolves this vulnerability.

    Fixed in 2.3.4
  4. Upgrade

    Upgrade pip/tensorflow-cpu to a version that resolves this vulnerability.

    Fixed in 2.5.1
  5. Upgrade

    Upgrade pip/tensorflow-cpu to a version that resolves this vulnerability.

    Fixed in 2.4.3
  6. Upgrade

    Upgrade pip/tensorflow-cpu to a version that resolves this vulnerability.

    Fixed in 2.3.4
  7. Upgrade

    Upgrade pip/tensorflow to a version that resolves this vulnerability.

    Fixed in 2.5.1
  8. Upgrade

    Upgrade pip/tensorflow to a version that resolves this vulnerability.

    Fixed in 2.4.3
  9. Upgrade

    Upgrade pip/tensorflow to a version that resolves this vulnerability.

    Fixed in 2.3.4
  10. Upgrade

    Upgrade TensorFlow to a version that resolves this vulnerability.

    Fixed in 2.6.0
  11. Upgrade

    Upgrade TensorFlow to a version that resolves this vulnerability.

    Patch 537bc7c723439b9194a358f64d871dd326c18887
  12. Upgrade

    Upgrade TensorFlow to a version that resolves this vulnerability.

    Patch 4a91f2069f7145aab6ba2d8cfe41be8a110c18a5
  13. Upgrade

    Upgrade TensorFlow to a version that resolves this vulnerability.

    Patch 8933b8a21280696ab119b63263babdb54c298538
  14. Upgrade

    Upgrade TensorFlow 2.5.1 to a version that resolves this vulnerability.

    Patch 537bc7c723439b9194a358f64d871dd326c18887
  15. Upgrade

    Upgrade TensorFlow 2.4.3 to a version that resolves this vulnerability.

    Patch 537bc7c723439b9194a358f64d871dd326c18887
  16. Upgrade

    Upgrade TensorFlow 2.3.4 to a version that resolves this vulnerability.

    Patch 537bc7c723439b9194a358f64d871dd326c18887

Event History

Aug 12, 2021
CVE Published
via MITRE·10:45 PM
Data Sourced
via MITRE·10:45 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Aug 25, 2021
Advisory Published
via GitHub·02:40 PM

Frequently Asked Questions

1

What is the severity of CVE-2021-37682?

CVE-2021-37682 is classified as a high severity vulnerability due to its potential to expose uninitialized values in TFLite operations using quantization.

2

How do I fix CVE-2021-37682?

To fix CVE-2021-37682, upgrade TensorFlow to version 2.5.1, 2.4.3, or 2.3.4 depending on the version you are currently using.

3

Which versions of TensorFlow are affected by CVE-2021-37682?

CVE-2021-37682 affects TensorFlow versions 2.3.0 to 2.3.4, 2.4.0 to 2.4.3, 2.5.0, and various release candidates of 2.6.0.

4

What kind of applications are impacted by CVE-2021-37682?

Applications using TensorFlow for machine learning operations that implement quantization techniques may be impacted by CVE-2021-37682.

5

Is there a workaround for CVE-2021-37682 if I cannot update TensorFlow immediately?

Currently, no official workarounds are provided for CVE-2021-37682, and it is recommended to upgrade to a patched version as soon as possible.

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