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.
ProviderTypeBase ScoreAtk. VectorAtk. ComplexityPriv. RequiredVector
GitHub_MCNA
5.9 MEDIUM
NETWORK
HIGH
NONE
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Base Score
CVSS 3.x
EPSS Score
Percentile: 55.69%
Affected Products (NVD)
VendorProductVersion
googletensorflow
𝑥
< 1.15.4
googletensorflow
2.0.0 ≤
𝑥
< 2.0.3
googletensorflow
2.1.0 ≤
𝑥
< 2.1.2
googletensorflow
2.2.0 ≤
𝑥
< 2.2.1
googletensorflow
2.3.0 ≤
𝑥
< 2.3.1
opensuseleap
15.2
𝑥
= Vulnerable software versions
Early Detection
Affected products identified ahead of NVD analysis through intelligence sources.
VendorProductVersionSource
tensorflowtensorflow
𝑥
< 1.15.4
CNA
Debian logo
Debian Releases
Debian Product
Codename
tensorflow
forky
2.14.1+dfsg-3.1
fixed
sid
2.14.1+dfsg-3.1
fixed