Out of bounds write in TFLite
tensorflow
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
tensorflow
| Product | Affected | Fixed in |
|---|---|---|
| tensorflow PyPI |
|
|
| tensorflow-cpu PyPI |
|
≥ 2.6.0 · < 2.6.3≥ 2.7.0 · < 2.7.1
|
| tensorflow-gpu PyPI |
|
|
Tensorflow is an Open Source Machine Learning Framework. An attacker can craft a TFLite model that would cause a write outside of bounds of an array in TFLite. In fact, the attacker can override the linked list used by the memory allocator. This can be leveraged for an arbitrary write primitive under certain conditions. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.
From the CVE record · GitHub_M
A crafted TFLite model can cause an out-of-bounds write in TFLite when it is processed. Under certain conditions, an attacker can use this to achieve an arbitrary write. The input does not specify whether network access or authentication is required.
Teams running the PyPI tensorflow, tensorflow-cpu, or tensorflow-gpu packages should check installations below 2.5.3, from 2.6.0 to below 2.6.3, or from 2.7.0 to below 2.7.1.