CVE-2021-37679

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:H/I:H/A:N
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 it is possible to nest a `tf.map_fn` within another `tf.map_fn` call. However, if the input tensor is a `RaggedTensor` and there is no function signature provided, code assumes the output is a fully specified tensor and fills output buffer with uninitialized contents from the heap. The `t` and `z` outputs should be identical, however this is not the case. The last row of `t` contains data from the heap which can be used to leak other memory information. The bug lies in the conversion from a `Variant` tensor to a `RaggedTensor`. The [implementation](https://github.com/tensorflow/tensorflow/blob/460e000de3a83278fb00b61a16d161b1964f15f4/tensorflow/core/kernels/ragged_tensor_from_variant_op.cc#L177-L190) does not check that all inner shapes match and this results in the additional dimensions. The same implementation can result in data loss, if input tensor is tweaked. We have patched the issue in GitHub commit 4e2565483d0ffcadc719bd44893fb7f609bb5f12. The fix will be included in TensorFlow 2.6.0. We will also cherrypick this commit on TensorFlow 2.5.1, TensorFlow 2.4.3, and TensorFlow 2.3.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.1-1
debian Debian Fixed 2 releases
VersionStatusFixed in
sid Fixed 0
forky Fixed 0

Package impact

EcosystemPackageVulnerableFixed
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-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<4e2565483d0ffcadc719bd44893fb7f609bb5f12||>=2.4.0,<2.4.34e2565483d0ffcadc719bd44893fb7f609bb5f12
python PyPItensorflow-cpu<4e2565483d0ffcadc719bd44893fb7f609bb5f12||>=2.4.0,<2.4.34e2565483d0ffcadc719bd44893fb7f609bb5f12
python PyPItensorflow-gpu<4e2565483d0ffcadc719bd44893fb7f609bb5f12||>=2.4.0,<2.4.34e2565483d0ffcadc719bd44893fb7f609bb5f12

References

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

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