CVE-2021-29571

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:L/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. The implementation of `tf.raw_ops.MaxPoolGradWithArgmax` can cause reads outside of bounds of heap allocated data if attacker supplies specially crafted inputs. The implementation(https://github.com/tensorflow/tensorflow/blob/31bd5026304677faa8a0b77602c6154171b9aec1/tensorflow/core/kernels/image/draw_bounding_box_op.cc#L116-L130) assumes that the last element of `boxes` input is 4, as required by [the op](https://www.tensorflow.org/api_docs/python/tf/raw_ops/DrawBoundingBoxesV2). Since this is not checked attackers passing values less than 4 can write outside of bounds of heap allocated objects and cause memory corruption. If the last dimension in `boxes` is less than 4, accesses similar to `tboxes(b, bb, 3)` will access data outside of bounds. Further during code execution there are also writes to these indices. 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<79865b542f9ffdc9caeb255631f7c56f1d4b6517||>=2.4.0,<2.4.379865b542f9ffdc9caeb255631f7c56f1d4b6517
python PyPItensorflow-cpu<79865b542f9ffdc9caeb255631f7c56f1d4b6517||>=2.4.0,<2.4.379865b542f9ffdc9caeb255631f7c56f1d4b6517
python PyPItensorflow-gpu<79865b542f9ffdc9caeb255631f7c56f1d4b6517||>=2.4.0,<2.4.379865b542f9ffdc9caeb255631f7c56f1d4b6517

References

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

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