Skip to main content

CVE-2022-35991: CWE-617: Reachable Assertion in tensorflow tensorflow

Medium
Published: Fri Sep 16 2022 (09/16/2022, 22:20:16 UTC)
Source: CVE
Vendor/Project: tensorflow
Product: tensorflow

Description

TensorFlow is an open source platform for machine learning. When `TensorListScatter` and `TensorListScatterV2` receive an `element_shape` of a rank greater than one, they give a `CHECK` fail that can trigger a denial of service attack. We have patched the issue in GitHub commit bb03fdf4aae944ab2e4b35c7daa051068a8b7f61. The fix will be included in TensorFlow 2.10.0. We will also cherrypick this commit on TensorFlow 2.9.1, TensorFlow 2.8.1, and TensorFlow 2.7.2, as these are also affected and still in supported range. There are no known workarounds for this issue.

AI-Powered Analysis

AILast updated: 06/22/2025, 18:21:09 UTC

Technical Analysis

CVE-2022-35991 is a vulnerability identified in TensorFlow, an open-source machine learning platform widely used for developing and deploying machine learning models. The issue arises specifically in the TensorFlow operations `TensorListScatter` and `TensorListScatterV2`. When these operations receive an `element_shape` parameter with a rank greater than one, they trigger a CHECK failure, which is an assertion mechanism used internally by TensorFlow to validate assumptions during execution. This failure leads to a denial of service (DoS) condition by causing the affected process to crash or terminate unexpectedly. The root cause is classified under CWE-617 (Reachable Assertion), indicating that an assertion can be triggered by crafted input, potentially disrupting normal operation. The vulnerability affects multiple TensorFlow versions: all versions prior to 2.7.2, versions between 2.8.0 and 2.8.1, and versions between 2.9.0 and 2.9.1. The issue has been patched in TensorFlow 2.10.0 and backported to supported versions 2.7.2, 2.8.1, and 2.9.1. No known workarounds exist, and no exploits have been observed in the wild to date. The vulnerability requires an attacker to supply malformed input to the TensorListScatter operations, which may be possible in environments where untrusted data is processed by TensorFlow models. The impact is primarily denial of service, affecting availability rather than confidentiality or integrity. Since TensorFlow is often deployed in server environments, cloud platforms, and edge devices for machine learning workloads, this vulnerability could disrupt AI services or pipelines if exploited.

Potential Impact

For European organizations, the primary impact of CVE-2022-35991 is the potential disruption of machine learning services that rely on vulnerable TensorFlow versions. This could affect industries such as finance, healthcare, automotive, and manufacturing, where AI-driven analytics, predictive modeling, or automation are critical. A denial of service attack could lead to downtime of AI applications, delayed processing, or interruption of automated decision-making systems, potentially causing operational inefficiencies or service unavailability. While the vulnerability does not directly compromise data confidentiality or integrity, the loss of availability can have cascading effects, especially in time-sensitive or safety-critical applications. Organizations using TensorFlow in multi-tenant or cloud environments may face increased risk if attackers can supply malicious inputs remotely. Additionally, research institutions and AI startups across Europe that deploy TensorFlow models in production environments could experience service interruptions. The absence of known exploits reduces immediate risk, but the widespread use of TensorFlow and the lack of workarounds necessitate prompt patching to mitigate potential future attacks.

Mitigation Recommendations

European organizations should prioritize upgrading TensorFlow installations to version 2.10.0 or later, or apply the backported patches available in versions 2.7.2, 2.8.1, and 2.9.1. Since no workarounds exist, patching is the only effective mitigation. Organizations should audit their environments to identify all TensorFlow deployments, including development, testing, and production systems, to ensure comprehensive coverage. Implement input validation and sanitization where possible to restrict or verify the shape and rank of tensors passed to TensorListScatter operations, reducing the risk of malformed inputs triggering the assertion. Deploy runtime monitoring and anomaly detection to identify unexpected crashes or service interruptions in AI workloads. For cloud-based deployments, leverage provider security features such as network segmentation and access controls to limit exposure to untrusted inputs. Additionally, incorporate TensorFlow vulnerability scanning into regular security assessments and CI/CD pipelines to detect and remediate outdated versions proactively. Document and test incident response procedures for AI service disruptions to minimize downtime if exploitation occurs.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2022-07-15T00:00:00.000Z
Cisa Enriched
true

Threat ID: 682d9845c4522896dcbf42cb

Added to database: 5/21/2025, 9:09:25 AM

Last enriched: 6/22/2025, 6:21:09 PM

Last updated: 8/14/2025, 3:41:57 AM

Views: 13

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats