Advisory

GHSA-qh32-6jjc-qprm

Also known as: BIT-tensorflow-2020-15209, CVE-2020-15209, PYSEC-2020-132, PYSEC-2020-289, PYSEC-2020-324

Summary

Null pointer dereference in tensorflow-lite

Details

Impact
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:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/core/subgraph.cc#L1224-L1227

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.

Patches
We have patched the issue in 0b5662bc and will release patch releases for all versions between 1.15 and 2.3.

We recommend users to upgrade to TensorFlow 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.

For more information
Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution
This vulnerability has been reported by members of the Aivul Team from Qihoo 360 but was also discovered through variant analysis of GHSA-cvpc-8phh-8f45.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2020-09-25 18:28 UTC
Modified
2026-07-08 06:28 UTC

Affected packages and fixes

15 affected packages; all PyPI · All systems
PackageAffectedFix
tensorflowEarlier versionspip install --upgrade tensorflow==1.15.4
tensorflowintroduced 2.0.0, fixed 2.0.3pip install --upgrade tensorflow==2.0.3
tensorflowintroduced 2.1.0, fixed 2.1.2pip install --upgrade tensorflow==2.1.2
tensorflowintroduced 2.2.0, fixed 2.2.1pip install --upgrade tensorflow==2.2.1
tensorflowintroduced 2.3.0, fixed 2.3.1pip install --upgrade tensorflow==2.3.1
tensorflow-cpuEarlier versionspip install --upgrade tensorflow-cpu==1.15.4
tensorflow-cpuintroduced 2.0.0, fixed 2.0.3pip install --upgrade tensorflow-cpu==2.0.3
tensorflow-cpuintroduced 2.1.0, fixed 2.1.2pip install --upgrade tensorflow-cpu==2.1.2
tensorflow-cpuintroduced 2.2.0, fixed 2.2.1pip install --upgrade tensorflow-cpu==2.2.1
tensorflow-cpuintroduced 2.3.0, fixed 2.3.1pip install --upgrade tensorflow-cpu==2.3.1
tensorflow-gpuEarlier versionspip install --upgrade tensorflow-gpu==1.15.4
tensorflow-gpuintroduced 2.0.0, fixed 2.0.3pip install --upgrade tensorflow-gpu==2.0.3
tensorflow-gpuintroduced 2.1.0, fixed 2.1.2pip install --upgrade tensorflow-gpu==2.1.2
tensorflow-gpuintroduced 2.2.0, fixed 2.2.1pip install --upgrade tensorflow-gpu==2.2.1
tensorflow-gpuintroduced 2.3.0, fixed 2.3.1pip install --upgrade tensorflow-gpu==2.3.1

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences