CVE-2021-37656: TensorFlow - Reference Binding to Null Pointer in tf.raw_ops.RaggedTensorToSparse
Summary
CVE-2021-37656: Reference binding to nullptr in RaggedTensorToSparse in TensorFlow. Affects tensorflow across 3 version ranges.
>= 2.3.0, < 2.3.4
>= 2.4.0, < 2.4.3
>= 2.5.0, < 2.5.1
Fixed in 2.3.4, 2.4.3 or 2.5.1, depending on the release line you run. How to fix ↓
Also tracked for
- tensorflow · PyPI
- tensorflow · PyPI
- tensorflow-cpu · PyPI
- tensorflow-gpu · PyPI
The same CVE-2021-37656 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
TensorFlow is an end-to-end open source platform for machine learning. It provides a comprehensive ecosystem for building and deploying machine learning models. TensorFlow is widely used in various industries and research domains due to its flexibility and scalability. However, a vulnerability has been discovered in TensorFlow that allows an attacker to cause undefined behavior by binding a reference to a null pointer in the tf.raw_ops.RaggedTensorToSparse function.
Vulnerability Detail
The vulnerability arises from incomplete validation of the splits values in the implementation of tf.raw_ops.RaggedTensorToSparse. The implementation does not check that the splits values are in increasing order, which can lead to undefined behavior. An attacker can exploit this vulnerability to cause a denial of service (DoS) or potentially execute arbitrary code. The issue has been patched in the latest versions of TensorFlow (2.6.0) and will also be backported to earlier supported versions (2.5.1, 2.4.3, and 2.3.4).
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
>= 2.3.0, < 2.3.42.3.4 -
>= 2.4.0, < 2.4.32.4.3 -
>= 2.5.0, < 2.5.12.5.1
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
There is no known workaround for this vulnerability. It is strongly advised to apply the recommended fix by updating to the latest patched version of TensorFlow.
Conclusion
The vulnerability in TensorFlow (CVE-2021-37656) allows an attacker to cause undefined behavior by binding a reference to a null pointer. It is crucial to update to the latest patched version of TensorFlow or apply the appropriate patch to mitigate the risk. For further assistance or support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for tensorflow →
FAQ
TensorFlow is an open source platform for machine learning that provides a comprehensive ecosystem for building and deploying machine learning models.
This vulnerability allows an attacker to cause undefined behavior in TensorFlow, potentially leading to a denial of service (DoS) or arbitrary code execution.
The vulnerability affects TensorFlow versions 2.3.0 to 2.3.4, 2.4.0 to 2.4.3, 2.5.0, and 2.6.0-rc0 to 2.6.0-rc2.
To fix this vulnerability, update TensorFlow to the latest patched version (2.6.0) or apply the appropriate patch for earlier supported versions (2.5.1, 2.4.3, or 2.3.4).
There is no known workaround for this vulnerability. It is recommended to apply the recommended fix by updating to the latest patched version of TensorFlow.
References
Related vulnerabilities
Recent vulnerabilities recorded for tensorflow.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
