CVE-2020-15209
CVE.org · Published
- Record status
- Published
- Identifier year (not publication year)
- 2020
- Source publication
- Source updated
- Imported by cveboard
- Source snapshot
- cve_2026-10-24_midnight_baseline ·
CNA source text (English)
Null pointer dereference in tensorflow-lite
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.
Scoped product and version facts
Fix information unknown; no fixed version is derived here. Missing information does not prove that no fix exists.
Exploitation unknown; this catalogue does not assess exploitation.
tensorflow
- Vendor
- tensorflow
- Product
- tensorflow
- Platforms
- Unknown
- Default status
Unknown
| Version (version) | Status (status) | Version scheme (versionType) | Exclusive end (lessThan) | Inclusive end (lessThanOrEqual) | Status changes (at → status) |
|---|---|---|---|---|---|
| < 1.15.4 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 2.0.0, < 2.0.3 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 2.1.0, < 2.1.2 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 2.2.0, < 2.2.1 | affected | Unavailable | Unavailable | Unavailable | None listed |
| >= 2.3.0, < 2.3.1 | affected | Unavailable | Unavailable | Unavailable | None listed |