CVE-2025-36407

6.5 MEDIUM

📋 TL;DR

This vulnerability in IBM Db2 allows a local user to cause a denial of service by exploiting improper neutralization of special elements in data query logic. It affects Db2 versions 11.5.0-11.5.9 and 12.1.0-12.1.3 on Linux, UNIX, and Windows systems. The attacker must have local access to the database server.

💻 Affected Systems

Products:
  • IBM Db2 for Linux, UNIX and Windows
  • IBM Db2 Connect Server
Versions: 11.5.0 - 11.5.9 and 12.1.0 - 12.1.3
Operating Systems: Linux, UNIX, Windows
Default Config Vulnerable: ⚠️ Yes
Notes: All default configurations of affected versions are vulnerable. The attacker must have local access to the database server.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database service disruption affecting all applications and users relying on the Db2 instance, potentially requiring system restart.

🟠

Likely Case

Temporary service degradation or crash of specific database processes, affecting availability for some users until service is restored.

🟢

If Mitigated

Minimal impact with proper access controls limiting local user privileges and monitoring for abnormal query patterns.

🌐 Internet-Facing: LOW - Requires local user access, not exploitable remotely over network.
🏢 Internal Only: MEDIUM - Local users with database access could disrupt critical database services affecting business operations.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: UNKNOWN
Unauthenticated Exploit: ✅ No
Complexity: LOW

Exploitation requires local access and database user privileges. The CWE-1284 suggests improper input validation in query processing.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply fixes from IBM Security Bulletin: 11.5.9.0 Fix Pack 10 or later, 12.1.3.0 Fix Pack 4 or later

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

Restart Required: Yes

Instructions:

1. Download appropriate fix pack from IBM Fix Central. 2. Stop all Db2 services. 3. Apply fix pack following IBM installation guide. 4. Restart Db2 services. 5. Verify version update.

🔧 Temporary Workarounds

Restrict Local User Access

all

Limit local user accounts with database access to only trusted administrators

# Review and remove unnecessary local database users
# Use OS-level access controls to restrict who can run database commands

Implement Query Monitoring

all

Monitor for abnormal query patterns that could indicate exploitation attempts

# Enable Db2 audit logging for query execution
# Set up alerts for unusual query patterns or frequency

🧯 If You Can't Patch

  • Implement strict least-privilege access controls for local database users
  • Deploy additional monitoring for database service availability and restart procedures

🔍 How to Verify

Check if Vulnerable:

Check Db2 version using 'db2level' command and compare against affected versions 11.5.0-11.5.9 or 12.1.0-12.1.3

Check Version:

db2level | grep "Product installed"

Verify Fix Applied:

Run 'db2level' command and verify version is 11.5.9.0 Fix Pack 10 or later, or 12.1.3.0 Fix Pack 4 or later

📡 Detection & Monitoring

Log Indicators:

  • Database service crashes or restarts
  • Abnormal query patterns in Db2 diagnostic logs
  • Error messages related to query processing failures

Network Indicators:

  • Sudden loss of database connectivity from applications
  • Increased failed connection attempts to database

SIEM Query:

source="db2*" AND ("crash" OR "restart" OR "abnormal query" OR "service terminated")

🔗 References

📤 Share & Export