Homepage

org.webjars.npm:follow-redirects@1.14.4 vulnerabilities

  • latest version

    1.15.9

  • latest non vulnerable version

    1.15.9

  • first published

    8 years ago

  • latest version published

    2 months ago

  • licenses detected

  • package manager

    View on Maven Repository
    • Go back to all versions of this package
    Report a new vulnerability Found a mistake?

    Direct Vulnerabilities

    Known vulnerabilities in the org.webjars.npm:follow-redirects package. This does not include vulnerabilities belonging to this package’s dependencies.

    How to fix?

    Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

    Fix for free
    VulnerabilityVulnerable Version
    • 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 org.webjars.npm: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 org.webjars.npm:follow-redirects to version 1.15.4 or higher.

    [,1.15.4)
    • L
    Information Exposure

    Affected versions of this package are vulnerable to Information Exposure due a leakage of the Authorization header from the same hostname during HTTPS to HTTP redirection. An attacker who can listen in on the wire (or perform a MITM attack) will be able to receive the Authorization header due to the usage of the insecure HTTP protocol which does not verify the hostname the request is sending to.

    How to fix Information Exposure?

    Upgrade org.webjars.npm:follow-redirects to version 1.14.8 or higher.

    [,1.14.8)
    • M
    Information Exposure

    Affected versions of this package are vulnerable to Information Exposure by leaking the cookie header to a third party site in the process of fetching a remote URL with the cookie in the request body. If the response contains a location header, it will follow the redirect to another URL of a potentially malicious actor, to which the cookie would be exposed.

    How to fix Information Exposure?

    Upgrade org.webjars.npm:follow-redirects to version 1.14.7 or higher.

    [,1.14.7)
    Go back to all versions of this package