CVEvulnerability

CVE-2020-15207

9.0 CRITICAL Published 2020-09-25 Modified 2026-06-17 Official page ↗
Status
Modified
Published
2020-09-25
Last modified
2026-06-17
Assigner
[email protected]
CVSS 3.1 ([email protected])
8.7 HIGH — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:H
CVSS 3.1 ([email protected])
9.0 CRITICAL — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
CVSS 2.0 ([email protected])
6.8 MEDIUM — AV:N/AC:M/Au:N/C:P/I:P/A:P
Weaknesses
CWE-119, CWE-787

Description

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.

Affected configurations

• google tensorflow (< 1.15.4) • google tensorflow (>= 2.0.0 < 2.0.3) • google tensorflow (>= 2.1.0 < 2.1.2) • google tensorflow (>= 2.2.0 < 2.2.1) • google tensorflow (>= 2.3.0 < 2.3.1) • opensuse leap 15.2

Related

Weakness · CWE (2)

  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer weakness
  • CWE-787 Out-of-bounds Write weakness

References