CHECK-fail in tf.raw_ops.EncodePng
- 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.1.4, 2.2.3, 2.3.3, 2.4.2
- 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 end-to-end open source platform for machine learning. An attacker can trigger a `CHECK` fail in PNG encoding by providing an empty input tensor as the pixel data. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/e312e0791ce486a80c9d23110841525c6f7c3289/tensorflow/core/kernels/image/encode_png_op.cc#L57-L60) only validates that the total number of pixels in the image does not overflow. Thus, an attacker can send an empty matrix for encoding. However, if the tensor is empty, then the associated buffer is `nullptr`. Hence, when calling `png::WriteImageToBuffer`(https://github.com/tensorflow/tensorflow/blob/e312e0791ce486a80c9d23110841525c6f7c3289/tensorflow/core/kernels/image/encode_png_op.cc#L79-L93), the first argument (i.e., `image.flat<T>().data()`) is `NULL`. This then triggers the `CHECK_NOTNULL` in the first line of `png::WriteImageToBuffer`(https://github.com/tensorflow/tensorflow/blob/e312e0791ce486a80c9d23110841525c6f7c3289/tensorflow/core/lib/png/png_io.cc#L345-L349). Since `image` is null, this results in `abort` being called after printing the stacktrace. Effectively, this allows an attacker to mount a denial of service attack. The fix will be included in TensorFlow 2.5.0. We will also cherrypick this commit on TensorFlow 2.4.2, TensorFlow 2.3.3, TensorFlow 2.2.3 and TensorFlow 2.1.4, as these are also affected and still in supported range.
Timeline
- CVE published
- Record last updated
Affected versions
- tensorflow tensorflow
fixed in 2.1.4; From 2.2.0 · fixed in 2.2.3; From 2.3.0 · fixed in 2.3.3; From 2.4.0 · fixed in 2.4.2
- tensorflowPyPI
fixed in 2.1.4
- tensorflowPyPI
From 2.2.0 · fixed in 2.2.3
- tensorflowPyPI
From 2.3.0 · fixed in 2.3.3
- tensorflowPyPI
From 2.4.0 · fixed in 2.4.2
- tensorflow-cpuPyPI
fixed in 2.1.4
- tensorflow-cpuPyPI
From 2.2.0 · fixed in 2.2.3
- tensorflow-cpuPyPI
From 2.3.0 · fixed in 2.3.3
- tensorflow-cpuPyPI
From 2.4.0 · fixed in 2.4.2
- tensorflow-gpuPyPI
fixed in 2.1.4
- tensorflow-gpuPyPI
From 2.2.0 · fixed in 2.2.3
- tensorflow-gpuPyPI
From 2.3.0 · fixed in 2.3.3
- tensorflow-gpuPyPI
From 2.4.0 · fixed in 2.4.2
- tensorflowPyPI
fixed in 2.1.4; From 2.2.0 · fixed in 2.2.3; From 2.3.0 · fixed in 2.3.3; From 2.4.0 · fixed in 2.4.2
- tensorflow-cpuPyPI
fixed in 2.1.4; From 2.2.0 · fixed in 2.2.3; From 2.3.0 · fixed in 2.3.3; From 2.4.0 · fixed in 2.4.2
- tensorflow-gpuPyPI
fixed in 2.1.4; From 2.2.0 · fixed in 2.2.3; From 2.3.0 · fixed in 2.3.3; From 2.4.0 · fixed in 2.4.2