CVE-2025-1823: CWE-770 Allocation of Resources Without Limits or Throttling in IBM Jazz Reporting Service
IBM Jazz Reporting Service could allow an authenticated user on the host network to cause a denial of service using specially crafted SQL query that consumes excess memory resources.
AI Analysis
Technical Summary
CVE-2025-1823 is a vulnerability identified in IBM Jazz Reporting Service versions 7.0.3 and 7.1, classified under CWE-770, which involves allocation of resources without proper limits or throttling. This weakness allows an authenticated user on the host network to craft SQL queries that consume excessive memory resources, leading to a denial of service (DoS) condition by exhausting the service's memory capacity. The vulnerability does not affect confidentiality or integrity but impacts availability by potentially causing the service to become unresponsive or crash. The attack vector requires the attacker to have low-level privileges (authenticated user) and network access to the host running the Jazz Reporting Service. No user interaction is needed beyond authentication. The CVSS v3.1 score is 3.5, reflecting low severity due to the limited impact scope and required authentication. No known exploits have been reported in the wild, and no official patches have been released as of the publication date. The root cause is the absence of resource management controls within the SQL query processing component, allowing resource exhaustion through crafted queries. Organizations using affected versions should be aware of this risk, especially in environments where multiple users have authenticated access to the reporting service over the network.
Potential Impact
For European organizations, the primary impact of CVE-2025-1823 is availability disruption of IBM Jazz Reporting Service, which could affect business intelligence, reporting, and decision-making processes relying on this service. Although the vulnerability does not compromise data confidentiality or integrity, denial of service could lead to operational delays and potential financial loss, especially in sectors where timely reporting is critical such as finance, manufacturing, and public services. The requirement for authenticated network access limits the attack surface but insider threats or compromised credentials could be leveraged to exploit this flaw. Organizations with large deployments of IBM Jazz Reporting Service or those integrated into critical infrastructure may experience more significant operational impact. The absence of known exploits reduces immediate risk but does not eliminate the threat, particularly as attackers may develop exploits once the vulnerability becomes widely known.
Mitigation Recommendations
To mitigate CVE-2025-1823, European organizations should implement strict network segmentation to limit access to the Jazz Reporting Service only to trusted and necessary users. Enforce strong authentication mechanisms and monitor authentication logs for unusual access patterns. Deploy application-layer monitoring to detect abnormal SQL query behavior indicative of resource exhaustion attempts. Limit the number of concurrent queries per user where possible and implement query timeouts or resource usage thresholds if supported. Maintain an inventory of affected Jazz Reporting Service versions and plan for timely patching once IBM releases a fix. Additionally, consider deploying Web Application Firewalls (WAFs) or Intrusion Detection Systems (IDS) configured to detect and block suspicious SQL query patterns. Educate administrators and users about the risks of credential compromise and enforce least privilege principles to reduce the risk of exploitation.
Affected Countries
Germany, United Kingdom, France, Netherlands, Italy, Spain, Sweden
CVE-2025-1823: CWE-770 Allocation of Resources Without Limits or Throttling in IBM Jazz Reporting Service
Description
IBM Jazz Reporting Service could allow an authenticated user on the host network to cause a denial of service using specially crafted SQL query that consumes excess memory resources.
AI-Powered Analysis
Technical Analysis
CVE-2025-1823 is a vulnerability identified in IBM Jazz Reporting Service versions 7.0.3 and 7.1, classified under CWE-770, which involves allocation of resources without proper limits or throttling. This weakness allows an authenticated user on the host network to craft SQL queries that consume excessive memory resources, leading to a denial of service (DoS) condition by exhausting the service's memory capacity. The vulnerability does not affect confidentiality or integrity but impacts availability by potentially causing the service to become unresponsive or crash. The attack vector requires the attacker to have low-level privileges (authenticated user) and network access to the host running the Jazz Reporting Service. No user interaction is needed beyond authentication. The CVSS v3.1 score is 3.5, reflecting low severity due to the limited impact scope and required authentication. No known exploits have been reported in the wild, and no official patches have been released as of the publication date. The root cause is the absence of resource management controls within the SQL query processing component, allowing resource exhaustion through crafted queries. Organizations using affected versions should be aware of this risk, especially in environments where multiple users have authenticated access to the reporting service over the network.
Potential Impact
For European organizations, the primary impact of CVE-2025-1823 is availability disruption of IBM Jazz Reporting Service, which could affect business intelligence, reporting, and decision-making processes relying on this service. Although the vulnerability does not compromise data confidentiality or integrity, denial of service could lead to operational delays and potential financial loss, especially in sectors where timely reporting is critical such as finance, manufacturing, and public services. The requirement for authenticated network access limits the attack surface but insider threats or compromised credentials could be leveraged to exploit this flaw. Organizations with large deployments of IBM Jazz Reporting Service or those integrated into critical infrastructure may experience more significant operational impact. The absence of known exploits reduces immediate risk but does not eliminate the threat, particularly as attackers may develop exploits once the vulnerability becomes widely known.
Mitigation Recommendations
To mitigate CVE-2025-1823, European organizations should implement strict network segmentation to limit access to the Jazz Reporting Service only to trusted and necessary users. Enforce strong authentication mechanisms and monitor authentication logs for unusual access patterns. Deploy application-layer monitoring to detect abnormal SQL query behavior indicative of resource exhaustion attempts. Limit the number of concurrent queries per user where possible and implement query timeouts or resource usage thresholds if supported. Maintain an inventory of affected Jazz Reporting Service versions and plan for timely patching once IBM releases a fix. Additionally, consider deploying Web Application Firewalls (WAFs) or Intrusion Detection Systems (IDS) configured to detect and block suspicious SQL query patterns. Educate administrators and users about the risks of credential compromise and enforce least privilege principles to reduce the risk of exploitation.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- ibm
- Date Reserved
- 2025-03-01T14:39:33.891Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6983b6ddf9fa50a62fad28fd
Added to database: 2/4/2026, 9:15:09 PM
Last enriched: 2/4/2026, 9:30:02 PM
Last updated: 2/7/2026, 2:19:07 AM
Views: 22
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2071: Buffer Overflow in UTT 进取 520W
HighCVE-2026-25762: CWE-400: Uncontrolled Resource Consumption in adonisjs core
HighCVE-2026-25754: CWE-1321: Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') in adonisjs core
HighCVE-2026-25644: CWE-295: Improper Certificate Validation in datahub-project datahub
HighCVE-2026-25804: CWE-287: Improper Authentication in antrea-io antrea
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
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.