CVE-2025-2534

5.3 MEDIUM

📋 TL;DR

IBM Db2 databases running vulnerable versions can be crashed by a specially crafted query, causing denial of service. This affects Db2 11.1.0-11.1.4.7, 11.5.0-11.5.9, and 12.1.0-12.1.3 on Linux, UNIX, and Windows systems, including Db2 Connect Server.

💻 Affected Systems

Products:
  • IBM Db2 Database Server
  • IBM Db2 Connect Server
Versions: 11.1.0 through 11.1.4.7, 11.5.0 through 11.5.9, 12.1.0 through 12.1.3
Operating Systems: Linux, UNIX, Windows
Default Config Vulnerable: ⚠️ Yes
Notes: All configurations within affected versions are vulnerable if the database accepts queries.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database unavailability requiring restart, potentially disrupting critical business operations and causing data loss if transactions are interrupted.

🟠

Likely Case

Temporary service disruption until database restart, affecting applications dependent on the database.

🟢

If Mitigated

Minimal impact with proper network segmentation and query filtering preventing malicious queries from reaching the database.

🌐 Internet-Facing: MEDIUM - Internet-facing Db2 instances could be targeted by automated scanning tools, but exploitation requires specific query crafting.
🏢 Internal Only: LOW - Requires authenticated database access or network path to database port, reducing exposure to trusted users only.

🎯 Exploit Status

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

Exploitation requires ability to submit queries to the database, typically requiring some level of database access or application compromise.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply fixes from IBM: 11.1.4.7a, 11.5.9a, 12.1.3a or later

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

Restart Required: Yes

Instructions:

1. Download appropriate fix pack from IBM Fix Central. 2. Apply fix pack following IBM Db2 installation procedures. 3. Restart Db2 instance and verify successful update.

🔧 Temporary Workarounds

Network Access Control

all

Restrict database access to only trusted applications and users using firewall rules.

Query Filtering

all

Implement application-layer validation to filter or sanitize database queries before submission.

🧯 If You Can't Patch

  • Implement strict network segmentation to limit database access to only necessary applications
  • Monitor database logs for unusual query patterns and implement rate limiting on database connections

🔍 How to Verify

Check if Vulnerable:

Check Db2 version using 'db2level' command and compare against affected version ranges.

Check Version:

db2level | grep "Product installed"

Verify Fix Applied:

Verify version after patching shows patched version (e.g., 11.5.9a) and test database stability with normal queries.

📡 Detection & Monitoring

Log Indicators:

  • Database crash logs
  • Unexpected termination of db2sysc process
  • Connection failures following unusual queries

Network Indicators:

  • Multiple failed connection attempts to database port
  • Unusual query patterns from single source

SIEM Query:

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

🔗 References

📤 Share & Export