MISFIRE

Browse / AI Framework and Platform Flaws / CVE-2021-37682

Use of unitialized value in TFLite

CVE-2021-37682 ยท 2021-08-25 moderate

Class
AI Framework and Platform Flaws (filed by a model that read the source)
Technique
Memory corruption
Affected
tensorflow-cpu, tensorflow (PyPI)
CVSS
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
EPSS
0.2% chance of exploitation in 30 days

How it works, in short

Quantized TFLite operations read quantization parameters without checking the quantization type, so they can use uninitialized pointers. (Our summary, written by a model. The source text is below.)

Details

Impact

All TFLite operations that use quantization can be made to use unitialized values. For example:

    const auto* affine_quantization =
        reinterpret_cast<TfLiteAffineQuantization*>(
            filter->quantization.params);

The issue stems from the fact that quantization.params is only valid if quantization.type is different that kTfLiteNoQuantization. However, these checks are missing in large parts of the code.

Patches

We have patched the issue in GitHub commits 537bc7c723439b9194a358f64d871dd326c18887, 4a91f2069f7145aab6ba2d8cfe41be8a110c18a5 and 8933b8a21280696ab119b63263babdb54c298538.

The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.4, as these are also affected and still in supported range.

For more information

Please consult our security guide for more information regarding the security model and how to contact us with issues and questions.

Attribution

This vulnerability has been reported by members of the Aivul Team from Qihoo 360.

References

Source: GitHub Advisory Database, used under CC BY 4.0.