Buffer overflow in Google Tensorflow

CVE-2020-15207

In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, to mimic Python's indexing with negative values, TFLite uses `ResolveAxis` to convert negative values to positive indices. However, the only check that the converted index is now valid is only present in debug builds. If the `DCHECK` does not trigger, then code execution moves ahead with a negative index. This, in turn, results in accessing data out of bounds which results in segfaults and/or data corruption. The issue is patched in commit 2d88f470dea2671b430884260f3626b1fe99830a, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.

Vulnerability class: Buffer Overflow

Published · last modified .

CVSS v3 metric

CVSS v3 base score 8.7 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H.

EPSS exploit prediction

EPSS: 0.012 (68.0th percentile), scored .

Low probability of exploitation in the next 30 days, but still tracked. 68th percentile — 68.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2020-15207: held from 0.012 to 0.012.

EPSS over last 30 days · oldest: 0.012 · newest: 0.012 · change: 0.000

Affected products

Weakness classification (CWE)

References

Frequently asked questions

What is CVE-2020-15207?
CVE-2020-15207 is a high-severity vulnerability in Google Tensorflow, classified under Improper Restriction of Operations within the Bounds of a Memory Buffer. CVSS score: 8.7/10. Published 2020-09-25.
How severe is CVE-2020-15207?
High severity. CVSS v3 base score is 8.7 out of 10.