Homepage

follow-redirects@1.15.2

HTTP and HTTPS modules that follow redirects.

  • latest version

    1.16.0

  • latest non vulnerable version

    1.16.0

  • first published

    13 years ago

  • latest version published

    6 days ago

  • licenses detected

  • View follow-redirects package health on Snyk  (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 follow-redirects 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
    Improper Removal of Sensitive Information Before Storage or Transfer

    Affected versions of this package are vulnerable to Improper Removal of Sensitive Information Before Storage or Transfer in the cross-domain redirects that do not strip custom authentication headers (such as X-API-Key, X-Auth-Token, Api-Key, Token). An attacker can obtain sensitive authentication headers by triggering a cross-domain redirect that causes custom authentication headers to be forwarded to an attacker-controlled domain.

    How to fix Improper Removal of Sensitive Information Before Storage or Transfer?

    Upgrade follow-redirects to version 1.16.0 or higher.

    <1.16.0
    • M
    Information Exposure

    Affected versions of this package are vulnerable to Information Exposure due to the handling of the Proxy-Authorization header across hosts. When using a dependent library, it only clears the authorization header during cross-domain redirects but allows the proxy-authentication header, which contains credentials, to persist. This behavior may lead to the unintended leakage of credentials if an attacker can trigger a cross-domain redirect and capture the persistent proxy-authentication header.

    How to fix Information Exposure?

    Upgrade follow-redirects to version 1.15.6 or higher.

    <1.15.6
    • H
    Improper Handling of Extra Parameters

    Affected versions of this package are vulnerable to Improper Handling of Extra Parameters due to the improper handling of URLs by the url.parse() function. When new URL() throws an error, it can be manipulated to misinterpret the hostname. An attacker could exploit this weakness to redirect traffic to a malicious site, potentially leading to information disclosure, phishing attacks, or other security breaches.

    How to fix Improper Handling of Extra Parameters?

    Upgrade follow-redirects to version 1.15.4 or higher.

    <1.15.4
    Go back to all versions of this package