Skip to content
Fencer Intel
medium 5.9

CVE-2020-15265 json

Segfault in Tensorflow

published 6y ago modified 2mo ago also BIT-tensorflow-2020-15265 , EUVD-2020-0211 , GHSA-rrfp-j2mp-hq9c , PYSEC-2020-138 , PYSEC-2020-295 , PYSEC-2020-330

cvss
5.9
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits
0
none known

Summary

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.

Patch / fix

  • pypi tensorflow 2.4.0
  • pypi tensorflow-cpu 2.4.0
  • pypi tensorflow-gpu 2.4.0
  • bitnami tensorflow 2.4.0
  • google tensorflow 2.4.0
  • tensorflow Arch Linux 2.4.0rc4-1

arch linux advisories AVG-1350

Is CVE-2020-15265 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.91% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/tensorflow/tensorflow/security/advisories/GHSA-rrfp-j2mp-hq9c referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 5.9 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:N/A:P
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
pypi tensorflow
<2.4.0
2.4.0
pypi tensorflow-cpu
<2.4.0
2.4.0
pypi tensorflow-gpu
<2.4.0
2.4.0
bitnami tensorflow
<2.4.0
2.4.0

Affected products

  • tensorflow tensorflow

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.