CVE Vulnerability Catalog

Previously, a user operating inside a malicious Go project that defines a bogus golang.org/toolchain go.sum entry and operates a malicious GOMODPROXY could bypass the intended checksum. It is now ensured that golang.org/toolchain always goes to the network for the canonical checksum.

Previously, a user operating inside a malicious Go project that defines a bogus golang.org/fips140 and operates a malicious GOMODPROXY could serve an arbitrary module in its place. The trusted ziphash for the bundled golang.org/fips140 module is now unpacked and its entry in GOMODCACHE is constructed so it can be verified by the toolchain.

Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes.

When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to CONNECT converts the connection into a tunnel, the server should not treat it as continuing to contain HTTP.

Deserialization of untrusted data in Microsoft Dataverse allows an unauthorized attacker to execute code over a network.

Missing authorization in Azure Event Grid allows an authorized attacker to perform spoofing over a network.

Exposure of sensitive information to an unauthorized actor in Azure API Center allows an unauthorized attacker to disclose information over a network.

A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.

When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU.

The HTTP/2 server can refund connection-level flow control twice for the same data: once when a client resets a stream, and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection).

Historically, the HTTP/2 implementation has been rather lax about malformed framing-related headers, as they cannot interfere with HTTP/2 framing. However, this makes it possible to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.

When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits.

Missing authentication for a critical function in Azure App Service allows an unauthorized attacker to execute code over a network.

Missing authorization in Azure SRE Agent allows an authorized attacker to elevate privileges over a network.

When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request.

On Windows, when the target of Root.Mkdir or Root.MkdirAll is a junction pointing to an empty location, the operation can create a directory at the junction target even when that target is located outside the root. This only applies to operations where the last path component is a junction (path/to/junction, but not path/junction/target).

SumatraPDF 3.6.1 and earlier embeds selected or pasted translation text in quoted Windows command lines in src/SelectionTranslate.cpp using incomplete quote-only escaping. The affected BuildGrokTranslateCmdLineTemp(), BuildClaudeTranslateCmdLineTemp(), and BuildCodexTranslateCmdLineTemp() functions can allow attacker-controlled text to inject model, working-directory, approval, or sandbox-bypass flags when the corresponding agentic CLI backend is installed and used.

SumatraPDF 3.6.1 and earlier has a vulnerability in ChmFile::GetCharZ() where file-controlled unsigned offsets are narrowed to signed integers without a lower-bound check. This can cause reads before the /#STRINGS buffer and deterministic application termination.

SumatraPDF 3.6.1 and earlier, and pre-release 3.7.0.20369 when WebView2 is absent, has a vulnerability in ParseProtoUrl() where the signed host component of an its:// URL is used as an index into gHtmlWindows. This can cause out-of-bounds pointer read and invalid callback dereference, terminating the process.

SumatraPDF 3.6.1 and earlier has a vulnerability in MaybeFlipBitmap() where GDI+ reads the attacker-controlled PropertyTagOrientation size into a fixed 64-byte stack buffer. Opening a crafted TIFF can overwrite stack control data, though tested builds terminate via stack cookie check.