Sensitive Data Exposure in ibm_db

published 2020-09-03 6y ago modified 2021-09-29 5y ago

cvss: 5.0; version 3.1, GitHub
cisa kev: Not listed; not in CISA's catalog
epss: —; no score, EPSS covers CVEs only
public exploits: 0; none known

Versions of `ibm_db` prior to 2.6.0 are vulnerable to Sensitive Data Exposure. The package printed database credentials in plaintext in logs while in debug mode.

## Recommendation

Upgrade to version 2.6.0 or later and ensure sensitive information was not logged.

Patch / fix

fixed in 1 links 1

npm ibm_db 2.6.0

github.com/ibmdb/node-ibm_db@526c88b commit

Is GHSA-p77h-hv6g-fmfp in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by	version	score	vector
GitHub	3.1	5.0	CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	ibm_db	<2.6.0	2.6.0

References

Sources

GitHub Advisory GHSA-p77h-hv6g-fmfp

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.