LiveActive security incident?Get immediate response
CVE Record

CVE-2021-29563: CHECK-fail in `tf.raw_ops.RFFT`

TensorFlow is an end-to-end open source platform for machine learning. An attacker can cause a denial of service by exploiting a `CHECK`-failure coming from the implementation of `tf.raw_ops.RFFT`. Eigen code operating on an empty matrix can trigger on an assertion and will cause program termination. 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-29563 is a low-severity TensorFlow denial-of-service issue. A user who can run TensorFlow code locally may trigger a failed internal check in RFFT handling, terminating the process. The business risk is mainly interruption of ML workloads, not data theft or privilege escalation.

Executive priority

Treat as routine patching unless TensorFlow is used in shared execution environments with untrusted users. Prioritize affected ML platforms where a process crash could disrupt production pipelines, customer workloads, or scheduled model processing.

Technical view

The flaw is a CWE-617 reachable assertion in tf.raw_ops.RFFT. Eigen code operating on an empty matrix can hit an assertion and terminate the TensorFlow process. CVSS is 2.5: local access, high complexity, low privileges, no confidentiality or integrity impact, and low availability impact.

Likely exposure

Exposure is most likely in environments running affected TensorFlow versions where low-privileged local users or submitted jobs can execute TensorFlow operations. Shared notebooks, research systems, and ML batch workers are more relevant than externally exposed services, based on the local attack vector.

Exploitation context

The supplied sources do not show active exploitation, and the CVE is not marked KEV. Exploitation requires local access with low privileges and high complexity. The documented outcome is process termination, not remote compromise or data access.

Researcher notes

Evidence supports a localized availability issue caused by an assertion failure in RFFT handling. The bundle identifies fixed release targets and a TensorFlow commit, but does not provide broader exploit telemetry, compensating controls, or evidence of remote reachability.

Mitigation direction

  • Upgrade TensorFlow to 2.5.0 or a fixed supported patch release.
  • Use 2.4.2, 2.3.3, 2.2.3, or 2.1.4 where those branches apply.
  • Check TensorFlow’s advisory for vendor-specific upgrade guidance.
  • Restrict untrusted users from running TensorFlow jobs on shared hosts until patched.

Validation and detection

  • Inventory TensorFlow versions across notebooks, services, containers, and batch workers.
  • Compare installed versions against the affected ranges in the CVE record.
  • Confirm upgraded environments report fixed TensorFlow versions.
  • Review whether workloads expose tf.raw_ops.RFFT through user-controlled jobs or plugins.
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-29563 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-29563Attack 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.