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-2025-2134: CWE-410 in IBM Jazz Reporting Service

0
Low
VulnerabilityCVE-2025-2134cvecve-2025-2134cwe-410
Published: Wed Feb 04 2026 (02/04/2026, 21:07:26 UTC)
Source: CVE Database V5
Vendor/Project: IBM
Product: Jazz Reporting Service

Description

IBM Jazz Reporting Service could allow an authenticated user on the network to affect the system's performance using complicated queries due to insufficient resource pooling.

AI-Powered Analysis

AILast updated: 02/04/2026, 21:29:30 UTC

Technical Analysis

CVE-2025-2134 identifies a vulnerability in IBM Jazz Reporting Service versions 7.1 and 7.0.3, categorized under CWE-410 (Insufficient Resource Pooling). The vulnerability arises because the service does not adequately manage resource allocation when processing complex or computationally expensive queries submitted by authenticated users over the network. This insufficiency can lead to resource exhaustion, causing degraded system performance or denial-of-service (DoS) conditions. The attack vector requires an attacker to have valid network access and authentication credentials, but no additional user interaction is necessary. The vulnerability does not compromise confidentiality or integrity, as it does not allow data leakage or unauthorized modification, but it impacts availability by potentially overwhelming system resources. The CVSS 3.1 base score is 3.5, reflecting low severity due to the limited impact scope and required privileges. No patches or known exploits are currently available, indicating that the vulnerability is either newly discovered or not yet actively exploited. The issue primarily affects environments where IBM Jazz Reporting Service is used for generating reports, which may be critical for business intelligence and operational monitoring. Attackers could leverage this weakness to disrupt reporting services, causing operational delays or loss of visibility into system status.

Potential Impact

For European organizations, the primary impact of CVE-2025-2134 is on the availability of IBM Jazz Reporting Service, which may be integral to business reporting and decision-making processes. Performance degradation or denial-of-service could interrupt reporting workflows, delaying critical insights and potentially affecting compliance reporting or operational monitoring. Organizations in sectors such as finance, manufacturing, and government that rely heavily on IBM Jazz Reporting Service for analytics and reporting may experience operational inefficiencies. Although the vulnerability does not expose sensitive data or allow unauthorized changes, the disruption of reporting services can indirectly affect business continuity and incident response capabilities. The requirement for authenticated access limits the threat to insiders or compromised accounts, emphasizing the importance of strong access controls. Given the low CVSS score and lack of known exploits, the immediate risk is moderate, but organizations should remain vigilant to prevent potential escalation or exploitation in targeted attacks.

Mitigation Recommendations

To mitigate CVE-2025-2134, European organizations should implement the following specific measures: 1) Restrict access to IBM Jazz Reporting Service by enforcing the principle of least privilege, ensuring only necessary users have authenticated network access. 2) Monitor and analyze query patterns to detect unusually complex or resource-intensive queries that could indicate exploitation attempts. 3) Implement rate limiting or query complexity controls within the reporting service if supported, to prevent resource exhaustion. 4) Harden authentication mechanisms, including multi-factor authentication, to reduce the risk of credential compromise. 5) Isolate the reporting service within segmented network zones to limit exposure. 6) Engage with IBM support to obtain patches or updates as soon as they become available and apply them promptly. 7) Conduct regular performance and load testing to identify potential bottlenecks related to resource pooling. 8) Maintain comprehensive logging and alerting to detect anomalies in service performance. These steps go beyond generic advice by focusing on operational controls and proactive monitoring tailored to the nature of this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
ibm
Date Reserved
2025-03-09T18:43:29.483Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6983b6ddf9fa50a62fad2903

Added to database: 2/4/2026, 9:15:09 PM

Last enriched: 2/4/2026, 9:29:30 PM

Last updated: 2/7/2026, 2:12:13 AM

Views: 17

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