CVE-2021-41227: Arbitrary memory read in `ImmutableConst`

Published Nov 5, 2021
·
Updated

Impact The ImmutableConst operation in TensorFlow can be tricked into reading arbitrary memory contents:

python import tensorflow as tf with open('/tmp/test','wb') as f: f.write(b'\xe2'128) data = tf.rawops.ImmutableConst(dtype=tf.string,shape=3,memoryregionname='/tmp/test') print(data) This is because the tstring TensorFlow string class has a special case for memory mapped strings but the operation itself does not offer any support for this datatype.

Patches We have patched the issue in GitHub commit 3712a2d3455e6ccb924daa5724a3652a86f6b585 and GitHub commit 1cb6bb6c2a6019417c9adaf9e6843ba75ee2580b. 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 members of the Aivul Team from Qihoo 360.

Other sources

TensorFlow is an open source platform for machine learning. In affected versions the ImmutableConst operation in TensorFlow can be tricked into reading arbitrary memory contents. This is because the tstring TensorFlow string class has a special case for memory mapped strings but the operation itself does not offer any support for this datatype. 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.

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
Nov 10, 2021
Advisory Published
via GitHub·06:34 PM

Frequently Asked Questions

1

What is the severity of CVE-2021-41227?

CVE-2021-41227 has been classified as a high severity vulnerability due to its ability to potentially read arbitrary memory contents.

2

How do I fix CVE-2021-41227?

You can mitigate CVE-2021-41227 by upgrading TensorFlow to version 2.4.4 or later, specifically to versions 2.5.2 or 2.6.1.

3

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

CVE-2021-41227 affects TensorFlow versions from 2.4.0 up to but not including 2.4.4, as well as 2.6.0 to 2.6.1.

4

How does CVE-2021-41227 impact TensorFlow users?

CVE-2021-41227 may allow an attacker to access sensitive information from memory, posing a risk to data security.

5

Is CVE-2021-41227 being actively exploited in the wild?

As of now, there are no confirmed reports of active exploitation of CVE-2021-41227.

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