Skip to content
Connect AISign inSign up free
CVE-2020-152655.9MediumCWE-125

CVE-2020-15265: Segfault in Tensorflow

tensorflow

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.9MediumCVSS 3.1
LowMedium

DescriptionCVE.org

In Tensorflow before version 2.4.0, an attacker can pass an invalid `axis` value to `tf.quantization.quantize_and_dequantize`. This results in accessing a dimension outside the rank of the input tensor in the C++ kernel implementation. However, dim_size only does a DCHECK to validate the argument and then uses it to access the corresponding element of an array. Since in normal builds, `DCHECK`-like macros are no-ops, this results in segfault and access out of bounds of the array. The issue is patched in eccb7ec454e6617738554a255d77f08e60ee0808 and TensorFlow 2.4.0 will be released containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.

Affected products1

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

  • tensorflow · tensorflow< 2.4.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
Published
October 2020

CoverageNo articles yet

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

References