CVE-2021-37682

critical
Published 2021-08-25 ยท Modified 2023-12-06
CVSS v3
โ€”
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
CVSS v4 NEW
โ€”
not yet in upstream
VIR risk
9.5

Description

TensorFlow is an end-to-end open source platform for machine learning. In affected versions all TFLite operations that use quantization can be made to use unitialized values. [For example](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/lite/kernels/depthwise_conv.cc#L198-L200). 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. 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.

Predictions

Exploit likelihood
20%
Patch ETA
โ€”

Heuristic predictions, AS-IS, for prioritization only.

Mitigations

No mitigations published for this CVE yet.

The vendor-content worker queues fetches as references arrive (check back in a few minutes). Or โ€” if you've already worked around this in production โ€” publish your fix to the community-verified tier.

โœš Propose a mitigation on Community โ†’ Mitigations published via the community go through AI scoring + 2 human reviewers + 7-day silent objection window before landing here with source_tier=community-verified.

OS impact

arch Arch Fixed 1 release
VersionStatusFixed in
โ€” Fixed 2.5.1-1
debian Debian Fixed 2 releases
VersionStatusFixed in
sid Fixed 0
forky Fixed 0

Package impact

EcosystemPackageVulnerableFixed
python PyPItensorflow-gpu<2.3.42.3.4
python PyPItensorflow<2.3.42.3.4
python PyPItensorflow>=2.4.0,<2.4.32.4.3
python PyPItensorflow-gpu>=2.5.0,<2.5.12.5.1
python PyPItensorflow>=2.5.0,<2.5.12.5.1
python PyPItensorflow-cpu>=2.5.0,<2.5.12.5.1
python PyPItensorflow-gpu>=2.4.0,<2.4.32.4.3
python PyPItensorflow-cpu<2.3.42.3.4
python PyPItensorflow-cpu>=2.4.0,<2.4.32.4.3
python PyPItensorflow<8933b8a21280696ab119b63263babdb54c298538||>=2.4.0,<2.4.3537bc7c723439b9194a358f64d871dd326c18887
python PyPItensorflow-cpu<8933b8a21280696ab119b63263babdb54c298538||>=2.4.0,<2.4.3537bc7c723439b9194a358f64d871dd326c18887
python PyPItensorflow-gpu<8933b8a21280696ab119b63263babdb54c298538||>=2.4.0,<2.4.3537bc7c723439b9194a358f64d871dd326c18887

References

Community-verified mitigations for this CVE will appear above when contributors publish them.

Verify integrity in audit chain (admin only). AS-IS.