dbcve.org
Db2Application · Ibm

CVE-2023-47145

HIGH · 7.8 CVSS v3.1 Published 2024-01-07
Fix available
A fix is available. Upgrade to 10.5.0.11 / 11.1.4.7 or later.
See remediation →
80/100
Remediation priority · High
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 Windows (includes Db2 Connect Server) 10.5, 11.1, and 11.5 could allow a local user to escalate their privileges to the SYSTEM user using the MSI repair functionality. IBM X-Force ID: 270402.

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 installations on Windows expose MSI repair functionality that can be exploited by any local user to execute code with SYSTEM-level privileges. An attacker with basic Windows user access can trigger the repair mode of the Db2 MSI installer to elevate their privileges to the highest local level.

MitigationApply IBM's security patches for affected Db2 versions (10.5, 11.1, 11.5) as provided in the vendor advisory. In the interim, restrict interactive logon access to server consoles and monitor for suspicious MSI repair invocations on Db2 systems.

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, < 10.5.0.11>= 11.1, < 11.1.4.7>= 11.5, < 11.5.8

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

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 on Windows
    Check for Db2 installation directories (typically C:\Program Files\IBM\DB2 or C:\Program Files (x86)\IBM\DB2) or query the Windows Registry under HKLM\SOFTWARE\IBM\DB2 for installed instances.
    Affected if Db2 is found installed on the Windows system
  2. Identify installed Db2 version
    Run 'db2level' from the Db2 bin directory (e.g., C:\Program Files\IBM\DB2\<instance>\BIN\db2level.exe) or query the registry key HKLM\SOFTWARE\IBM\DB2\<instance>\Version.
    Affected if Unable to determine version - further investigation needed
  3. Compare version against affected ranges
    The affected versions are: 10.5.x where x < 11 (i.e., < 10.5.0.11), 11.1.x where x < 7 (i.e., < 11.1.4.7), and 11.5.x where x < 8 (i.e., < 11.5.8). Compare your installed version against these ranges.
    Affected if Installed version falls within 10.5.0.0 to 10.5.0.10, 11.1.0.0 to 11.1.4.6, or 11.5.0.0 to 11.5.7
  4. Confirm Windows platform
    This vulnerability affects only Windows installations. Verify the operating system is Windows using 'systeminfo' or 'winver'.
    Affected if Operating system is Windows and Db2 version is in the affected ranges

If IBM Db2 is installed on Windows and the installed version falls within 10.5.0.0-10.5.0.10, 11.1.0.0-11.1.4.6, or 11.5.0.0-11.5.7, the system is vulnerable to local privilege escalation via MSI repair functionality.

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 10.5.0.11 / 11.1.4.7 / 11.5.8 or later
Fixed in 10.5.0.1111.1.4.711.5.8
Interim mitigation

Apply IBM's security patches for affected Db2 versions (10.5, 11.1, 11.5) as provided in the vendor advisory. In the interim, restrict interactive logon access to server consoles and monitor for suspicious MSI repair invocations on Db2 systems.

Recommended fix High confidence

Db2 10.5.0.11, 11.1.4.7, or 11.5.8 depending on your current major version branch

  1. 1. Back up all Db2 databases and configurations before starting the upgrade process
  2. 2. Stop all Db2 instances and services on the Windows server
  3. 3. Download the appropriate Db2 fix pack for your version from IBM Fix Central (10.5.0.11, 11.1.4.7, or 11.5.8)
  4. 4. Run the Db2 installer with administrator privileges on Windows
  5. 5. Follow the IBM installation wizard to apply the fix pack upgrade
  6. 6. After installation completes, verify the Db2 version matches the target fixed release
  7. 7. Start the Db2 services and instances
  8. 8. Validate that applications can connect to the database successfully
Caveat Standard Db2 fix pack upgrades are generally non-breaking; however, always test in a non-production environment first and review IBM's fix pack readme for version-specific notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Db2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,150
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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