dbcve.org
Db2Application · Ibm

CVE-2024-25030

MEDIUM · 5.5 CVSS v3.1 Published 2024-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
57/100
Remediation priority · Elevated
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 stores potentially sensitive information in log files that could be read by a local user. IBM X-Force ID: 281677.

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 11.1 for Linux, UNIX, and Windows stores potentially sensitive information in log files that can be read by local users with system access. This information disclosure vulnerability has a CVSS of 5.5, indicating moderate severity due to the low attack complexity and limited scope of information exposure.

MitigationRestrict file system permissions on Db2 log directories to authorized administrators only, and apply IBM's security patch for CVE-2024-25030 when available to prevent sensitive data from being written to logs.

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

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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. Confirm IBM Db2 version
    Run 'db2level' or 'db2pd -version' from a Db2 instance owner account to retrieve the installed Db2 version number
    Affected if The installed version is exactly 11.1 (any 11.1.x release)
  2. Identify Db2 log directories
    Run 'db2 get dbm cfg | grep -i diag' to locate the diagnostic path (DIAGPATH), which contains log files
    Affected if DIAGPATH points to a directory readable by non-privileged users
  3. Check log directory permissions
    Use 'ls -ld <DIAGPATH>' to verify that only the Db2 instance owner and db2admin group have read/write access
    Affected if World-readable or group-readable permissions exist on the log directory
  4. Inspect log files for sensitive data
    Search log files in the DIAGPATH (such as db2diag.log and messages log) using 'grep -i -E "password|secret|token|credential" <DIAGPATH>/*' to find potentially sensitive strings
    Affected if Log files contain cleartext passwords, secrets, or credentials

A system is affected if running IBM Db2 version 11.1 with publicly readable log directories or log files containing sensitive information.

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

Restrict file system permissions on Db2 log directories to authorized administrators only, and apply IBM's security patch for CVE-2024-25030 when available to prevent sensitive data from being written to logs.

Recommended fix Moderate confidence

IBM Db2 11.1 FP10 or later, or migrate to Db2 11.5

  1. Check current Db2 version using: db2pd -version or db2 SELECT GET_VARCHAR_FROM_XML(db2diag.log, 'product_version') FROM SYSIBM.SYSDUMMY1
  2. Locate Db2 diagnostic log files (db2diag.log) and administration notification logs in the <Db2 installation directory>/sqllib/db2dump/ path
  3. Review log files for any sensitive information exposure and ensure file permissions are restricted to authorized administrators only
  4. Apply the latest IBM Db2 11.1 fix pack (FP10 or later) from IBM Fix Central: https://www.ibm.com/support/fixcentral/
  5. After applying the fix pack, verify the remediation by checking IBM's security bulletin for CVE-2024-25030
Caveat Review IBM Db2 fix pack release notes for any known compatibility issues before applying; test in non-production environment first

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
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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