GHSA-jmqm-f2gx-4fjv Sensitive information exposure through logs in npm-registry-fetch
Not scored
Published
Check this codebase for GHSA-jmqm-f2gx-4fjv and fix it if it is affected.
What it is: GHSA-jmqm-f2gx-4fjv is a vulnerability in npm-registry-fetch, published on 7 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-jmqm-f2gx-4fjv in the wild and no public exploit code.
Affected packages and fixed versions:
- npm-registry-fetch (npm): affected all versions; fixed in 4.0.5
- npm-registry-fetch (npm): affected all versions; fixed in 4.0.5
- npm-registry-fetch (npm): affected from 5.0.0; fixed in 8.1.1
- npm-registry-fetch (npm): affected from 5.0.0; fixed in 8.1.1
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/GHSA-jmqm-f2gx-4fjv/ (Markdown: https://insights.sbomify.com/GHSA-jmqm-f2gx-4fjv/index.md)
Attackers can read sensitive credentials from logs or stdout when using npm-registry-fetch with URLs containing passwords.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is GHSA-jmqm-f2gx-4fjv?
GHSA-jmqm-f2gx-4fjv is a vulnerability in npm-registry-fetch, published on 7 Jul 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.Which versions are affected by GHSA-jmqm-f2gx-4fjv?
4 open source packages ship an affected version, including npm-registry-fetch.
| Package | Affected | Fixed in |
|---|---|---|
npm-registry-fetch npm | All versions | 4.0.5 |
npm-registry-fetch npm | All versions | 4.0.5 |
npm-registry-fetch npm | From 5.0.0 | 8.1.1 |
npm-registry-fetch npm | From 5.0.0 | 8.1.1 |
How do I fix GHSA-jmqm-f2gx-4fjv?
Upgrade npm-registry-fetch to a fixed version for your release line: 4.0.5 or 8.1.1.
Is GHSA-jmqm-f2gx-4fjv being exploited?
There is no known exploitation of GHSA-jmqm-f2gx-4fjv in the wild and no public exploit code.