Skip to content

← Public intelligence

Go package

github.com/pires/go-proxyproto

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. High, CVSS 7.5GoPublished

    github.com/pires/go-proxyproto vulnerable to DoS via Connection descriptor exhaustion

    CVE-2021-23409 · GHSA-xcf7-q56x-78gh

    Affected
    • Go github.com/pires/go-proxyproto < 0.6.1
    Fixed in
    0.6.1· Vendor fix available
    Issue
    The package github.com/pires/go-proxyproto before 0.6.1 is vulnerable to Denial of Service (DoS) via creating connections without the proxy protocol header. While this issue was patched in 0.6.0, the fix introduced additional issues which were subsequently patched in 0.6.1.

    Recommended action: Upgrade to 0.6.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Medium, CVSS 4.9GoPublished

    github.com/pires/go-proxyproto denial of service vulnerability

    CVE-2021-23351 · GHSA-fqh4-rh59-xhvf

    Affected
    • Go github.com/pires/go-proxyproto < 0.5.0
    Fixed in
    0.5.0· Vendor fix available
    Issue
    The package github.com/pires/go-proxyproto before 0.5.0 are vulnerable to Denial of Service (DoS) via the parseVersion1() function. The reader in this package is a default bufio.Reader wrapping a net.Conn. It will read from the connection until it finds a newline. Since no limits are implemented in the code, a deliberately malformed V1 header could be used to exhaust memory in a server process using this code - and create a DoS. This can be exploited by sending a stream starting with PROXY and continuing to send data (which does not contain a newline) until the target stops acknowledging. The risk here is small, because only trusted sources should be allowed to send proxy protocol headers.

    Recommended action: Upgrade to 0.5.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →