CVE-2021-41225: A use of uninitialized value vulnerability in Tensorflow

Published Nov 5, 2021
·
Updated

Impact TensorFlow's Grappler optimizer has a use of unitialized variable:

cc const NodeDef dequeuenode; for (const auto& trainnode : trainnodes) { if (IsDequeueOp(trainnode)) { dequeuenode = trainnode; break; } }

if (dequeuenode) { ... }

If the trainnodes vector (obtained from the saved model that gets optimized) does not contain a Dequeue node, then dequeuenode is left unitialized.

Patches We have patched the issue in GitHub commit 68867bf01239d9e1048f98cbad185bf4761bedd3.

The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.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 Qian Feng from Baidu Security Team.

Other sources

TensorFlow is an open source platform for machine learning. In affected versions TensorFlow's Grappler optimizer has a use of unitialized variable. If the trainnodes vector (obtained from the saved model that gets optimized) does not contain a Dequeue node, then dequeuenode is left unitialized. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, TensorFlow 2.5.2, and TensorFlow 2.4.4, as these are also affected and still in supported range.

MITRE

Affected Software

13 affected componentsFixes available
pip/tensorflow-gpu<2.4.4
2.4.4
pip/tensorflow-gpu>=2.5.0<2.5.2
2.5.2
pip/tensorflow-gpu>=2.6.0<2.6.1
2.6.1
pip/tensorflow-cpu<2.4.4
2.4.4
pip/tensorflow-cpu>=2.5.0<2.5.2
2.5.2
pip/tensorflow-cpu>=2.6.0<2.6.1
2.6.1
pip/tensorflow<2.4.4
2.4.4
pip/tensorflow>=2.5.0<2.5.2
2.5.2
pip/tensorflow>=2.6.0<2.6.1
2.6.1
Google TensorFlow>=2.4.0<2.4.4
Google TensorFlow>=2.6.0<2.6.1
Google TensorFlow=2.7.0-rc0
Google TensorFlow=2.7.0-rc1

Event History

Nov 5, 2021
CVE Published
via MITRE·10:30 PM
Data Sourced
via MITRE·10:30 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Nov 10, 2021
Advisory Published
via GitHub·06:44 PM

Frequently Asked Questions

1

What does CVE-2021-41225 refer to?

CVE-2021-41225 refers to a use of uninitialized variable vulnerability in TensorFlow's Grappler optimizer.

2

What versions of TensorFlow are affected by CVE-2021-41225?

CVE-2021-41225 affects TensorFlow versions between 2.4.0 and 2.4.4, versions between 2.6.0 and 2.6.1, as well as specific release candidates 2.7.0-rc0 and 2.7.0-rc1.

3

How can I fix the vulnerability identified by CVE-2021-41225?

To fix CVE-2021-41225, upgrade TensorFlow to versions 2.4.4, 2.5.2, or 2.6.1.

4

What is the potential impact of CVE-2021-41225?

The impact of CVE-2021-41225 could lead to unpredictable behavior or crashes in applications relying on the affected versions of TensorFlow.

5

Is there a known exploitation for CVE-2021-41225?

As of now, there are no publicly known exploits targeting CVE-2021-41225, but it is advisable to patch affected versions to mitigate risk.

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