dbcve.org
Db2Application · Ibm

CVE-2024-40679

MEDIUM · 5.5 CVSS v3.1 Published 2025-01-08
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.5 is vulnerable to an information disclosure vulnerability as sensitive information may be included in a log file under specific conditions.

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 version 11.5 for Linux, UNIX, and Windows contains an information disclosure vulnerability where sensitive information may be written to log files under specific conditions. This could allow an attacker with access to the log files to obtain confidential data such as credentials or user data that should not be exposed.

MitigationReview and configure Db2 log settings to ensure sensitive data is filtered or masked before being written to log files. Apply any available IBM patches for CVE-2024-40679 and implement log access controls to limit exposure.

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.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
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. Check if IBM Db2 is installed and identify the version
    Run the command 'db2level' or 'db2pd -version' from a Db2 instance owner account. Alternatively, check the Db2 installation directory for version information.
    Affected if The installed version is IBM Db2 11.5 for Linux, UNIX, or Windows.
  2. Confirm the exact Db2 version number
    Examine the output from db2level to verify the full version string (for example, v11.5.0.0 through v11.5.9.x). Compare against the affected version range.
    Affected if The version shows 11.5.x indicating installation of the affected release.
  3. Identify Db2 log file locations
    Run 'db2 get dbm cfg | grep -i diag' to find the diagnostic path (DIAGPATH) configuration. Common default locations include the sqllib/db2dump directory under the instance home directory.
    Affected if Db2 is configured with a diagnostic log directory accessible to the system.
  4. Verify Db2 logging is enabled
    Run 'db2 get dbm cfg' and check that DIAGPATH is set and that logging is active. Also verify the database configuration for audit settings if applicable.
    Affected if Diagnostic logging (DIAGPATH) is configured and active, writing to log files.
  5. Examine log files for sensitive data exposure
    Review log files in the DIAGPATH directory (such as db2diag.log and nfm log files) for patterns that may contain sensitive information like passwords, usernames, or personal data that should not be logged.
    Affected if Log files contain or may contain sensitive data due to the vulnerability, allowing unauthorized access to confidential information through log file access.

You are affected if IBM Db2 version 11.5 is installed and diagnostic logging is enabled, creating potential for unauthorized access to sensitive data through log files.

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

Review and configure Db2 log settings to ensure sensitive data is filtered or masked before being written to log files. Apply any available IBM patches for CVE-2024-40679 and implement log access controls to limit exposure.

Fix this in Db2 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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