p PatchFirst

PatchFirst · Latest vulnerabilities

go vulnerabilities

Vulnerabilities published for go in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 91

  1. CVE-2023-45288

    High · CVSS 7.5EPSS 89.45%Fix available

    HTTP/2 CONTINUATION flood in net/http

    An attacker may cause an HTTP/2 endpoint to read arbitrary amounts of header data by sending an excessive number of CONTINUATION frames. Maintaining HPACK state requires parsing and processing all HEADERS and CONTINUATION frames on a connection. When a request's headers exceed MaxHeaderBytes, no memory is allocated to store the excess headers, but they are still parsed. This permits an attacker to cause an HTTP/2 endpoint to read arbitrary amounts of header data, all associated with a request which is going to be rejected. These headers can include Huffman-encoded data which is significantly more expensive for the receiver to decode than for

    • Update to 1.21.9-r0
    Published Updated
  2. CVE-2024-24785

    Medium · CVSS 5.4EPSS 0.79%Fix available

    Errors returned from JSON marshaling may break template escaping in html/template

    If errors returned from MarshalJSON methods contain user controlled data, they may be used to break the contextual auto-escaping behavior of the html/template package, allowing for subsequent actions to inject unexpected content into templates.

    • Update to 1.21.8-r0
    Published Updated
  3. CVE-2024-24784

    High · CVSS 7.5EPSS 1.05%Fix available

    Comments in display names are incorrectly handled in net/mail

    The ParseAddressList function incorrectly handles comments (text within parentheses) within display names. Since this is a misalignment with conforming address parsers, it can result in different trust decisions being made by programs using different parsers.

    • Update to 1.21.8-r0
    Published Updated
  4. CVE-2023-45289

    Medium · CVSS 4.3EPSS 1.08%Fix available

    Incorrect forwarding of sensitive headers and cookies on HTTP redirect in net/http

    When following an HTTP redirect to a domain which is not a subdomain match or exact match of the initial domain, an http.Client does not forward sensitive headers such as "Authorization" or "Cookie". For example, a redirect from foo.com to www.foo.com will forward the Authorization header, but a redirect to bar.com will not. A maliciously crafted HTTP redirect could cause sensitive headers to be unexpectedly forwarded.

    • Update to 1.21.8-r0
    Published Updated
  5. CVE-2023-45290

    Medium · CVSS 6.5EPSS 1.16%Fix available

    Memory exhaustion in multipart form parsing in net/textproto and net/http

    When parsing a multipart form (either explicitly with Request.ParseMultipartForm or implicitly with Request.FormValue, Request.PostFormValue, or Request.FormFile), limits on the total size of the parsed form were not applied to the memory consumed while reading a single form line. This permits a maliciously crafted input containing very long lines to cause allocation of arbitrarily large amounts of memory, potentially leading to memory exhaustion. With fix, the ParseMultipartForm function now correctly limits the maximum size of form lines.

    • Update to 1.21.8-r0
    Published Updated
  6. CVE-2024-24783

    Medium · CVSS 5.9EPSS 0.67%Fix available

    Verify panics on certificates with an unknown public key algorithm in crypto/x509

    Verifying a certificate chain which contains a certificate with an unknown public key algorithm will cause Certificate.Verify to panic. This affects all crypto/tls clients, and servers that set Config.ClientAuth to VerifyClientCertIfGiven or RequireAndVerifyClientCert. The default behavior is for TLS servers to not verify client certificates.

    • Update to 1.21.8-r0
    Published Updated
  7. CVE-2023-39326

    Medium · CVSS 5.3EPSS 1.21%Fix available

    Denial of service via chunk extensions in net/http

    A malicious HTTP sender can use chunk extensions to cause a receiver reading from a request or response body to read many more bytes from the network than are in the body. A malicious HTTP client can further exploit this to cause a server to automatically read a large amount of data (up to about 1GiB) when a handler fails to read the entire body of a request. Chunk extensions are a little-used HTTP feature which permit including additional metadata in a request or response body sent using the chunked encoding. The net/http chunked encoding reader discards this metadata. A sender can exploit this by inserting a large metadata segment with each

    • Update to 1.21.5-r0
    Published Updated
  8. CVE-2023-39325

    High · CVSS 7.5EPSS 3.8%Fix available

    HTTP/2 rapid reset can cause excessive work in net/http

    A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption. While the total number of requests is bounded by the http2.Server.MaxConcurrentStreams setting, resetting an in-progress request allows the attacker to create a new request while the existing one is still executing. With the fix applied, HTTP/2 servers now bound the number of simultaneously executing handler goroutines to the stream concurrency limit (MaxConcurrentStreams). New requests arriving when at the limit (which can only happen after the client has reset an existing, in-flight request) will be queued un

    • Update to 1.21.3-r0
    Published Updated
  9. CVE-2023-39323

    High · CVSS 8.1EPSS 1.91%Fix available

    Arbitrary code execution during build via line directives in cmd/go

    Line directives ("//line") can be used to bypass the restrictions on "//go:cgo_" directives, allowing blocked linker and compiler flags to be passed during compilation. This can result in unexpected execution of arbitrary code when running "go build". The line directive requires the absolute path of the file in which the directive lives, which makes exploiting this issue significantly more complex.

    • Update to 1.21.2-r0
    Published Updated
  10. CVE-2023-39322

    High · CVSS 7.5EPSS 1.34%Fix available

    Memory exhaustion in QUIC connection handling in crypto/tls

    QUIC connections do not set an upper bound on the amount of data buffered when reading post-handshake messages, allowing a malicious QUIC connection to cause unbounded memory growth. With fix, connections now consistently reject messages larger than 65KiB in size.

    • Update to 1.21.1-r0
    Published Updated
  11. CVE-2023-39319

    Medium · CVSS 6.1EPSS 0.91%Fix available

    Improper handling of special tags within script contexts in html/template

    The html/template package does not apply the proper rules for handling occurrences of "<script", "<!--", and "</script" within JS literals in <script> contexts. This may cause the template parser to improperly consider script contexts to be terminated early, causing actions to be improperly escaped. This could be leveraged to perform an XSS attack.

    • Update to 1.21.1-r0
    Published Updated
  12. CVE-2023-39320

    Critical · CVSS 9.8EPSS 1.76%Fix available

    Arbitrary code execution via go.mod toolchain directive in cmd/go

    The go.mod toolchain directive, introduced in Go 1.21, can be leveraged to execute scripts and binaries relative to the root of the module when the "go" command was executed within the module. This applies to modules downloaded using the "go" command from the module proxy, as well as modules downloaded directly using VCS software.

    • Update to 1.21.1-r0
    Published Updated
  13. CVE-2023-39318

    Medium · CVSS 6.1EPSS 0.93%Fix available

    Improper handling of HTML-like comments in script contexts in html/template

    The html/template package does not properly handle HTML-like "" comment tokens, nor hashbang "#!" comment tokens, in <script> contexts. This may cause the template parser to improperly interpret the contents of <script> contexts, causing actions to be improperly escaped. This may be leveraged to perform an XSS attack.

    • Update to 1.21.1-r0
    Published Updated
  14. CVE-2023-29409

    Medium · CVSS 5.3EPSS 1.91%Fix available

    Large RSA keys can cause high CPU usage in crypto/tls

    Extremely large RSA keys in certificate chains can cause a client/server to expend significant CPU time verifying signatures. With fix, the size of RSA keys transmitted during handshakes is restricted to <= 8192 bits. Based on a survey of publicly trusted RSA keys, there are currently only three certificates in circulation with keys larger than this, and all three appear to be test certificates that are not actively deployed. It is possible there are larger keys in use in private PKIs, but we target the web PKI, so causing breakage here in the interests of increasing the default safety of users of crypto/tls seems reasonable.

    • Update to 1.20.7-r0
    Published Updated
  15. CVE-2023-29406

    Medium · CVSS 6.5EPSS 1.45%Fix available

    Insufficient sanitization of Host header in net/http

    The HTTP/1 client does not fully validate the contents of the Host header. A maliciously crafted Host header can inject additional headers or entire requests. With fix, the HTTP/1 client now refuses to send requests containing an invalid Request.Host or Request.URL.Host value.

    • Update to 1.20.6-r0
    Published Updated
  16. CVE-2023-29405

    Critical · CVSS 9.8EPSS 1.71%Fix available

    Improper sanitization of LDFLAGS with embedded spaces in go command with cgo in cmd/go

    The go command may execute arbitrary code at build time when using cgo. This may occur when running "go get" on a malicious module, or when running any other command which builds untrusted code. This is can by triggered by linker flags, specified via a "#cgo LDFLAGS" directive. Flags containing embedded spaces are mishandled, allowing disallowed flags to be smuggled through the LDFLAGS sanitization by including them in the argument of another flag. This only affects usage of the gccgo compiler.

    • Update to 1.20.5-r0
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →