Microsoft Windows CryptoAPI Spoofing Vulnerability

HTTP/2 Rapid Reset Attack Vulnerability

Code execution vulnerability in SWIG code generation in cmd/go

The "go get" implementation in Go 1.9.4, when the -insecure command-line option is used, does not validate the import path (get/vcs.go only checks for "://" anywhere in the…

Potential code smuggling via doc comments in cmd/cgo

Unexpected command execution in untrusted VCS repositories in cmd/go

Case-sensitive excludedSubtrees name constraints cause Auth Bypass in crypto/x509

Go before 1.10.8 and 1.11.x before 1.11.5 mishandles P-521 and P-384 elliptic curves, which allows attackers to cause a denial of service (CPU consumption) or possibly conduct…

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

In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to directory traversal when executed with the import path of a malicious Go package which contains…

In Go before 1.10.6 and 1.11.x before 1.11.3, the "go get" command is vulnerable to remote code execution when executed with the -u flag and the import path of a malicious Go…

The net/http package in Go through 1.6 does not attempt to address RFC 3875 section 4.1.18 namespace conflicts and therefore does not protect CGI applications from the presence of…

Root escape via symlink plus trailing slash in os

Arbitrary file write using cgo pkg-config directive in cmd/go

On Unix platforms, the Go runtime does not behave differently when a binary is run with the setuid/setgid bits

Empty Cmd.Path can trigger unintended binary in os/exec on Windows

Go through 1.12 on Windows misuses certain LoadLibrary functionality, leading to DLL injection

Go before 1.8.7, Go 1.9.x before 1.9.4, and Go 1.10 pre-releases before Go 1.10rc2 allow "go get" remote command execution during source code build, by leveraging the gcc or clang…

Untrusted search path vulnerability in Go before 1.5.4 and 1.6.x before 1.6.1 on Windows allows local users to gain privileges via a Trojan horse DLL in the current working…

Traefik - Denial of Service via HTTP/2 Request Handling

Quadratic string concatentation in consumeComment in net/mail

Malicious module proxy can bypass checksum database in cmd/go

Crash when handling long CNAME response in net

Quadratic string concatenation in consumePhrase in net/mail

Panic in Dial and LookupPort when handling NUL byte on Windows in net

Infinite loop in HTTP/2 transport when given bad SETTINGS_MAX_FRAME_SIZE in net/http/internal/http2 in golang.org/x/net

Unexpected work during chain building in crypto/x509

Inefficient policy validation in crypto/x509

Unauthenticated TLS 1.3 KeyUpdate record can cause persistent connection retention and DoS in crypto/tls

Incorrect parsing of IPv6 host literals in net/url

Incorrect enforcement of email constraints in crypto/x509

Memory exhaustion in query parameter parsing in net/url

Excessive resource consumption when printing error string for host certificate validation in crypto/x509

Panic when validating certificates with DSA public keys in crypto/x509

Quadratic complexity when parsing some invalid inputs in encoding/pem

Quadratic complexity when checking name constraints in crypto/x509

Using go get to fetch a module with the ".git" suffix may unexpectedly fallback to the insecure "git://" protocol if the module is unavailable via the secure "https://" and…

Before Go 1.20, the RSA based TLS key exchanges used the math/big library, which is not constant time

The filepath package does not recognize paths with a \??\ prefix as special

A malicious HTTP/2 client which rapidly creates requests and immediately resets them can cause excessive server resource consumption

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…

Processing an incomplete post-handshake message for a QUIC connection can cause a panic

Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow

Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts

HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service

A denial of service is possible from excessive resource consumption in net/http and mime/multipart

Large handshake records may cause panics in crypto/tls

A maliciously crafted HTTP/2 stream could cause excessive CPU consumption in the HPACK decoder, sufficient to cause a denial of service from a small number of small requests

A path traversal vulnerability exists in filepath.Clean on Windows

On Windows, restricted files can be accessed via os.DirFS and http.Dir