dbcve.org
Db2Application · Ibm

CVE-2024-49350

HIGH · 7.5 CVSS v3.1 Published 2025-05-29
Fix available
A fix is available. Upgrade to after 12.1.1 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 for Linux, UNIX and Windows (includes DB2 Connect Server) 11.1.0 through 11.1.4.7, 11.5.0 through 11.5.9 and 12.1.0 through 12.1.1 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 for Linux, UNIX and Windows is vulnerable to a denial of service attack where a specially crafted query can cause the server to crash. The vulnerability affects versions 11.1.0 through 11.1.4.7, 11.5.0 through 11.5.9, and 12.1.0 through 12.1.1.

MitigationApply the appropriate IBM Db2 patch or upgrade to a supported version outside the affected ranges. Implement query validation or rate limiting as a temporary mitigation until patching can be completed.

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.1.4.7>= 11.5, <= 11.5.9>= 12.1.0, <= 12.1.1

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. Identify installed Db2 version
    Run 'db2level' command or check DB2INSTANCE registry variable, or query 'SELECT GETVARIABLE('SYSINSTALL.*')' from a Db2 command
    Affected if Version falls within 11.1.0-11.1.4.7, 11.5.0-11.5.9, or 12.1.0-12.1.1 ranges
  2. Verify Db2 instance is running
    Check process status with 'ps -ef | grep db2sysc' or query 'db2 list active databases'
    Affected if Db2 instance is running and accepting query connections
  3. Confirm query execution is possible
    Test basic query execution with 'db2 connect to <database> && db2 SELECT 1 FROM SYSIBM.SYSDUMMY1'
    Affected if User can connect and execute SQL queries against any database on the instance

You are affected if your Db2 version matches 11.1.0 through 11.1.4.7, 11.5.0 through 11.5.9, or 12.1.0 through 12.1.1 and the database instance is operational and processing 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 12.1.1
Interim mitigation

Apply the appropriate IBM Db2 patch or upgrade to a supported version outside the affected ranges. Implement query validation or rate limiting as a temporary mitigation until patching can be completed.

Recommended fix Moderate confidence

Db2 12.1.2 or later (or 11.1.4.8+, 11.5.10+ depending on your release line)

  1. 1. Identify your current Db2 version by running 'db2level' or 'db2 SELECT * FROM SYSCAT.ENVIRONMENT_INFO'
  2. 2. Schedule a maintenance window for the upgrade (this is a production system)
  3. 3. Back up your database before applying any changes
  4. 4. Download the IBM Db2 fix pack for your version from IBM Fix Central (https://www.ibm.com/support/fixcentral/)
  5. 5. Install the appropriate fix pack: For 11.1.x install 11.1.4.8 or later; For 11.5.x install 11.5.10 or later; For 12.1.x install 12.1.2 or later
  6. 6. Apply the fix pack using the db2updv117 or db2iupdt command as appropriate for your installation
  7. 7. Restart Db2 services after applying the fix pack
  8. 8. Verify the version has been updated and the vulnerability is resolved by running 'db2level' and confirming the new version number
Caveat Review IBM Db2 fix pack release notes for any known compatibility issues or migration considerations 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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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