CVE-2021-29519

CHECK-fail in SparseCross due to type confusion

MEDIUM

5.5

CVSS Score

Published: May 14, 2021 at 07:35 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

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

Description

TensorFlow is an end-to-end open source platform for machine learning. The API of `tf.raw_ops.SparseCross` allows combinations which would result in a `CHECK`-failure and denial of service. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/3d782b7d47b1bf2ed32bd4a246d6d6cadc4c903d/tensorflow/core/kernels/sparse_cross_op.cc#L114-L116) is tricked to consider a tensor of type `tstring` which in fact contains integral elements. Fixing the type confusion by preventing mixing `DT_STRING` and `DT_INT64` types solves this issue. 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.

Tensorflow · Google

95%

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

TensorFlow · Tensorflow

60%

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:

Patch and advisory references

References (2)

x_refsource_MISCPatchThird Party Advisory

Source: [email protected]

https://github.com/tensorflow/tensorflow/commit/b1cc5e5a50e7cee09f2c6eb48eb40ee9c4125025

x_refsource_CONFIRMExploitPatchThird Party Advisory

Source: [email protected]

https://github.com/tensorflow/tensorflow/security/advisories/GHSA-772j-h9xw-ffp5

CVSS

5.5MEDIUM[email protected]

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

Vector?

Quick Info

StatusMODIFIED

CWE

CWE-843

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.

Create account Sign in

Free plan, no card