dbcve.org
Db2Application · Ibm

CVE-2024-47118

HIGH · 7.5 CVSS v3.1 Published 2025-11-07
Fix available
A fix is available. Upgrade to after 12.1.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 10.5.0 through 10.5.11, 11.1.0 through 11.1.4.7, 11.5.0 through 11.5.9, and 12.1.0 through 12.1.3 for Linux, UNIX and Windows (includes Db2 Connect Server) 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 · moderate confidence

IBM Db2 is vulnerable to a denial of service attack where a specially crafted query can cause the database server to crash. The vulnerability affects multiple versions across the 10.5, 11.1, 11.5, and 12.1 release trains on Linux, UNIX, and Windows platforms, including Db2 Connect Server.

MitigationApply the IBM-provided patch or upgrade to a fixed version of Db2 as specified in IBM's security bulletin. Test the patch in a non-production environment before deploying to production.

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.0, <= 10.5.0.11>= 11.1.0, <= 11.1.4.7>= 11.5.0, <= 11.5.9>= 12.1.0, <= 12.1.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 installed Db2 version
    Run 'db2level' command from a Db2 instance owner or query 'SELECT * FROM SYSIBMADM.ENV_GET_INST_INFO' via db2 CLI
    Affected if The returned version falls within these ranges: 10.5.0.0 to 10.5.0.11, 11.1.0 to 11.1.4.7, 11.5.0 to 11.5.9, or 12.1.0 to 12.1.3
  2. Confirm Db2 release train
    Verify the major version number (first two digits before decimal) from the version output
    Affected if The major version is 10.5, 11.1, 11.5, or 12.1 within the affected version ranges above
  3. Verify platform
    Check the platform where Db2 is installed - this vulnerability affects Linux, UNIX, and Windows
    Affected if Db2 is running on Linux, UNIX, or Windows platforms (vulnerable), not on other platforms like z/OS or iSeries which are not listed as affected
  4. Identify if Db2 Connect Server is in use
    Check if Db2 Connect Server is installed by running 'db2pd -inst' or reviewing installed Db2 products via 'db2ls'
    Affected if Db2 Connect Server is installed and running an affected version

You are affected if your installed Db2 version falls within any of the affected ranges (10.5.0.0-10.5.0.11, 11.1.0-11.1.4.7, 11.5.0-11.5.9, 12.1.0-12.1.3) on Linux, UNIX, or Windows, and a specially crafted query is executed against the database.

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 12.1.3
Interim mitigation

Apply the IBM-provided patch or upgrade to a fixed version of Db2 as specified in IBM's security bulletin. Test the patch in a non-production environment before deploying to production.

Recommended fix Moderate confidence

IBM Db2 10.5.0.12+, 11.1.4.8+, 11.5.10+, or 12.1.4+ (specific fix pack levels per IBM's remediation)

  1. Check your current IBM Db2 version using 'db2level' command
  2. Identify your major version (10.5, 11.1, 11.5, or 12.1) and plan upgrade accordingly
  3. For Db2 10.5.x users: Upgrade to version 10.5.0.11 or later (specifically a version beyond 10.5.0.11)
  4. For Db2 11.1.x users: Upgrade to version 11.1.4.7 or later (specifically a version beyond 11.1.4.7)
  5. For Db2 11.5.x users: Upgrade to version 11.5.9 or later (specifically a version beyond 11.5.9)
  6. For Db2 12.1.x users: Upgrade to version 12.1.3 or later (specifically a version beyond 12.1.3)
  7. After upgrade, verify the fix by testing with the crafted query pattern that previously caused the crash
  8. Apply the latest Db2 Fix Pack for your respective version from IBM Fix Central
Caveat Review IBM Db2 Fix Pack release notes for any compatibility changes or deprecated features before upgrading

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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