medium
6.5
CWE
476
Advisory Published
Advisory Published
Updated

CVE-2022-23577: Null-dereference in Tensorflow

First published: Fri Feb 04 2022(Updated: )

### Impact The [implementation of `GetInitOp`](https://github.com/tensorflow/tensorflow/blob/a1320ec1eac186da1d03f033109191f715b2b130/tensorflow/cc/saved_model/loader_util.cc#L31-L61) is vulnerable to a crash caused by dereferencing a null pointer: ```cc const auto& init_op_sig_it = meta_graph_def.signature_def().find(kSavedModelInitOpSignatureKey); if (init_op_sig_it != sig_def_map.end()) { *init_op_name = init_op_sig_it->second.outputs() .find(kSavedModelInitOpSignatureKey) ->second.name(); return Status::OK(); } ``` Here, we have a nested map and we assume that if the first `.find` succeeds then so would be the search in the internal map. However, the maps are built based on the `SavedModel` protobuf format and a malicious user can alter that on disk before loading to cause the second `.find` to return `nullptr`. ### Patches We have patched the issue in GitHub commit [4f38b1ac8e42727e18a2f0bde06d3bee8e77b250](https://github.com/tensorflow/tensorflow/commit/4f38b1ac8e42727e18a2f0bde06d3bee8e77b250). The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range. ### 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
pip/tensorflow-gpu=2.7.0
2.7.1
pip/tensorflow-gpu>=2.6.0<2.6.3
2.6.3
pip/tensorflow-gpu<2.5.3
2.5.3
pip/tensorflow-cpu=2.7.0
2.7.1
pip/tensorflow-cpu>=2.6.0<2.6.3
2.6.3
pip/tensorflow-cpu<2.5.3
2.5.3
pip/tensorflow=2.7.0
2.7.1
pip/tensorflow>=2.6.0<2.6.3
2.6.3
pip/tensorflow<2.5.3
2.5.3
TensorFlow Keras<=2.5.2
TensorFlow Keras>=2.6.0<=2.6.2
TensorFlow Keras=2.7.0

Remedy

https://github.com/tensorflow/tensorflow/commit/4f38b1ac8e42727e18a2f0bde06d3bee8e77b250

Remedy

https://github.com/tensorflow/tensorflow/security/advisories/GHSA-8cxv-76p7-jxwr

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-2022-23577?

    CVE-2022-23577 has a severity rating that indicates it can cause application crashes due to null pointer dereferences.

  • How do I fix CVE-2022-23577?

    To fix CVE-2022-23577, upgrade TensorFlow to version 2.5.3, 2.6.3, or 2.7.1 depending on your current version.

  • Which versions of TensorFlow are affected by CVE-2022-23577?

    CVE-2022-23577 affects TensorFlow versions up to 2.5.2 and from 2.6.0 to 2.6.2, as well as the exact version 2.7.0.

  • What causes the vulnerability described in CVE-2022-23577?

    CVE-2022-23577 is caused by the implementation of the GetInitOp function, which can dereference a null pointer.

  • Is CVE-2022-23577 a high-risk vulnerability?

    Yes, CVE-2022-23577 is considered high-risk as it can lead to application crashes and potential disruptions.

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