dbcve.org
Db2Application · Ibm

CVE-2024-22360

MEDIUM · 6.5 CVSS v3.1 Published 2024-04-03
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) 11.5 is vulnerable to a denial of service with a specially crafted query on certain columnar tables. IBM X-Force ID: 280905.

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 11.5 for Linux, UNIX, and Windows contains a denial of service vulnerability where specially crafted queries targeting columnar tables can cause the database service to become unresponsive or crash. Columnar tables are optimized for analytical workloads and represent a specific storage format within Db2.

MitigationApply the appropriate IBM Db2 security patch when available. Until a patch is applied, consider restricting query privileges on columnar tables to trusted users and monitoring for anomalous query patterns.

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:= 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. Identify IBM Db2 installation and version
    Run 'db2level' command or query 'SELECT GET_VARCHAR_FOR_BIT_DATA(PACKAGE_VERSION) AS VERSION FROM SYSIBM.SYSDUMMY1' to obtain the exact Db2 version installed.
    Affected if The installed version is exactly 11.5 (any subversion of 11.5).
  2. Check for columnar tables in the database
    Query the system catalog using: SELECT TABNAME, TABSCHEMA FROM SYSCAT.TABLES WHERE TABLE_TYPE='T' AND COLUMN_ORGANIZATION = 'COLUMN' OR (SELECT COUNT(*) FROM SYSCAT.COLUMNS C WHERE C.TABSCHEMA = T.TABSCHEMA AND C.TABNAME = T.TABNAME AND C.COLUMN_ORG = 'C') > 0. Alternatively, check SYSCAT.TABLES for COLUMN_ORGANIZATION = 'COLUMN'.
    Affected if Any columnar tables exist in the database, creating a potential attack surface.
  3. Verify columnar table functionality is enabled
    Check Db2 configuration for columnar support using 'GET DATABASE CONFIGURATION' and look for columnar-related settings, or verify the storage group associated with columnar tables exists using 'SELECT * FROM SYSCAT.STORAGEGROUPS' where STMTools indicates columnar capability.
    Affected if Columnar storage groups and columnar table support are active in the Db2 instance.

If IBM Db2 version 11.5 is installed and columnar tables exist in the database, the environment is potentially affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the appropriate IBM Db2 security patch when available. Until a patch is applied, consider restricting query privileges on columnar tables to trusted users and monitoring for anomalous query patterns.

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-22360 — 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-22360 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