GHSA-jmqm-f2gx-4fjv json
Sensitive information exposure through logs in npm-registry-fetch
published 6y ago modified 5y ago
- cvss
- 5.3
- 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
Summary
Affected versions of `npm-registry-fetch` are vulnerable to an information exposure vulnerability through log files. The cli supports URLs like `<protocol>://[<user>[:<password>]@]<hostname>[:<port>][:][/]<path>`. The password value is not redacted and is printed to stdout and also to any generated log files.
Patch / fix
- npm npm-registry-fetch 4.0.5, 8.1.1
- github.com/npm/npm-registry-fetch@18bf9b9 commit
- github.com/npm/npm-registry-fetch#29 pull request
Is GHSA-jmqm-f2gx-4fjv 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 FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| npm | npm-registry-fetch | <4.0.5 >=5.0.0, <8.1.1 |
4.0.5 8.1.1 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/npm/npm-registry-fetch/pull/29
web
-
github.com
/npm/npm-registry-fetch/commit/18bf9b97fb1deecdba01ffb05580370846255c88
web
-
github.com
/npm/npm-registry-fetch/security/advisories/GHSA-jmqm-f2gx-4fjv
web
-
github.com
/npm/npm-registry-fetch
package
-
snyk.io
/vuln/SNYK-JS-NPMREGISTRYFETCH-575432
web
Sources
- GitHub Advisory GHSA-jmqm-f2gx-4fjv
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.