Heap OOB read in shape inference for `QuantizeV2`
- 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 2.6.1, 2.7.0
- 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
TensorFlow is an open source platform for machine learning. In affected versions the shape inference code for `QuantizeV2` can trigger a read outside of bounds of heap allocated array. This occurs whenever `axis` is a negative value less than `-1`. In this case, we are accessing data before the start of a heap buffer. The code allows `axis` to be an optional argument (`s` would contain an `error::NOT_FOUND` error code). Otherwise, it assumes that `axis` is a valid index into the dimensions of the `input` tensor. If `axis` is less than `-1` then this results in a heap OOB read. The fix will be included in TensorFlow 2.7.0. We will also cherrypick this commit on TensorFlow 2.6.1, as this version is the only one that is also affected.
Timeline
- CVE published
- Record last updated
Affected versions
- tensorflow tensorflow
From 2.6.0 · fixed in 2.6.1
- tensorflow-gpuPyPI
From 2.6.0 · fixed in 2.6.1; From 2.7.0rc0 · fixed in 2.7.0
- tensorflow-cpuPyPI
From 2.6.0 · fixed in 2.6.1; From 2.7.0rc0 · fixed in 2.7.0
- tensorflowPyPI
From 2.6.0 · fixed in 2.6.1; From 2.7.0rc0 · fixed in 2.7.0
- tensorflowPyPI
From 2.6.0 · fixed in 2.6.1
- tensorflow-cpuPyPI
From 2.6.0 · fixed in 2.6.1
- tensorflow-gpuPyPI
From 2.6.0 · fixed in 2.6.1