CVE-2025-25020

6.5 MEDIUM

📋 TL;DR

This vulnerability in IBM QRadar Suite Software and IBM Cloud Pak for Security allows authenticated users to cause denial of service by sending malformed API requests. The improper input validation can crash services, affecting organizations running vulnerable versions of these security monitoring platforms.

💻 Affected Systems

Products:
  • IBM QRadar Suite Software
  • IBM Cloud Pak for Security
Versions: QRadar Suite 1.10.12.0 through 1.11.2.0; Cloud Pak for Security 1.10.0.0 through 1.10.11.0
Operating Systems: Linux-based platforms running IBM security software
Default Config Vulnerable: ⚠️ Yes
Notes: All deployments with affected versions are vulnerable if API access is enabled.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Critical security monitoring services become unavailable, potentially blinding security teams to active threats during an attack.

🟠

Likely Case

Partial service disruption affecting specific API endpoints, reducing functionality of the security platform.

🟢

If Mitigated

Minimal impact with proper API access controls and rate limiting in place.

🌐 Internet-Facing: MEDIUM - Requires authentication but could be exploited if APIs are exposed externally.
🏢 Internal Only: HIGH - Authenticated internal users (including compromised accounts) can exploit this vulnerability.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW - Simple API request manipulation required.

Exploitation requires valid authentication credentials to access the vulnerable API endpoints.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: QRadar Suite 1.11.3.0 or later; Cloud Pak for Security 1.10.12.0 or later

Vendor Advisory: https://www.ibm.com/support/pages/node/7235432

Restart Required: Yes

Instructions:

1. Download the latest patch from IBM Fix Central. 2. Backup current configuration. 3. Apply the patch following IBM's upgrade documentation. 4. Restart affected services.

🔧 Temporary Workarounds

Restrict API Access

all

Limit API access to trusted IP addresses and users only.

Configure firewall rules to restrict access to API endpoints
Implement API gateway with rate limiting

Enhanced Monitoring

all

Monitor for unusual API request patterns that could indicate exploitation attempts.

Set up alerts for high-volume API requests
Monitor for service restarts

🧯 If You Can't Patch

  • Implement strict API access controls and authentication requirements
  • Deploy Web Application Firewall (WAF) with input validation rules

🔍 How to Verify

Check if Vulnerable:

Check the installed version via the IBM QRadar/Cloud Pak administration console or command line.

Check Version:

For QRadar: /opt/qradar/bin/qradar_versions.sh; For Cloud Pak: oc get pods -n cp4s

Verify Fix Applied:

Verify the version is updated to patched versions and test API functionality.

📡 Detection & Monitoring

Log Indicators:

  • Unusual API request patterns
  • Service restart logs
  • Error messages related to API input validation

Network Indicators:

  • High volume of malformed API requests
  • Unusual traffic to API endpoints

SIEM Query:

source="qradar" AND ("API error" OR "service restart" OR "denial of service")

🔗 References

📤 Share & Export