CVE-2021-29549

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. An attacker can cause a runtime division by zero error and denial of service in `tf.raw_ops.QuantizedBatchNormWithGlobalNormalization`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L289-L295) computes a modulo operation without validating that the divisor is not zero. Since `vector_num_elements` is determined based on input shapes(https://github.com/tensorflow/tensorflow/blob/6f26b3f3418201479c264f2a02000880d8df151c/tensorflow/core/kernels/quantized_add_op.cc#L522-L544), a user can trigger scenarios where this quantity is 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<744009c9e5cc5d0447f0dc39d055f917e1fd9e16||>=2.4.0,<2.4.3744009c9e5cc5d0447f0dc39d055f917e1fd9e16
python PyPItensorflow-cpu<744009c9e5cc5d0447f0dc39d055f917e1fd9e16||>=2.4.0,<2.4.3744009c9e5cc5d0447f0dc39d055f917e1fd9e16
python PyPItensorflow-gpu<744009c9e5cc5d0447f0dc39d055f917e1fd9e16||>=2.4.0,<2.4.3744009c9e5cc5d0447f0dc39d055f917e1fd9e16

References

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

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