CVE-2024-31880

5.3 MEDIUM

📋 TL;DR

IBM Db2 databases on Linux, UNIX, and Windows can crash when authenticated users execute specially crafted SQL statements, causing denial of service. This affects Db2 versions 10.5, 11.1, and 11.5 under specific configurations.

💻 Affected Systems

Products:
  • IBM Db2 for Linux, UNIX and Windows
  • IBM Db2 Connect Server
Versions: 10.5, 11.1, 11.5
Operating Systems: Linux, UNIX, Windows
Default Config Vulnerable: ✅ No
Notes: Only vulnerable under specific configurations mentioned in IBM advisory; not all installations are affected.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete database unavailability affecting all applications and users relying on the Db2 instance, requiring restart and potentially causing data corruption or service disruption.

🟠

Likely Case

Temporary service interruption affecting specific database connections or applications until the Db2 service is restarted.

🟢

If Mitigated

Minimal impact with proper access controls limiting authenticated users and monitoring preventing malicious SQL execution.

🌐 Internet-Facing: MEDIUM - Internet-facing Db2 instances are at risk if exposed with authenticated user access, though exploitation requires specific SQL knowledge.
🏢 Internal Only: MEDIUM - Internal databases remain vulnerable to authenticated users, including legitimate users with malicious intent or compromised credentials.

🎯 Exploit Status

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

Requires authenticated database access and knowledge of specific SQL statement construction; no public exploit code available.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Apply fixes per IBM advisory: 10.5 FP11, 11.1.4 FP7, 11.5.9 FP2 or later

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

Restart Required: Yes

Instructions:

1. Review IBM advisory for specific fix versions. 2. Apply appropriate fix pack for your Db2 version. 3. Restart Db2 instance to apply changes.

🔧 Temporary Workarounds

Restrict SQL Execution

all

Limit authenticated users' ability to execute arbitrary SQL statements through application controls or database permissions.

-- Review and tighten database user privileges
-- Implement application-level SQL validation

🧯 If You Can't Patch

  • Implement strict access controls to limit authenticated database users to only necessary privileges.
  • Monitor database logs for unusual SQL statement patterns and implement alerting for potential exploitation attempts.

🔍 How to Verify

Check if Vulnerable:

Check Db2 version and compare against affected versions in IBM advisory; review configuration against specific vulnerable conditions.

Check Version:

db2level (on Db2 server)

Verify Fix Applied:

Verify Db2 version after patch installation matches or exceeds fixed versions listed in IBM advisory.

📡 Detection & Monitoring

Log Indicators:

  • Db2 crash logs
  • Unexpected service restarts
  • Error logs containing SQL statement failures

Network Indicators:

  • Sudden drop in database connections
  • Application errors indicating database unavailability

SIEM Query:

source="db2" AND (event="crash" OR event="restart")

🔗 References

📤 Share & Export