Skip to content

← Public intelligence

npm package

https-proxy-agent

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

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

  1. Medium, CVSS 6.1npmAmendedPublished

    Machine-In-The-Middle in https-proxy-agent

    GHSA-pc5p-h8pf-mvwp

    Affected
    • npm https-proxy-agent < 2.2.3
    Fixed in
    2.2.3· Vendor fix available
    Issue
    Versions of https-proxy-agent prior to 2.2.3 are vulnerable to Machine-In-The-Middle. The package fails to enforce TLS on the socket if the proxy server responds the to the request with a HTTP status different than 200. This allows an attacker with access to the proxy server to intercept unencrypted communications, which may include sensitive information such as credentials. Recommendation Upgrade to version 3.0.0 or 2.2.3.

    Recommended action: Upgrade to 2.2.3 or later, 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 →
  2. Critical, CVSS 9.1npmAmendedPublished

    Denial of Service in https-proxy-agent

    CVE-2018-3739 · GHSA-8g7p-74h8-hg48

    Affected
    • npm https-proxy-agent < 2.2.0
    Fixed in
    2.2.0· Vendor fix available
    Issue
    Versions of https-proxy-agent before 2.2.0 are vulnerable to denial of service. This is due to unsanitized options (proxy.auth) being passed to Buffer(). Recommendation Update to version 2.2.0 or later.

    Recommended action: Upgrade to 2.2.0 or later, 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 →