Sensitive Data Exposure in ibm_db
Summary
GHSA-p77h-hv6g-fmfp: Sensitive Data Exposure in ibm_db. Affects ibm_db versions < 2.6.0. Fixed in 2.6.0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The ibm_db package is an npm package used for connecting to IBM Db2 databases from Node.js applications. It provides an interface to interact with the database, execute SQL statements, and retrieve results. The package is widely used in applications that require connectivity to IBM Db2 databases. However, versions prior to 2.6.0 are vulnerable to Sensitive Data Exposure.
Vulnerability Detail
The vulnerability in ibm_db versions prior to 2.6.0 is related to the package printing database credentials in plaintext in logs while in debug mode. This means that sensitive information, such as usernames and passwords, could be exposed to anyone with access to the logs. This vulnerability poses a moderate risk as it could lead to unauthorized access to the database and potential data breaches.
How To Fix
Minimum fixed version
2.6.0
This is the first release that contains the fix.
npm install ibm_db@2.6.0Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Conclusion
In conclusion, the ibm_db package versions prior to 2.6.0 are vulnerable to sensitive data exposure. It is crucial to upgrade to the fixed version and ensure that sensitive information is not logged in plaintext in the application's logs. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for ibm_db →
FAQ
ibm_db is an npm package used for connecting to IBM Db2 databases from Node.js applications. It provides an interface to interact with the database, execute SQL statements, and retrieve results.
The vulnerability in ibm_db versions prior to 2.6.0 can expose sensitive database credentials, such as usernames and passwords, in plaintext in logs. This could lead to unauthorized access to the database and potential data breaches.
To fix this vulnerability, you should upgrade to version 2.6.0 or later of the ibm_db package. Additionally, ensure that sensitive information is not logged in plaintext in the application's logs.
No, there is no known workaround for this vulnerability. Upgrading to the fixed version is the recommended solution.
You can find more information about this vulnerability in the GitHub Advisory Database: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2020/09/GHSA-p77h-hv6g-fmfp/GHSA-p77h-hv6g-fmfp.json
References
Related vulnerabilities
Recent vulnerabilities recorded for ibm_db.
