Homepage

npm-registry-fetch@3.0.0 vulnerabilities

Fetch-based http client for use with npm registry APIs

  • latest version

    19.0.0

  • latest non vulnerable version

    19.0.0

  • first published

    8 years ago

  • latest version published

    2 months ago

  • licenses detected

    • ISC
      >=0.0.0 <0.0.1; >=1.0.0
  • View npm-registry-fetch package health on Snyk Advisor  (opens in a new tab)
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the npm-registry-fetch package. This does not include vulnerabilities belonging to this package’s dependencies.

    Fix vulnerabilities automatically

    Snyk's AI Trust Platform automatically finds the best upgrade path and integrates with your development workflows. Secure your code at zero cost.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Insertion of Sensitive Information into Log File

    npm-registry-fetch is a Fetch-based http client for use with npm registry APIs

    Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File through log files. The package 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.

    How to fix Insertion of Sensitive Information into Log File?

    Upgrade npm-registry-fetch to version 4.0.5, 8.1.1 or higher.

    <4.0.5>=5.0.0 <8.1.1
    Go back to all versions of this package