CVE-2021-29571

Memory corruption in `DrawBoundingBoxesV2`

HIGH
7.8
CVSS Score
Published: May 14, 2021 at 07:16 PM UTC
Updated: June 17, 2026 at 03:47 AM UTC
2 products affected across 2 vendorsTensorflowTensorFlow

Using tensorflow by tensorflow?

Get instant alerts when new vulnerabilities affect tensorflow - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2.1.42.2.0 ≤ v < 2.2.32.3.0 ≤ v < 2.3.32.4.0 ≤ v < 2.4.2
Affected range stops below 2.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.2.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.3.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.4.2, so it looks safe — our inference, not a vendor statement
v < 2.1.4v < 2.2.3v < 2.3.3v < 2.4.2
Affected range stops below 2.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.2.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.3.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2.4.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card