CVE-2021-37682: Use of unitialized value in TFLite
4.4
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.1052%
CWE
Published
8/25/2021
Updated
11/13/2024
KEV Status
No
Technology
Python
Technical Details
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
---|---|---|---|
tensorflow | pip | < 2.3.4 | 2.3.4 |
tensorflow | pip | >= 2.4.0, < 2.4.3 | 2.4.3 |
tensorflow | pip | = 2.5.0 | 2.5.1 |
tensorflow-cpu | pip | < 2.3.4 | 2.3.4 |
tensorflow-cpu | pip | >= 2.4.0, < 2.4.3 | 2.4.3 |
tensorflow-cpu | pip | = 2.5.0 | 2.5.1 |
tensorflow-gpu | pip | < 2.3.4 | 2.3.4 |
tensorflow-gpu | pip | >= 2.4.0, < 2.4.3 | 2.4.3 |
tensorflow-gpu | pip | = 2.5.0 | 2.5.1 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability stems from accessing quantization.params without validating quantization.type first. The patched commits explicitly add TF_LITE_ENSURE checks for quantization.type != kTfLiteNoQuantization before accessing params in these functions. The functions are clearly identified in the commit diffs across multiple files (unidirectional_sequence_lstm.cc, svdf.cc, depthwise_conv.cc), all following the same vulnerability pattern of missing quantization type checks when handling quantization parameters.