CVE-2020-15209
Summary
| CVE | CVE-2020-15209 |
| State | PUBLIC |
| Assigner | [email protected] |
| Source Priority | CVE Program / NVD first with legacy fallback |
| Published | 2020-09-25 19:15:00 UTC |
| Updated | 2021-09-16 15:45:00 UTC |
| Description | 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. |
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|
| Null pointer dereference in TFLite · Advisory · tensorflow/tensorflow · GitHub |
CONFIRM |
github.com |
Exploit, Third Party Advisory |
| Release TensorFlow 2.3.1 · tensorflow/tensorflow · GitHub |
MISC |
github.com |
Third Party Advisory |
| [security-announce] openSUSE-SU-2020:1766-1: moderate: Security update f |
SUSE |
lists.opensuse.org |
|
| [tflite] Ensure input tensors don't have `nullptr` buffers. · tensorflow/tensorflow@0b5662b · GitHub |
MISC |
github.com |
Patch, Third Party Advisory |
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
Legacy QID Mappings
- 981465 Python (pip) Security Update for tensorflow-gpu (GHSA-qh32-6jjc-qprm)