NULL pointer dereference in Google Tensorflow
CVE-2020-15209
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 5.9 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS 0.008, 57.2th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Google Tensorflow
- Tensorflow — versions < 1.15.4, >= 2.0.0, < 2.0.3, >= 2.1.0, < 2.1.2
- openSUSE Leap — versions 15.2
Weakness classification (CWE)
References
- github.com/tensorflow/tensorflow/releases/tag/v2.3.1 (Third Party Advisory)
- github.com/tensorflow/tensorflow/security/advisories/GHSA-qh32-6jjc-qprm (Exploit, Third Party Advisory)
- github.com/tensorflow/tensorflow/commit/0b5662bc2be13a8c8f044d925d87fb6e56247cd8 (Patch, Third Party Advisory)
- openSUSE-SU-2020:1766 (vendor-advisory, Mailing List, Third Party Advisory)