dbcve.org
Db2Application · Ibm

CVE-2024-31880

MEDIUM · 6.5 CVSS v3.1 Published 2024-10-23
Fix available
A fix is available. Upgrade to after 11.5.9 or later.
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, under specific configurations, as the server may crash when using a specially crafted SQL statement by an authenticated user.

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 · moderate confidence

IBM Db2 versions 10.5, 11.1, and 11.5 on Linux, UNIX, and Windows is vulnerable to a denial of service attack where an authenticated user can cause the database server to crash using a specially crafted SQL statement under specific configurations.

MitigationApply the IBM Db2 fix/patch when available, and review user permissions to ensure only necessary SQL privileges are granted to authenticated users.

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.0.0, <= 10.5.11>= 11.1.4, <= 11.1.4.7>= 11.5, <= 11.5.9

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. Identify Db2 version
    Run 'db2level' command from a Db2 instance owner or query 'SELECT * FROM SYSIBMADM.DBMCFG' where name='service_level'
    Affected if The installed version falls within 10.5.0.0-10.5.11, 11.1.4-11.1.4.7, or 11.5.0-11.5.9
  2. Verify Db2 authentication is enabled
    Query 'SELECT name, value FROM SYSIBMADM.DBMCFG' and check that AUTHENTICATION is set to a valid mode (not NONE)
    Affected if Authentication is disabled (AUTHENTICATION=NONE), allowing unauthenticated access to the exploit vector
  3. Review user SQL privileges
    Query 'SELECT GRANTEE, CREATETAB, BINDADD, CONNECT, DBADM FROM SYSCAT.DBAUTH' to identify users with elevated privileges
    Affected if Authenticated users have broad SQL privileges (CONNECT, CREATETAB, DBADM) that could allow executing the specially crafted SQL statement
  4. Check for abnormal connection activity
    Review Db2 diagnostic logs (db2diag.log) for recent instance crashes or unexpected terminations matching the timeframe of the CVE
    Affected if Recent crashes or abnormal terminations are logged with SQL error codes indicating the vulnerability may have been exploited

You are affected if your installed Db2 version is within the listed ranges AND authenticated users have SQL privileges that could execute the specially crafted statement.

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
Upgrade available Upgrade to a release after 11.5.9
Interim mitigation

Apply the IBM Db2 fix/patch when available, and review user permissions to ensure only necessary SQL privileges are granted to authenticated users.

Recommended fix High confidence

Db2 10.5.12+, Db2 11.1.4.8+, or Db2 11.5.10+ (select the major version matching your current installation)

  1. 1. Identify your current Db2 version by running: db2level (for server) or checking DB2VERSION registry variable
  2. 2. Determine your current fix pack level: db2pd -version (or from db2diag.log)
  3. 3. For Db2 10.5.x: Upgrade to version 10.5.12 or later (fix pack 12)
  4. 4. For Db2 11.1.4.x: Upgrade to version 11.1.4.8 or later (fix pack 8 for version 11.1)
  5. 5. For Db2 11.5.x: Upgrade to version 11.5.10 or later (fix pack 10)
  6. 6. Download the appropriate fix pack from IBM Fix Central (https://www.ibm.com/support/fixcentral/)
  7. 7. Stop all Db2 instances before applying the fix pack: db2stop force
  8. 8. Apply the fix pack as root or db2admin using the installer appropriate for your platform
Caveat Fix packs are generally cumulative and non-disruptive when applied within the same major version; however, always review IBM's fix pack readme for any configuration or compatibility notices before applying

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

Fix this in Db2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-31880 — 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-31880 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