CVE-2021-29585

critical
Published 2021-05-21 ยท Modified 2023-12-06
CVSS v3
โ€”
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/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. The TFLite computation for size of output after padding, `ComputeOutSize`(https://github.com/tensorflow/tensorflow/blob/0c9692ae7b1671c983569e5d3de5565843d500cf/tensorflow/lite/kernels/padding.h#L43-L55), does not check that the `stride` argument is not 0 before doing the division. Users can craft special models such that `ComputeOutSize` is called with `stride` set to 0. 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.

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.0-1
debian Debian Fixed 2 releases
VersionStatusFixed in
sid Fixed 0
forky Fixed 0

Package impact

EcosystemPackageVulnerableFixed
python PyPItensorflow<2.1.42.1.4
python PyPItensorflow>=2.2.0,<2.2.32.2.3
python PyPItensorflow>=2.3.0,<2.3.32.3.3
python PyPItensorflow>=2.4.0,<2.4.22.4.2
python PyPItensorflow-cpu<2.1.42.1.4
python PyPItensorflow-cpu>=2.2.0,<2.2.32.2.3
python PyPItensorflow-cpu>=2.3.0,<2.3.32.3.3
python PyPItensorflow-cpu>=2.4.0,<2.4.22.4.2
python PyPItensorflow-gpu<2.1.42.1.4
python PyPItensorflow-gpu>=2.2.0,<2.2.32.2.3
python PyPItensorflow-gpu>=2.3.0,<2.3.32.3.3
python PyPItensorflow-gpu>=2.4.0,<2.4.22.4.2
python PyPItensorflow<49847ae69a4e1a97ae7f2db5e217c77721e37948||>=2.4.0,<2.4.349847ae69a4e1a97ae7f2db5e217c77721e37948
python PyPItensorflow-cpu<49847ae69a4e1a97ae7f2db5e217c77721e37948||>=2.4.0,<2.4.349847ae69a4e1a97ae7f2db5e217c77721e37948
python PyPItensorflow-gpu<49847ae69a4e1a97ae7f2db5e217c77721e37948||>=2.4.0,<2.4.349847ae69a4e1a97ae7f2db5e217c77721e37948

References

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

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