CVE-2021-29608

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:L/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. Due to lack of validation in `tf.raw_ops.RaggedTensorToTensor`, an attacker can exploit an undefined behavior if input arguments are empty. The implementation(https://github.com/tensorflow/tensorflow/blob/656e7673b14acd7835dc778867f84916c6d1cac2/tensorflow/core/kernels/ragged_tensor_to_tensor_op.cc#L356-L360) only checks that one of the tensors is not empty, but does not check for the other ones. There are multiple `DCHECK` validations to prevent heap OOB, but these are no-op in release builds, hence they don't prevent anything. The fix will be included in TensorFlow 2.5.0. We will also cherrypick these commits 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<b761c9b652af2107cfbc33efd19be0ce41daa33e||>=2.4.0,<2.4.3c4d7afb6a5986b04505aca4466ae1951686c80f6
python PyPItensorflow-cpu<b761c9b652af2107cfbc33efd19be0ce41daa33e||>=2.4.0,<2.4.3c4d7afb6a5986b04505aca4466ae1951686c80f6
python PyPItensorflow-gpu<b761c9b652af2107cfbc33efd19be0ce41daa33e||>=2.4.0,<2.4.3c4d7afb6a5986b04505aca4466ae1951686c80f6

References

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

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