CVEvulnerability

CVE-2021-29571

7.8 HIGH Published 2021-05-14 Modified 2026-06-17 Official page ↗
Status
Modified
Published
2021-05-14
Last modified
2026-06-17
Assigner
[email protected]
CVSS 3.1 ([email protected])
4.5 MEDIUM — CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
CVSS 3.1 ([email protected])
7.8 HIGH — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.0 ([email protected])
4.6 MEDIUM — AV:L/AC:L/Au:N/C:P/I:P/A:P
Weaknesses
CWE-787

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. 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.

Affected configurations

• google tensorflow (< 2.1.4) • google tensorflow (>= 2.2.0 < 2.2.3) • google tensorflow (>= 2.3.0 < 2.3.3) • google tensorflow (>= 2.4.0 < 2.4.2)

Related

Weakness · CWE (1)

  • CWE-787 Out-of-bounds Write weakness

References