CVE-2020-15209

Null pointer dereference in tensorflow-lite

MEDIUM
5.9
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
Severity
MEDIUM5.9
Exploit prediction
EPSS 0.8%

Description

In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one. The runtime assumes that these buffers are written to before a possible read, hence they are initialized with `nullptr`. However, by changing the buffer index for a tensor and implicitly converting that tensor to be a read-write one, as there is nothing in the model that writes to it, we get a null pointer dereference. The issue is patched in commit 0b5662bc, 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.

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
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:

CVSS

5.9MEDIUMGitHub_M
Attack Vector
NETWORK
Complexity
HIGH
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476

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.

Free plan, no card