dbcve.org
Db2Application · Ibm

CVE-2023-29267

MEDIUM · 6.5 CVSS v3.1 Published 2024-06-12
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 (includes Db2 Connect Server) 10.5, 11.1, and 11.5is vulnerable to a denial of service, under specific configurations, as the server may crash when using a specially crafted SQL statement by an authenticated user. IBM X-Force ID: 287612.

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 for Linux, UNIX, and Windows versions 10.5, 11.1, and 11.5 contains a denial of service vulnerability where an authenticated user can crash the server by executing a specially crafted SQL statement under specific configurations. The attacker requires valid database credentials to exploit this issue.

MitigationApply IBM's published security patches for this vulnerability (contact IBM Support for fix packs). Until patched, limit SQL execution permissions to trusted users and review configuration settings that may enable this attack vector.

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= 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. Verify IBM Db2 is installed
    Run 'db2level' command or check for Db2 installation directories such as /opt/ibm/db2 or the presence of db2pd utility in the PATH
    Affected if IBM Db2 software is present on the system
  2. Determine installed Db2 version
    Execute 'db2level' and parse the output for the version number (e.g., v10.5, v11.1, or v11.5)
    Affected if The installed version starts with 10.5, 11.1, or 11.5 (including any subversions like 10.5.0.0 through 10.5.x, 11.1.0.0 through 11.1.x, or 11.5.0.0 through 11.5.x)
  3. Confirm database authentication is enabled
    Check Db2 configuration using 'db2 get database manager configuration' and look for authentication settings (AUTHENTICATION parameter)
    Affected if Authentication is set to a value other than NONE, meaning valid database credentials are required for access
  4. Identify users with SQL execution privileges
    Query system catalog tables (e.g., SELECT GRANTOR, GRANTEE FROM SYSCAT.DBAUTH where EXECUTECATMAUTH='Y') or review DBADM or SQLADM role assignments
    Affected if There are authenticated database users with permission to execute SQL statements (this is required for exploitation)
  5. Check for specific Db2 configurations that may enable the attack vector
    Review Db2 registry variables (db2set -all) and database manager configuration for non-default settings related to query processing or statement compilation
    Affected if Non-default configurations exist in Db2 settings, as the vulnerability triggers under specific configuration conditions

A system is affected if it runs IBM Db2 versions 10.5, 11.1, or 11.5 with authentication enabled and has users who can execute arbitrary SQL statements.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply IBM's published security patches for this vulnerability (contact IBM Support for fix packs). Until patched, limit SQL execution permissions to trusted users and review configuration settings that may enable this attack vector.

Fix this in Db2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA3.0 h
20.0 hours of engineering $3,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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