LiveActive security incident?Get immediate response
CVE Record

CVE-2021-29543: CHECK-fail in `CTCGreedyDecoder`

TensorFlow is an end-to-end open source platform for machine learning. An attacker can trigger a denial of service via a `CHECK`-fail in `tf.raw_ops.CTCGreedyDecoder`. This is because the implementation(https://github.com/tensorflow/tensorflow/blob/1615440b17b364b875eb06f43d087381f1460a65/tensorflow/core/kernels/ctc_decoder_ops.cc#L37-L50) has a `CHECK_LT` inserted to validate some invariants. When this condition is false, the program aborts, instead of returning a valid error to the user. This abnormal termination can be weaponized in denial of service attacks. 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.

LowCVSS 2.5Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2021-29543 is a low-severity TensorFlow denial-of-service flaw. A local, low-privileged attacker who can reach a vulnerable CTC greedy decoder path may cause the process to abort instead of returning a normal error. The direct business risk is service interruption in affected machine learning workloads, not data theft or system takeover.

Executive priority

Treat this as routine patching unless vulnerable TensorFlow decoding is exposed in production workflows. Prioritize internet-facing or multi-tenant ML services first, but the source evidence supports low business urgency compared with code execution or data exposure vulnerabilities.

Technical view

The issue is a CWE-617 reachable assertion in tf.raw_ops.CTCGreedyDecoder. TensorFlow used a CHECK_LT invariant check in ctc_decoder_ops.cc; when false, TensorFlow aborts. Affected ranges include TensorFlow versions below listed patched releases: 2.1.4, 2.2.3, 2.3.3, and 2.4.2, with the fix also included in 2.5.0.

Likely exposure

Exposure is most likely in applications, services, notebooks, or batch ML jobs running affected TensorFlow versions and using CTC greedy decoding. The CVSS vector indicates local access, high attack complexity, and low privileges are required, with availability impact only.

Exploitation context

The provided sources describe denial-of-service potential through abnormal process termination. They do not report active exploitation, and the CVE is not listed as KEV in the provided bundle. No evidence here supports remote exploitation, confidentiality loss, or integrity impact.

Researcher notes

The key behavior is a reachable CHECK failure rather than graceful error handling. Analysis should stay focused on version confirmation, affected decoder usage, and availability blast radius. The provided evidence does not establish exploit prevalence or broader product impact beyond TensorFlow.

Mitigation direction

  • Upgrade TensorFlow to 2.5.0 or supported patched branch versions 2.4.2, 2.3.3, 2.2.3, or 2.1.4.
  • Review the TensorFlow advisory before relying on branch-specific remediation.
  • Restrict untrusted access to ML workflows using CTC greedy decoding until patched.
  • Rebuild containers or runtime images that bundle affected TensorFlow versions.

Validation and detection

  • Inventory TensorFlow versions in applications, containers, notebooks, and ML worker images.
  • Check whether code paths invoke tf.raw_ops.CTCGreedyDecoder or CTC decoder wrappers.
  • Confirm dependency lockfiles and runtime environments resolve to patched TensorFlow versions.
  • Review service restart or crash telemetry for unexplained TensorFlow process aborts.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-617: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-29543 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
2.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
2.5CVSS 3.1LowCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L11.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

2.5Low
CVSS 3.1 vector shape for CVE-2021-29543Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
tensorflowtensorflow< 2.1.4, >= 2.2.0, < 2.2.3, >= 2.3.0, < 2.3.3, >= 2.4.0, < 2.4.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-617 · source CWE mapping

Reachable Assertion

Reachable Assertion represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.