CVE-2020-15209: Google Tensorflow

Medium severity, CVSS 5.9. EPSS: 0.8% chance of exploitation in the next 30 days.

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 products

• Google Tensorflow: before 1.15.4 (fixed in 1.15.4); from 2.0.0, before 2.0.3 (fixed in 2.0.3); from 2.1.0, before 2.1.2 (fixed in 2.1.2); from 2.2.0, before 2.2.1 (fixed in 2.2.1); from 2.3.0, before 2.3.1 (fixed in 2.3.1)
• Opensuse Leap: version 15.2 only

Published 2020-09-25. Last modified 2026-06-17.