Data corruption in tensorflow-lite
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.15.4, 2.0.3, 2.1.2, 2.2.1, 2.3.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can craft cases where this is larger than that of the second tensor. In turn, this would result in reads/writes outside of bounds since the interpreter will wrongly assume that there is enough data in both tensors. The issue is patched in commit 8ee24e7949a203d234489f9da2c5bf45a7d5157d, and is released in TensorFlow versions 1.15.4, 2.0.3, 2.1.2, 2.2.1, or 2.3.1.
Timeline
- CVE published
- Record last updated
Affected versions
- tensorflow tensorflow
fixed in 1.15.4; From 2.0.0 · fixed in 2.0.3; From 2.1.0 · fixed in 2.1.2; From 2.2.0 · fixed in 2.2.1; From 2.3.0 · fixed in 2.3.1
- tensorflow-cpuPyPI
fixed in 1.15.4; From 2.0.0 · fixed in 2.0.3; From 2.1.0 · fixed in 2.1.2; From 2.2.0 · fixed in 2.2.1; From 2.3.0 · fixed in 2.3.1
- tensorflow-gpuPyPI
fixed in 1.15.4; From 2.0.0 · fixed in 2.0.3; From 2.1.0 · fixed in 2.1.2; From 2.2.0 · fixed in 2.2.1; From 2.3.0 · fixed in 2.3.1
- tensorflowPyPI
fixed in 1.15.4
- tensorflowPyPI
From 2.0.0 · fixed in 2.0.3
- tensorflowPyPI
From 2.1.0 · fixed in 2.1.2
- tensorflowPyPI
From 2.2.0 · fixed in 2.2.1
- tensorflowPyPI
From 2.3.0 · fixed in 2.3.1
- tensorflow-cpuPyPI
fixed in 1.15.4
- tensorflow-cpuPyPI
From 2.0.0 · fixed in 2.0.3
- tensorflow-cpuPyPI
From 2.1.0 · fixed in 2.1.2
- tensorflow-cpuPyPI
From 2.2.0 · fixed in 2.2.1
- tensorflow-cpuPyPI
From 2.3.0 · fixed in 2.3.1
- tensorflow-gpuPyPI
fixed in 1.15.4
- tensorflow-gpuPyPI
From 2.0.0 · fixed in 2.0.3
- tensorflow-gpuPyPI
From 2.1.0 · fixed in 2.1.2
- tensorflow-gpuPyPI
From 2.2.0 · fixed in 2.2.1
- tensorflow-gpuPyPI
From 2.3.0 · fixed in 2.3.1
- tensorflowPyPI
fixed in 1.15.4; From 2.0.0 · fixed in 2.0.3; From 2.1.0 · fixed in 2.1.2; From 2.2.0 · fixed in 2.2.1; From 2.3.0 · fixed in 2.3.1