CVE-2020-15191
5.3 · MEDIUMOverview
CVE-2020-15191 is a medium-severity vulnerability affecting google tensorflow. It was published on September 25, 2020 and has a CVSS 3.1 base score of 5.3 (MEDIUM).
This vulnerability has a CVSS 3.1 base score of 5.3, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
Technical Description
In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes an invalid argument to `dlpack.to_dlpack` the expected validations will cause variables to bind to `nullptr` while setting a `status` variable to the error condition. However, this `status` argument is not properly checked. Hence, code following these methods will bind references to null pointers. This is undefined behavior and reported as an error if compiling with `-fsanitize=null`. The issue is patched in commit 22e07fb204386768e5bcbea563641ea11f96ceb8 and is released in TensorFlow versions 2.2.1, or 2.3.1.
Remediation
Check the references section for vendor advisories and patches from google. Update tensorflow to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|
References
Frequently Asked Questions
What is CVE-2020-15191?
CVE-2020-15191 is a medium-severity vulnerability affecting google tensorflow. It was published on September 25, 2020 and has a CVSS 3.1 base score of 5.3 (MEDIUM).
How severe is CVE-2020-15191?
This vulnerability has a CVSS 3.1 base score of 5.3, rated MEDIUM. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
How do I fix or remediate CVE-2020-15191?
Check the references section for vendor advisories and patches from google. Update tensorflow to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2020-15191?
CyberStrike's AI-powered security agents can automatically detect CVE-2020-15191 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related MEDIUM CVEs from 2020
View all →In postfix-mta-sts-resolver before 0.5.1, All users can receive incorrect response from daemon under
Potential security vulnerabilities have been identified in HPE OpenCall Media Platform (OCMP) result
In jQuery versions greater than or equal to 1.0.3 and before 3.5.0, passing HTML containing <option>
In jQuery starting with 1.12.0 and before 3.5.0, passing HTML from untrusted sources - even after sa
In Wiki.js before 2.3.81, there is a stored XSS in the Markdown editor. An editor with write access
The shell subsystem contains a buffer overflow, whereby an adversary with physical access to the dev
In FreeRDP less than or equal to 2.0.0, an Integer Overflow to Buffer Overflow exists. When using /v
In Saleor Storefront before version 2.10.3, request data used to authenticate customers was inadvert
Privilege Escalation vulnerability in the installer in McAfee McAfee Total Protection (MTP) trial pr
Authentication Protection Bypass vulnerability in McAfee Endpoint Security (ENS) for Windows prior t
Dell Inspiron 15 7579 2-in-1 BIOS versions prior to 1.31.0 contain an Improper SMM communication buf
Azure Sphere Elevation of Privilege Vulnerability