Advisory

GHSA-cvpc-8phh-8f45

Also known as: BIT-tensorflow-2020-15211, CVE-2020-15211, PYSEC-2020-134, PYSEC-2020-291, PYSEC-2020-326

Summary

Out of bounds access in tensorflow-lite

Details

Impact
In TensorFlow Lite, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices for the tensors, indexing into an array of tensors that is owned by the subgraph. This results in a pattern of double array indexing when trying to get the data of each tensor: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/kernels/kernel_util.cc#L36

However, some operators can have some tensors be optional. To handle this scenario, the flatbuffer model uses a negative -1 value as index for these tensors:
https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/c/common.h#L82

This results in special casing during validation at model loading time: https://github.com/tensorflow/tensorflow/blob/0e68f4d3295eb0281a517c3662f6698992b7b2cf/tensorflow/lite/core/subgraph.cc#L566-L580

Unfortunately, this means that the -1 index is a valid tensor index for any operator, including those that don't expect optional inputs and including for output tensors. Thus, this allows writing and reading from outside the bounds of heap allocated arrays, although only at a specific offset from the start of these arrays.

This results in both read and write gadgets, albeit very limited in scope.

Patches
We have patched the issue in several commits (46d5b0852, 00302787b7, e11f5558, cd31fd0ce, 1970c21, and fff2c83). We 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.

Workarounds
A potential workaround would be to add a custom Verifier to the model loading code to ensure that only operators which accept optional inputs use the -1 special value and only for the tensors that they expect to be optional. Since this allow-list type approach is erro-prone, we advise upgrading to the patched code.

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2020-09-25 18:28 UTC
Modified
2026-07-08 06:27 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