CVE-2020-15191: TensorFlow - Invalid Argument in dlpack.to_dlpack() Function
Summary
CVE-2020-15191: Undefined behavior in Tensorflow. Affects tensorflow across 2 version ranges.
>= 2.2.0, < 2.2.1
>= 2.3.0, < 2.3.1
Fixed in 2.2.1 or 2.3.1, depending on the release line you run. How to fix ↓
Also tracked for
- tensorflow · PyPI
- tensorflow-cpu · PyPI
- tensorflow-gpu · PyPI
- tensorflow · PyPI
The same CVE-2020-15191 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 open-source machine learning framework developed by Google. It provides a comprehensive ecosystem of tools, libraries, and resources for building and deploying machine learning models. TensorFlow is widely used in various domains, including research, industry, and academia. However, versions 2.2.0 and 2.3.0 of TensorFlow are vulnerable to a specific issue.
Vulnerability Detail
The vulnerability (CVE-2020-15191) in TensorFlow versions 2.2.0 and 2.3.0 arises when an invalid argument is passed to the dlpack.to_dlpack function. This leads to variables binding to nullptr while setting a status variable to the error condition. Unfortunately, the status argument is not properly checked, resulting in references being bound to null pointers. This behavior is undefined and can cause errors during compilation with -fsanitize=null. The issue has been addressed in commit 22e07fb204386768e5bcbea563641ea11f96ceb8 and fixed in TensorFlow versions 2.2.1 and 2.3.1.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
>= 2.2.0, < 2.2.12.2.1 -
>= 2.3.0, < 2.3.12.3.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 specific workaround mentioned for this vulnerability.
Conclusion
In conclusion, the vulnerability (CVE-2020-15191) in TensorFlow versions 2.2.0 and 2.3.0 can lead to undefined behavior and errors during compilation. It is crucial to update TensorFlow to versions 2.2.1 or 2.3.1 to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for tensorflow →
FAQ
TensorFlow is an open-source machine learning framework developed by Google. It provides a comprehensive ecosystem of tools, libraries, and resources for building and deploying machine learning models.
Versions 2.2.0 and 2.3.0 of TensorFlow are affected by this vulnerability.
This vulnerability can lead to undefined behavior and errors during compilation with -fsanitize=null.
Yes, the vulnerability has been fixed in TensorFlow versions 2.2.1 and 2.3.1.
Users can update their TensorFlow installation by following the official upgrade instructions provided by the TensorFlow team.
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.
