CVE-2024-25030: Medium severity ibm db2 vulnerability

Published Apr 2, 2024
·
Updated

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.

Other sources

IBM Db2 for Linux, UNIX and Windows (includes Db2 Connect Server) stores potentially sensitive information in log files that could be read by a local user.

— IBM

Affected Software

7 affected components
IBM Db2 Linux=11.1
IBM Data Virtualization on Cloud Pak for Data<=3.0
IBM Watson Query on Cloud Pak for Data<=2.2
IBM Watson Query on Cloud Pak for Data<=2.1
IBM Watson Query on Cloud Pak for Data<=2.0
IBM Data Virtualization on Cloud Pak for Data<=1.8
IBM Data Virtualization on Cloud Pak for Data<=1.7

Event History

Apr 3, 2024
CVE Published
via MITRE·12:14 PM
Data Sourced
via MITRE·12:14 PM
DescriptionSeverityWeakness
Aug 15, 2025
Data Sourced
via IBM·03:29 PM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-25030?

CVE-2024-25030 is classified as a moderate severity vulnerability due to the potential exposure of sensitive information in log files.

2

How do I fix CVE-2024-25030?

To fix CVE-2024-25030, ensure that log files are secured and do not store sensitive user information, and apply any available patches provided by IBM.

3

Who is affected by CVE-2024-25030?

CVE-2024-25030 affects users of IBM Db2 for Linux, UNIX, and Windows, specifically version 11.1 and its related products.

4

What are the potential risks of CVE-2024-25030?

The risks of CVE-2024-25030 include unauthorized access to potentially sensitive information by local users, leading to data exposure.

5

Is there a workaround for CVE-2024-25030?

A potential workaround for CVE-2024-25030 is to restrict access to log files to authorized users only, while awaiting a permanent fix.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203