Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2022-21728: n/a in n/a

0
High
VulnerabilityCVE-2022-21728cvecve-2022-21728
Published: Thu Feb 03 2022 (02/03/2022, 10:55:55 UTC)
Source: CVE
Vendor/Project: n/a
Product: n/a

Description

Tensorflow is an Open Source Machine Learning Framework. The implementation of shape inference for `ReverseSequence` does not fully validate the value of `batch_dim` and can result in a heap OOB read. There is a check to make sure the value of `batch_dim` does not go over the rank of the input, but there is no check for negative values. Negative dimensions are allowed in some cases to mimic Python's negative indexing (i.e., indexing from the end of the array), however if the value is too negative then the implementation of `Dim` would access elements before the start of an array. The fix will be included in TensorFlow 2.8.0. We will also cherrypick this commit on TensorFlow 2.7.1, TensorFlow 2.6.3, and TensorFlow 2.5.3, as these are also affected and still in supported range.

AI-Powered Analysis

AILast updated: 07/05/2025, 21:55:04 UTC

Technical Analysis

CVE-2022-21728 is a high-severity vulnerability in TensorFlow, an open-source machine learning framework widely used for developing and deploying machine learning models. The vulnerability arises from improper validation in the shape inference implementation of the `ReverseSequence` operation. Specifically, the parameter `batch_dim` is not fully validated: while there is a check to ensure `batch_dim` does not exceed the rank of the input tensor, negative values are not properly checked. Negative indexing is sometimes allowed in TensorFlow to mimic Python's negative indexing behavior, but if `batch_dim` is too negative, it causes the internal `Dim` implementation to access memory locations before the start of an array, resulting in a heap out-of-bounds (OOB) read. This type of memory access can lead to information disclosure or potentially destabilize the application, causing denial of service. The vulnerability affects multiple TensorFlow versions prior to 2.8.0, including 2.7.1, 2.6.3, and 2.5.3, which are still supported. The fix involves adding proper validation to ensure `batch_dim` values are within valid bounds. The CVSS 3.1 score is 8.1 (high), reflecting the network attack vector, low attack complexity, requirement for privileges but no user interaction, and high impact on confidentiality and availability. No known exploits are reported in the wild as of the publication date. The vulnerability is categorized under CWE-125 (Out-of-bounds Read).

Potential Impact

For European organizations, the impact of this vulnerability can be significant, especially for those relying on TensorFlow for critical machine learning workloads in production environments. Exploitation could allow attackers with some level of access (local or network with privileges) to read sensitive memory contents, potentially exposing confidential data processed by machine learning models, such as personal data, intellectual property, or proprietary algorithms. Additionally, the heap OOB read could cause application crashes or denial of service, disrupting AI-driven services or analytics platforms. Given the increasing adoption of AI and ML in sectors like finance, healthcare, manufacturing, and government across Europe, exploitation could lead to operational disruptions, data breaches, and compliance violations under GDPR. Although exploitation requires some privileges, the network attack vector means that compromised internal systems or malicious insiders could leverage this vulnerability. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as threat actors may develop exploits over time.

Mitigation Recommendations

European organizations should prioritize upgrading TensorFlow to version 2.8.0 or later, or apply the backported patches available for versions 2.7.1, 2.6.3, and 2.5.3. In environments where immediate upgrade is not feasible, organizations should implement strict access controls to limit who can execute or modify TensorFlow workloads, minimizing the risk of exploitation. Monitoring and logging of TensorFlow usage and anomalous behavior should be enhanced to detect potential exploitation attempts. Additionally, organizations should conduct code audits and testing of machine learning pipelines that use the `ReverseSequence` operation to identify and remediate any unsafe inputs or configurations. Network segmentation and isolation of critical ML infrastructure can reduce exposure. Finally, integrating vulnerability management processes to track TensorFlow updates and CVE disclosures will ensure timely patching.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.1
Assigner Short Name
GitHub_M
Date Reserved
2021-11-16T00:00:00.000Z
Cisa Enriched
true
Cvss Version
3.1
State
PUBLISHED

Threat ID: 682d981ec4522896dcbdbebd

Added to database: 5/21/2025, 9:08:46 AM

Last enriched: 7/5/2025, 9:55:04 PM

Last updated: 2/5/2026, 1:34:03 AM

Views: 45

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

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

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats