dbcve.org
Db2Application · Ibm

CVE-2024-54178

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-22
Fix available
A fix is available. Upgrade to 5.4 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 on Cloud Pak for Data and Db2 Warehouse on Cloud Pak for Data versions 4.8,5.0,5.1,5.2,5.3 could allow an authenticated user to cause a denial of service when creating new databases due to improper allocation of resources.

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 on Cloud Pak for Data and Db2 Warehouse versions 4.8 through 5.3 contain a denial of service vulnerability where an authenticated user can exhaust server resources by creating new databases, due to improper resource allocation during the database creation process.

MitigationApply IBM's available patches for this vulnerability or restrict database creation privileges to trusted administrators until the fix can be deployed.

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:>= 4.8, < 5.4
Db2 WarehouseApplication
Affected:>= 4.8, < 5.4

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 the installed IBM Db2 product and version
    Query the Db2 system catalog or use the db2pd utility: `db2pd -version` or check the Cloud Pak for Data console for the Db2 component version
    Affected if The installed version is between 4.8 and 5.3 inclusive (4.8 <= version < 5.4)
  2. Confirm the product type is affected
    Verify the product is either IBM Db2 on Cloud Pak for Data or IBM Db2 Warehouse by checking the product name in the installation manifest or console
    Affected if The product is Db2 on Cloud Pak for Data or Db2 Warehouse within the vulnerable version range
  3. Check for database creation privileges
    Query user privileges using: `db2 select grantor, grantee, privilege from syscat.dbauth where grantee = '<username>'` or check if the user has CREATEDB authority
    Affected if The user has CREATEDB privilege or DBADM authority and can create new databases
  4. Look for resource exhaustion indicators
    Monitor system resources during database creation attempts: check CPU, memory, and disk I/O usage. Review Db2 diagnostic logs (db2diag.log) for errors related to resource allocation failures
    Affected if Database creation operations consume disproportionate resources or fail with resource allocation errors, indicating the vulnerability is triggerable

A user is affected if they are running IBM Db2 on Cloud Pak for Data or Db2 Warehouse versions 4.8 through 5.3 and have database creation privileges that allow triggering the resource exhaustion condition.

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 5.4 or later
Fixed in 5.4
Interim mitigation

Apply IBM's available patches for this vulnerability or restrict database creation privileges to trusted administrators until the fix can be deployed.

Recommended fix Moderate confidence

IBM Cloud Pak for Data version 5.4 or later (which includes Db2 and Db2 Warehouse 5.4)

  1. 1. Back up all critical data and configurations in the current Db2 or Db2 Warehouse deployment
  2. 2. Review IBM Cloud Pak for Data upgrade documentation for your specific version
  3. 3. Plan a maintenance window suitable for production systems
  4. 4. Test the upgrade in a non-production environment first
  5. 5. Upgrade IBM Cloud Pak for Data to version 5.4 or later using IBM's recommended upgrade procedure
  6. 6. Verify that Db2 and Db2 Warehouse services are running correctly after upgrade
  7. 7. Test database creation functionality to confirm the vulnerability is remediated
  8. 8. Monitor system resources during database creation to verify proper resource allocation
Caveat Review IBM Cloud Pak for Data 5.4 release notes for any compatibility changes or deprecated features before upgrading production systems

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

Fix this in Db2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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