dbcve.org
Db2Application · Ibm

CVE-2024-25046

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.1 and 11.5 is vulnerable to a denial of service by an authenticated user using a specially crafted query. IBM X-Force ID: 282953.

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 11.1 and 11.5 are vulnerable to a denial of service attack. An authenticated database user can trigger the vulnerability by executing a specially crafted query that causes the Db2 server to become unresponsive or crash.

MitigationRestrict database user permissions to only those necessary and apply IBM Db2 patches as they become available. Monitor for unusual query patterns from 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:= 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. Check IBM Db2 version
    Run 'db2level' command or query SELECT * FROM SYSIBM.SYSVERSION to determine the installed Db2 version.
    Affected if The installed version is 11.1 or 11.5 exactly.
  2. Verify authenticated database users exist
    Query SYSIBMADM.SESSIONS or use 'db2 list users' to see which database users have authentication credentials configured.
    Affected if Any authenticated database user account exists in the Db2 instance.
  3. Check user permissions for SQL execution
    Query SYSIBMADM.SESSION_AUTHORIZATIONS or run 'db2 get authorizations' to see which users have privileges to execute SQL queries.
    Affected if Any user has CONNECT or SQLEXEC authority granted to them.
  4. Review database manager configuration for remote access
    Examine DBM CFG settings, specifically AUTHENTICATION, and check if TCP/IP listener is enabled via 'db2 get dbm cfg' or 'db2diag -aw'.
    Affected if Remote client connections are permitted (AUTHENTICATION is not SERVER_ENCRYPT and TCP/IP is enabled).

Your environment is affected if you are running IBM Db2 version 11.1 or 11.5 and have any authenticated database users with the ability to execute SQL 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

Restrict database user permissions to only those necessary and apply IBM Db2 patches as they become available. Monitor for unusual query patterns from authenticated users.

Recommended fix Moderate confidence

Db2 11.1 and 11.5 latest security fix pack (check IBM Fix Central for specific APAR number)

  1. 1. Identify your current Db2 version by running 'db2level' command
  2. 2. Visit IBM Fix Central (https://www.ibm.com/support/fixcentral/) and search for Db2 11.1 or 11.5
  3. 3. Apply the latest security fix or fix pack that addresses CVE-2024-25046
  4. 4. Test the fix in a non-production environment before deploying to production
  5. 5. Backup your database before applying any updates
  6. 6. Apply the fix during a planned maintenance window
  7. 7. Verify the fix is applied by running 'db2level' again and confirming the version includes the security patch
Caveat Test application compatibility with new fix pack in non-production 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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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