CVE-2021-37640

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:N/A:H
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 the implementation of `tf.raw_ops.SparseReshape` can be made to trigger an integral division by 0 exception. The [implementation](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L176-L181) calls the reshaping functor whenever there is at least an index in the input but does not check that shape of the input or the target shape have both a non-zero number of elements. The [reshape functor](https://github.com/tensorflow/tensorflow/blob/8d72537c6abf5a44103b57b9c2e22c14f5f49698/tensorflow/core/kernels/reshape_util.cc#L40-L78) blindly divides by the dimensions of the target shape. Hence, if this is not checked, code will result in a division by 0. We have patched the issue in GitHub commit 4923de56ec94fff7770df259ab7f2288a74feb41. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1 as this is the other affected version.

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-cpu>=2.4.0,<2.4.32.4.3
python PyPItensorflow-cpu>=2.5.0,<2.5.12.5.1
python PyPItensorflow-gpu<2.3.42.3.4
python PyPItensorflow-gpu>=2.4.0,<2.4.32.4.3
python PyPItensorflow-gpu>=2.5.0,<2.5.12.5.1
python PyPItensorflow<2.3.42.3.4
python PyPItensorflow>=2.4.0,<2.4.32.4.3
python PyPItensorflow>=2.5.0,<2.5.12.5.1
python PyPItensorflow-cpu<2.3.42.3.4
python PyPItensorflow<4923de56ec94fff7770df259ab7f2288a74feb41||>=2.4.0,<2.4.34923de56ec94fff7770df259ab7f2288a74feb41
python PyPItensorflow-gpu<4923de56ec94fff7770df259ab7f2288a74feb41||>=2.4.0,<2.4.34923de56ec94fff7770df259ab7f2288a74feb41
python PyPItensorflow-cpu<4923de56ec94fff7770df259ab7f2288a74feb41||>=2.4.0,<2.4.34923de56ec94fff7770df259ab7f2288a74feb41

References

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

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