dbcve.org
Db2Application · Ibm

CVE-2023-47701

HIGH · 7.5 CVSS v3.1 Published 2023-12-04
Fix available
A fix is available. Upgrade to after 11.5.9 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) 10.5, 11.1, and 11.5 is vulnerable to denial of service with a specially crafted query. IBM X-Force ID: 266166.

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 versions 10.5, 11.1, and 11.5 contain a denial of service vulnerability where a specially crafted query can cause the database service to become unavailable, likely due to improper handling of malformed SQL input in the query processor or parser.

MitigationApply IBM Db2 fix packs or patches as released by IBM for the affected versions. Until a patch is available, consider restricting query execution privileges and implementing query timeout limits to mitigate potential exploitation.

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.0, <= 11.1.4.7>= 11.5, <= 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
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. Verify IBM Db2 is installed
    Run 'db2level' command on Linux/Unix or check Windows Services for Db2 service, or query SELECT * FROM sysibm.sysversions
    Affected if Db2 database software is present on the system
  2. Determine the installed Db2 version number
    Execute 'db2level' and locate the version string (format: V10.5.0.x, V11.1.0.x, or V11.5.x)
    Affected if Unable to retrieve version information from the Db2 installation
  3. Compare version against affected range for Db2 10.5
    If version starts with 10.5, check if it is between 10.5.0.0 and 10.5.0.11 inclusive
    Affected if Installed version falls within 10.5.0.0 through 10.5.0.11
  4. Compare version against affected range for Db2 11.1
    If version starts with 11.1, check if it is between 11.1.0.0 and 11.1.4.7 inclusive
    Affected if Installed version falls within 11.1.0.0 through 11.1.4.7
  5. Compare version against affected range for Db2 11.5
    If version starts with 11.5, check if it is between 11.5.0.0 and 11.5.9 inclusive
    Affected if Installed version falls within 11.5.0.0 through 11.5.9

The environment is affected if IBM Db2 is installed and its version falls within any of the ranges: 10.5.0.0-10.5.0.11, 11.1.0.0-11.1.4.7, or 11.5.0.0-11.5.9

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

Apply IBM Db2 fix packs or patches as released by IBM for the affected versions. Until a patch is available, consider restricting query execution privileges and implementing query timeout limits to mitigate potential exploitation.

Recommended fix Moderate confidence

Db2 11.5.10+ (or latest available fix pack for respective release line)

  1. 1. Identify the current Db2 version by running 'db2level' command or querying sysibmadm.env_cfg
  2. 2. Determine which Db2 release family (10.5, 11.1, or 11.5) is currently installed
  3. 3. For Db2 10.5.x users: IBM no longer supports this release line; plan migration to Db2 11.5
  4. 4. For Db2 11.1.x users: Upgrade to Db2 11.1.5 or later (contact IBM support for specific fix pack)
  5. 5. For Db2 11.5.x users: Upgrade to Db2 11.5.10 or later to obtain the security fix
  6. 6. Test the upgrade in a non-production environment before deploying to production
  7. 7. Ensure proper database backups exist before performing upgrade
  8. 8. After upgrade, verify the vulnerability is resolved by testing with the previously crafted query pattern
Caveat Db2 upgrade may require application testing; review IBM Db2 migration guide for compatibility considerations

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
  • Testing8.0 h
  • Review / QA3.0 h
23.0 hours of engineering $3,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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