NULL Pointer Dereference Affecting tensorflow/tensorflow package, versions [,1.15.4)[2.0.0,2.0.3)[2.1.0,2.1.2)[2.2.0,2.2.1)[2.3.0,2.3.1)


Severity

Recommended
0.0
medium
0
10

CVSS assessment made by Snyk's Security Team. Learn more

Threat Intelligence

Exploit Maturity
Proof of Concept
EPSS
0.16% (54th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about NULL Pointer Dereference vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-UNMANAGED-TENSORFLOWTENSORFLOW-2333479
  • published12 Jan 2022
  • disclosed25 Sept 2020
  • creditUnknown

Introduced: 25 Sep 2020

CVE-2020-15209  (opens in a new tab)
CWE-476  (opens in a new tab)

How to fix?

Upgrade tensorflow/tensorflow to version 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1 or higher.

Overview

Affected versions of this package are vulnerable to NULL Pointer Dereference. 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.

CVSS Scores

version 3.1