Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

npm package

npm-registry-fetch

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.3npmAmendedPublished

    Sensitive information exposure through logs in npm-registry-fetch

    GHSA-jmqm-f2gx-4fjv

    Affected
    • npm npm-registry-fetch < 4.0.5; >= 5.0.0, < 8.1.1
    Fixed in
    8.1.14.0.5· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 8.1.1 or 4.0.5 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →