CVE-2020-151924.3MediumCWE-20

CVE-2020-15192: Memory leak 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.8%probability of exploitation in the next 30 days

58th percentile

050100

Higher than 58% of scored CVEs

4.3MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

In Tensorflow before versions 2.2.1 and 2.3.1, if a user passes a list of strings to `dlpack.to_dlpack` there is a memory leak following an expected validation failure. The issue occurs because the `status` argument during validation failures is not properly checked. Since each of the above methods can return an error status, the `status` value must be checked before continuing. 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: Improper Input Validation · Input Validation and Logic
Vendor: tensorflow
Published: September 2020
Band: Unlikely (under 1%), September 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2020-15192 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.