dbcve.org
Db2Application · Ibm

CVE-2024-41762

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-07
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 as the server may crash under certain conditions with a specially crafted query.

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 10.5, 11.1, and 11.5 on Linux, UNIX, and Windows is vulnerable to denial of service. A specially crafted SQL query can cause the database server to crash, rendering it unavailable until restarted.

MitigationApply the IBM Db2 patch or upgrade to a patched version. Implement query timeout limits or resource governor controls as a defensive measure until the vendor patch is applied.

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, <= 10.5.11>= 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 IBM Db2 version
    Run the command 'db2level' from a Db2 instance owner account, or query DB2 with: 'SELECT GET_VARCHAR_FOR_BIT_DATA(SERVICE_LEVEL) AS VERSION FROM SYSIBM.SYSDUMMY1'
    Affected if Version falls within 10.5.0-10.5.11, 11.1.4-11.1.4.7, or 11.5.0-11.5.9
  2. Confirm Db2 edition and platform
    Verify the installation is on Linux, UNIX, or Windows using 'db2level' output or checking the installation directory
    Affected if Running on Linux, UNIX, or Windows platforms with affected versions
  3. Assess SQL execution exposure
    Review which database users or applications have permission to execute arbitrary SQL queries against the database
    Affected if Untrusted or low-privilege users can submit custom SQL queries to the database

You are affected if your IBM Db2 version is 10.5.0-10.5.11, 11.1.4-11.1.4.7, or 11.5.0-11.5.9 on Linux/UNIX/Windows and untrusted users can 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.

From vendor data
Upgrade available Upgrade to a release after 11.5.9
Interim mitigation

Apply the IBM Db2 patch or upgrade to a patched version. Implement query timeout limits or resource governor controls as a defensive measure until the vendor patch is applied.

Fix this in Db2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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