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: 81

  1. 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.20.10-r0
    Published Updated
  2. 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.20.9-r0
    Published Updated
  3. 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.20.8-r0
    Published Updated
  4. 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.20.8-r0
    Published Updated
  5. 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.20.8-r0
    Published Updated
  6. 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
  7. 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.7-r0
    Published Updated
  8. 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
  9. CVE-2023-29404

    Critical · CVSS 9.8EPSS 1.82%Fix available

    Improper handling of non-optional LDFLAGS 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. The arguments for a number of flags which are non-optional are incorrectly considered optional, allowing disallowed flags to be smuggled through the LDFLAGS sanitization. This affects usage of both the gc and gccgo compilers.

    • Update to 1.20.5-r0
    Published Updated
  10. CVE-2023-29403

    High · CVSS 7.8EPSS 0.43%Fix available

    Unsafe behavior in setuid/setgid binaries in runtime

    On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits. This can be dangerous in certain cases, such as when dumping memory state, or assuming the status of standard i/o file descriptors. If a setuid/setgid binary is executed with standard I/O file descriptors closed, opening any files can result in unexpected content being read or written with elevated privileges. Similarly, if a setuid/setgid program is terminated, either via panic or signal, it may leak the contents of its registers.

    • Update to 1.20.5-r0
    Published Updated
  11. CVE-2023-29402

    Critical · CVSS 9.8EPSS 1.69%Fix available

    Code injection via go command with cgo in cmd/go

    The go command may generate unexpected code at build time when using cgo. This may result in unexpected behavior when running a go program which uses cgo. This may occur when running an untrusted module which contains directories with newline characters in their names. Modules which are retrieved using the go command, i.e. via "go get", are not affected (modules retrieved using GOPATH-mode, i.e. GO111MODULE=off, may be affected).

    • Update to 1.20.5-r0
    Published Updated
  12. CVE-2023-24539

    High · CVSS 7.3EPSS 1.03%Fix available

    Improper sanitization of CSS values in html/template

    Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input.

    • Update to 1.20.4-r0
    Published Updated
  13. CVE-2023-24540

    Critical · CVSS 9.8EPSS 1.56%Fix available

    Improper handling of JavaScript whitespace in html/template

    Not all valid JavaScript whitespace characters are considered to be whitespace. Templates containing whitespace characters outside of the character set "\t\n\f\r\u0020\u2028\u2029" in JavaScript contexts that also contain actions may not be properly sanitized during execution.

    • Update to 1.20.4-r0
    Published Updated
  14. CVE-2023-29400

    High · CVSS 7.3EPSS 1.03%Fix available

    Improper handling of empty HTML attributes in html/template

    Templates containing actions in unquoted HTML attributes (e.g. "attr={{.}}") executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags.

    • Update to 1.20.4-r0
    Published Updated
  15. CVE-2023-24538

    Critical · CVSS 9.8EPSS 2.28%Fix available

    Backticks not treated as string delimiters in html/template

    Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. "var a = {{.}}"), since there is no obviously safe way to allow this behavior. This

    • Update to 1.20.3-r0
    Published Updated
  16. CVE-2023-24534

    High · CVSS 7.5EPSS 1.89%Fix available

    Excessive memory allocation in net/http and net/textproto

    HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service. Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service. With fix, header parsing now correctly allocates only the memory required to hold parsed headers.

    • Update to 1.20.3-r0
    Published Updated
  17. CVE-2023-24536

    High · CVSS 7.5EPSS 1.47%Fix available

    Excessive resource consumption in net/http, net/textproto and mime/multipart

    Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3. ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combi

    • Update to 1.20.3-r0
    Published Updated

Check your server

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

Check your server →