CVE-2020-15207

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data tampering, service disruption.

Exploit odds

1.2% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2020-09-25 19:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 02:56 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.2% in the next 30 days (EPSS).
• Severity: 8.7 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2020-09-25 19:15 UTC

Last modified

2026-06-17 02:56 UTC

Exploit probability

1.2% · EPSS, next 30 days

Weakness

CWE-119 · Buffer errors

Record status

Modified

Affected

• Google Tensorflow < 1.15.4
• Google Tensorflow < 2.0.3
• Google Tensorflow < 2.1.2
• Google Tensorflow < 2.2.1
• Google Tensorflow < 2.3.1
• Opensuse Leap 15.2

Attack profile CVSS 3.1 · 8.7

Attack vector

Network

Complexity

High

Privileges needed

None

User interaction

None

Scope

Changed

Confidentiality

None

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2020-15207.md and follow it. Check whether this project is affected by CVE-2020-15207. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge