dbcve.org
Db2Application · Ibm

CVE-2024-37529

MEDIUM · 6.5 CVSS v3.1 Published 2024-08-14
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) 11.1 and 11.5 could allow an authenticated user to cause a denial of service with a specially crafted query due to improper memory allocation. IBM X-Force ID: 294295.

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 11.1 and 11.5 contain a vulnerability where an authenticated user can cause a denial of service by executing a specially crafted query. The root cause is improper memory allocation within the database engine when processing certain query patterns, leading to a crash or hang condition.

MitigationApply the IBM Db2 patch or upgrade to a fixed version as provided by IBM's security bulletin. Since this requires an authenticated session, ensure database access controls and query validation are in place as a defense-in-depth measure.

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.4, <= 11.1.4.7>= 11.5.0, <= 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 installed Db2 version
    Run 'db2level' command from a Db2 instance user, or query DB2 GET SNAPSHOT FOR DATABASE to retrieve version information
    Affected if The version number falls within 11.1.4.x (where x is 0-7) or 11.5.0.x (where x is 0-9)
  2. Confirm Db2 instance is running
    Run 'db2pd -dbp' or check if db2sysc process is active using 'ps -ef | grep db2sysc'
    Affected if The Db2 instance is online and accepting connections, making the DoS condition reachable
  3. Verify authenticated access exposure
    Review DB2 connection settings via 'db2 get dbm cfg | grep AUTHENTICATION' and check if remote connections are permitted
    Affected if Remote client authentication is enabled or the instance is accessible to users beyond local system administrators
  4. Check for crash or hang indicators
    Review Db2 diagnostic logs in the diagnostic directory (typically $DB2DIR/diaglog) for recent abend, signal, or hang entries corresponding to query processing
    Affected if Recent crash logs exist with timestamps after the suspected vulnerability introduction period

A user is affected if their installed IBM Db2 version is 11.1.4 through 11.1.4.7 or 11.5.0 through 11.5.9, and the database accepts authenticated user 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
Upgrade available Upgrade to a release after 11.5.9
Interim mitigation

Apply the IBM Db2 patch or upgrade to a fixed version as provided by IBM's security bulletin. Since this requires an authenticated session, ensure database access controls and query validation are in place as a defense-in-depth measure.

Recommended fix High confidence

Db2 11.1.4.8+ or 11.5.10+ (latest respective release)

  1. 1. Identify the current IBM Db2 version by running: db2level
  2. 2. For Db2 11.1.x users: Upgrade to version 11.1.4.8 or later (or the latest 11.1.x fix pack)
  3. 3. For Db2 11.5.x users: Upgrade to version 11.5.10 or later (or the latest 11.5.x fix pack)
  4. 4. Download the appropriate fix pack from IBM Fix Central (https://www.ibm.com/support/fixcentral)
  5. 5. Apply the fix pack following IBM's standard Db2 update procedure: stop Db2 instances, apply the update, restart instances
  6. 6. Verify the upgrade was successful by running: db2level
  7. 7. Test that the specially crafted query no longer causes the denial of service condition
Caveat Review IBM Db2 release notes for breaking changes between versions; test application queries after upgrade

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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