Sensitive information exposure through logs in npm-registry-fetch
Priority LOW 38CWE-352Published · Updated
Key facts
- Attack vector
- —
- Privileges required
- —
- User interaction
- —
- Attack complexity
- —
- Impact type
- Tampering
- Confidentiality · integrity · availability
- —
- Fix status
- Fixed
No CVSS vector from any source. Fix status from GitHub. Impact type from CWE-352.
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.
Why it matters now
Fix Fixed npm-registry-fetch (npm): 4.0.5, 8.1.1
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| — | npm-registry-fetch (npm) | before 4.0.5 | 4.0.5 | Patch available | GHSA-jmqm-f2gx-4fjv |
| — | npm-registry-fetch (npm) | 5.0.0 to before 8.1.1 | 8.1.1 | Patch available | GHSA-jmqm-f2gx-4fjv |
- npm-registry-fetch (npm) Vendor— Affected before 4.0.5 Fixed in 4.0.5 Patch available GHSA-jmqm-f2gx-4fjv
- npm-registry-fetch (npm) Vendor— Affected 5.0.0 to before 8.1.1 Fixed in 8.1.1 Patch available GHSA-jmqm-f2gx-4fjv
Remediation
- Fix · GHSA-jmqm-f2gx-4fjv npm-registry-fetch (npm) Fixed in 4.0.5 Advisory →
- Fix · GHSA-jmqm-f2gx-4fjv npm-registry-fetch (npm) Fixed in 8.1.1 Advisory →
Timeline
- 2026-10-03 Threatist record created from GHSA-jmqm-f2gx-4fjv
References
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences