CVE-2020-151915.3MediumCWE-476

CVE-2020-15191: Undefined behavior in Tensorflow

tensorflow

Vendor fix available · Affected: tensorflow · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.9%probability of exploitation in the next 30 days

60th percentile

050100

Higher than 60% of scored CVEs

5.3MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

tensorflow · tensorflow= 2.2.0; = 2.3.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: NULL Pointer Dereference · Memory Corruption
Vendor: tensorflow
Published: September 2020
Band: Unlikely (under 1%), September 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-15191 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.