CVE-2020-15266GHSA-XWHF-G6J5-J5GCBIT-TENSORFLOW-2020-15266PYSEC-2020-139PYSEC-2020-296PYSEC-2020-331
Undefined behavior in Tensorflow
- 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.4.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
In Tensorflow before version 2.4.0, when the `boxes` argument of `tf.image.crop_and_resize` has a very large value, the CPU kernel implementation receives it as a C++ `nan` floating point value. Attempting to operate on this is undefined behavior which later produces a segmentation fault. The issue is patched in eccb7ec454e6617738554a255d77f08e60ee0808 and TensorFlow 2.4.0 will be released containing the patch. TensorFlow nightly packages after this commit will also have the issue resolved.
Timeline
- CVE published
- Record last updated
Affected versions
- tensorflow tensorflow
fixed in 2.4.0
- tensorflowPyPI
fixed in 2.4.0
- tensorflow-cpuPyPI
fixed in 2.4.0
- tensorflow-gpuPyPI
fixed in 2.4.0
- tensorflowPyPI
fixed in 2.4.0