CVE-2020-15207

Segfault and data corruption in tensorflow-lite

CRITICAL

CVSS Score

Published: September 25, 2020 at 06:45 PM UTC

Updated: June 17, 2026 at 02:56 AM UTC

3 products affected across 3 vendorsLeapTensorflowTensorFlow

Using tensorflow by tensorflow?

Get instant alerts when new vulnerabilities affect tensorflow - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

CRITICAL9

Exploit prediction

EPSS 1%

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Tensorflow · Google

95%

v < 1.15.42.0.0 ≤ v < 2.0.32.1.0 ≤ v < 2.1.22.2.0 ≤ v < 2.2.12.3.0 ≤ v < 2.3.1

Affected range stops below 1.15.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.0.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.1.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.2.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.3.1, so it looks safe — our inference, not a vendor statement

Leap · openSUSEdrupal

95%

15.2

TensorFlow · Tensorflow

60%

v < 1.15.4v < 2.0.3v < 2.1.2v < 2.2.1v < 2.3.1

Affected range stops below 1.15.4, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.0.3, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.1.2, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.2.1, so it looks safe — our inference, not a vendor statement

Affected range stops below 2.3.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references

References (4)

Vendor Advisoryx_refsource_SUSEMailing ListThird Party Advisory

Source: [email protected]

http://lists.opensuse.org/opensuse-security-announce/2020-10/msg00065.html

x_refsource_MISCPatchThird Party Advisory

Source: [email protected]

https://github.com/tensorflow/tensorflow/commit/2d88f470dea2671b430884260f3626b1fe99830a

x_refsource_MISCThird Party Advisory

Source: [email protected]

https://github.com/tensorflow/tensorflow/releases/tag/v2.3.1

x_refsource_CONFIRMExploitThird Party Advisory

Source: [email protected]

https://github.com/tensorflow/tensorflow/security/advisories/GHSA-q4qf-3fc6-8x34

CVSS

9CRITICAL[email protected]

Attack Vector: NETWORK
Complexity: HIGH
Privileges: NONE
User Interaction: NONE
Scope: CHANGED
Confidentiality: HIGH
Integrity: HIGH
Availability: HIGH

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-119CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Create account Sign in

Free plan, no card