dbcve.org
Db2Application · Ibm

CVE-2024-31881

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IBM Db2 for Linux, UNIX and Windows (includes Db2 Connect Server) 10.5, 11.1, and 11.5 is vulnerable to a denial of service as the server may crash when using a specially crafted query on certain columnar tables by an authenticated user. IBM X-Force ID: 287613.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

IBM Db2 versions 10.5, 11.1, and 11.5 are vulnerable to a denial of service where an authenticated user can cause the database server to crash by executing a specially crafted query targeting certain columnar tables. The vulnerability requires valid database credentials but can be exploited remotely by any authenticated user.

MitigationApply IBM's vendor patches for this vulnerability (contact IBM support or visit IBM Fix Central for Db2 10.5, 11.1, and 11.5). Until patches are applied, limit database access to trusted users and monitor for unusual query patterns against columnar tables.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Db2Application
Affected:= 10.5= 11.1= 11.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Db2 version
    Run the command `db2level` or query `SELECT * FROM SYSIBMADM.DBMCFG WHERE NAME = 'db2_version'` to retrieve the exact Db2 version number.
    Affected if The installed version is exactly 10.5, 11.1, or 11.5.
  2. Identify if columnar tables exist
    Query the system catalog using `SELECT TABSCHEMA, TABNAME FROM SYSCAT.TABLES WHERE TYPE = 'T' AND ORGANIZE BY = 'COLUMN'` to list any columnar tables in the database.
    Affected if Columnar tables exist in the database (the vulnerability targets columnar tables specifically).
  3. Review database logs for crash events
    Examine the db2diag.log file (located in the diagnostic data directory) for recent entries indicating database crashes, abnormal termination, or SQL errors, particularly those occurring during SELECT or query operations.
    Affected if Recent crash events or abnormal terminations are logged, especially involving queries on columnar tables.
  4. Check remote access configuration
    Review Db2 configuration settings using `db2 get dbm cfg` and check the AUTHENTICATION parameter, and verify whether remote connections are enabled and accessible to untrusted users.
    Affected if Remote database connections are enabled and the database is accessible to users who are not fully trusted.

If the installed Db2 version is 10.5, 11.1, or 11.5 and columnar tables are in use, the environment is potentially affected; confirm by reviewing logs for crash events related to queries.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM's vendor patches for this vulnerability (contact IBM support or visit IBM Fix Central for Db2 10.5, 11.1, and 11.5). Until patches are applied, limit database access to trusted users and monitor for unusual query patterns against columnar tables.

Recommended fix Moderate confidence

Db2 11.5 Fix Pack 11.5.9 or later; Db2 11.1 Fix Pack 11.1.4.4 or later; Db2 10.5 users should migrate to Db2 11.5

  1. 1. Identify your current Db2 version by running: db2level
  2. 2. For Db2 11.5: Apply Db2 Fix Pack 11.5.9 or later from IBM Fix Central (https://www.ibm.com/support/fixcentral/)
  3. 3. For Db2 11.1: Apply Db2 Fix Pack 11.1.4.4 or later from IBM Fix Central
  4. 4. For Db2 10.5: IBM 10.5 reached End of Support; migrate to Db2 11.5 by installing a fresh instance and migrating data using DB2MOVE or backup/restore
  5. 5. After applying fix pack, stop all Db2 instances: db2stop force
  6. 6. Install the fix pack following IBM's installation guide for your platform
  7. 7. Start Db2 instances: db2start
  8. 8. Verify the fix by running: db2level to confirm the updated version
Caveat Db2 10.5 is End of Support - requires full migration rather than in-place upgrade; test application queries against columnar tables before deploying to production

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Db2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31881 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-31881 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data