dbcve.org
Db2Application · Ibm

CVE-2022-22389

MEDIUM · 6.5 CVSS v3.1 Published 2022-06-24
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 9.7, 10.1, 10.5, 11.1, and 11.5 is vulnerable to a denial of service as the server may terminate abnormally when executing specially crafted SQL statements by an authenticated user. IBM X-Force ID: 2219740.

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 9.7 through 11.5 on Linux, UNIX, and Windows contains a denial of service vulnerability where an authenticated user can cause the database server to terminate abnormally by executing specially crafted SQL statements. The vulnerability requires valid database credentials to exploit.

MitigationApply the appropriate IBM Db2 fix pack or patch for versions 9.7, 10.1, 10.5, 11.1, or 11.5 as provided by IBM. Prior to production deployment, validate the patch in a non-production environment.

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:= 9.7= 10.1= 10.5= 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 if IBM Db2 is installed
    Run the command 'db2level' or 'db2start' from a command prompt, or check for Db2 installation directories such as /opt/ibm/db2 or C:\Program Files\IBM\DB2 on Windows
    Affected if Db2 is installed on the system
  2. Determine the installed Db2 version
    Execute 'db2level' and locate the version number in the output. The version will appear as a release like Version 9.7, 10.1, 10.5, 11.1, or 11.5
    Affected if The output shows version 9.7, 10.1, 10.5, 11.1, or 11.5
  3. Confirm the full version string
    Run 'db2 select * from sysibm.sysversions' or check the db2diag.log for detailed version information including the fix pack level
    Affected if The version falls within the 9.7 through 11.5 release family including fix packs
  4. Verify database authentication is enabled
    Check if database connections are allowed by reviewing dbm cfg configuration parameters like 'AUTHENTICATION' or by attempting to connect with valid credentials using 'db2 connect to <database> user <user>'
    Affected if The database accepts authenticated connections from users who can execute SQL statements
  5. Check if SQL execution is permitted
    As an authenticated user, run 'db2 -t' to enter interactive mode and verify SQL statements can be executed, or check user privileges with 'db2 get authorizations'
    Affected if Authenticated users have the ability to execute arbitrary SQL statements against the database

The environment is affected if IBM Db2 version 9.7, 10.1, 10.5, 11.1, or 11.5 is installed and the database accepts authenticated SQL connections, since an authenticated user can execute specially crafted SQL to cause denial of service.

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

Apply the appropriate IBM Db2 fix pack or patch for versions 9.7, 10.1, 10.5, 11.1, or 11.5 as provided by IBM. Prior to production deployment, validate the patch in a non-production environment.

Recommended fix Moderate confidence

IBM Db2 11.5 (latest fix pack)

  1. 1. Identify the current Db2 version using 'db2level' command or 'SELECT VERSION(*) FROM SYSIBM.SYSDUMMY1'
  2. 2. Plan maintenance window for the upgrade as it requires database downtime
  3. 3. Back up all databases using 'BACKUP DATABASE' command
  4. 4. Download the latest Db2 fix pack for your version from IBM Fix Central (https://www.ibm.com/support/fixcentral/)
  5. 5. Stop all Db2 instances and services
  6. 6. Install the fix pack using the installation wizard or silent install with response file
  7. 7. Restart Db2 instances and verify the upgrade with 'db2level'
  8. 8. Apply the fix pack to all nodes in a partitioned database environment
Caveat Review IBM Db2 11.5 migration guide for compatibility changes; test applications against new version before production deployment

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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