     stdlib 1.27.1 (golang)
pkg:golang/stdlib@1.27.1
# api-server.Dockerfile (36:36)
COPY --from=build /app /bin/app
| Affected range | >=1.27.0-0
<1.27.2
| | Fixed version | 1.27.2 | | EPSS Score | 0.493% | | EPSS Percentile | 41st percentile |
Description
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).
| Affected range | >=1.27.0-0
<1.27.2
| | Fixed version | 1.27.2 | | EPSS Score | 0.574% | | EPSS Percentile | 46th percentile |
Description
The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the 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). Total buffered data is still limited by the concurrent stream limit and stream-level flow control.
| Affected range | >=1.27.0-0
<1.27.2
| | Fixed version | 1.27.2 | | EPSS Score | 0.394% | | EPSS Percentile | 32nd percentile |
Description
Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references.
We now reject these as malformed and curb the memory amplification vector as a result.
| Affected range | >=1.27.0-0
<1.27.2
| | Fixed version | 1.27.2 | | EPSS Score | 0.404% | | EPSS Percentile | 33rd percentile |
Description
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.
| Affected range | >=1.27.0-0
<1.27.2
| | Fixed version | 1.27.2 | | EPSS Score | 0.315% | | EPSS Percentile | 23rd percentile |
Description
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 an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP.
The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP.
| Affected range | >=1.27.0-0
<1.27.2
| | Fixed version | 1.27.2 | | EPSS Score | 0.568% | | EPSS Percentile | 45th percentile |
Description
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.
| Affected range | >=1.27.0-0
<1.27.2
| | Fixed version | 1.27.2 | | EPSS Score | 0.379% | | EPSS Percentile | 30th percentile |
Description
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.
| Affected range | >=1.27.0-0
<1.27.2
| | Fixed version | 1.27.2 | | EPSS Score | 0.303% | | EPSS Percentile | 21st percentile |
Description
Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation 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.
| Affected range | >=1.27.0-0
<1.27.2
| | Fixed version | 1.27.2 | | EPSS Score | 0.570% | | EPSS Percentile | 46th percentile |
Description
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. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently.
| Affected range | >=1.27.0-0
<1.27.2
| | Fixed version | 1.27.2 | | EPSS Score | 0.309% | | EPSS Percentile | 22nd percentile |
Description
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. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.
| Affected range | >=1.27.0-0
<1.27.2
| | Fixed version | 1.27.2 | | EPSS Score | 0.181% | | EPSS Percentile | 7th percentile |
Description
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
| Affected range | >=1.27.0-0
<1.27.2
| | Fixed version | 1.27.2 | | EPSS Score | 0.181% | | EPSS Percentile | 7th percentile |
Description
A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped.
We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.
| Affected range | >=1.27.0-0
<1.27.2
| | Fixed version | 1.27.2 | | EPSS Score | 0.181% | | EPSS Percentile | 7th percentile |
Description
When a JavaScript template literal contains consecutive expressions, the context tracking state was not properly reset upon entering a new expression.
We now ensure that template-literal expression entries correctly reset context variables so all subsequent regular expression literals are accurately recognized and escaped.
|
   golang.org/x/net 0.58.0 (golang)
pkg:golang/golang.org/x/net@0.58.0
# api-server.Dockerfile (36:36)
COPY --from=build /app /bin/app
| Affected range | <0.60.0 | | Fixed version | 0.60.0 | | EPSS Score | 0.574% | | EPSS Percentile | 46th percentile |
Description
The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the 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). Total buffered data is still limited by the concurrent stream limit and stream-level flow control.
| Affected range | <0.60.0 | | Fixed version | 0.60.0 | | EPSS Score | 0.568% | | EPSS Percentile | 45th percentile |
Description
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.
| Affected range | <0.60.0 | | Fixed version | 0.60.0 | | EPSS Score | 0.303% | | EPSS Percentile | 21st percentile |
Description
Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation 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.
| Affected range | <0.60.0 | | Fixed version | 0.60.0 | | EPSS Score | 0.570% | | EPSS Percentile | 46th percentile |
Description
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. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently.
| Affected range | <0.60.0 | | Fixed version | 0.60.0 | | EPSS Score | 0.181% | | EPSS Percentile | 7th percentile |
Description
HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.
|
  libexpat 2.8.5-r0 (apk)
pkg:apk/alpine/libexpat@2.8.5-r0?arch=aarch64&distro=alpine-3.24.2&upstream=expat
# api-server.Dockerfile (34:34)
RUN apk --no-cache upgrade && apk --no-cache add ca-certificates libssl3 git
| Affected range | <2.9.0-r0 | | Fixed version | 2.9.0-r0 | | EPSS Score | 0.549% | | EPSS Percentile | 44th percentile |
Description
| Affected range | <2.9.0-r0 | | Fixed version | 2.9.0-r0 | | EPSS Score | 0.348% | | EPSS Percentile | 26th percentile |
Description |
 zlib 1.3.2-r0 (apk)
pkg:apk/alpine/zlib@1.3.2-r0?arch=aarch64&distro=alpine-3.24.2
# api-server.Dockerfile (33:33)
FROM ${ALPINE_IMAGE}
| Affected range | <1.3.2-r1 | | Fixed version | 1.3.2-r1 | | EPSS Score | 0.356% | | EPSS Percentile | 27th percentile |
Description |
github.com/docker/cli 29.7.2+incompatible (golang)
pkg:golang/github.com/docker/cli@29.7.2%2Bincompatible
# api-server.Dockerfile (36:36)
COPY --from=build /app /bin/app
| Affected range | >=19.03.0+incompatible | | Fixed version | Not Fixed | | EPSS Score | 0.490% | | EPSS Percentile | 40th percentile |
Description
Docker CLI Plugins: Uncontrolled Search Path Element Leads to Local Privilege Escalation on Windows in github.com/docker/cli
|
 golang.org/x/crypto 0.57.0 (golang)
pkg:golang/golang.org/x/crypto@0.57.0
# api-server.Dockerfile (36:36)
COPY --from=build /app /bin/app
| Affected range | >=0 | | Fixed version | Not Fixed |
Description
The golang.org/x/crypto/openpgp package is unsafe by design, has numerous known security issues, is not maintained, and should not be used.
If you are required to interoperate with OpenPGP systems and need a maintained package, consider github.com/ProtonMail/go-crypto/openpgp which is a maintained fork that aims to be a drop-in replacement for this package.
|
github.com/chrismellard/docker-credential-acr-env 0.0.0-20230304212654-82a0ddb27589 (golang)
pkg:golang/github.com/chrismellard/docker-credential-acr-env@0.0.0-20230304212654-82a0ddb27589
# api-server.Dockerfile (36:36)
COPY --from=build /app /bin/app
| Affected range | >=0 | | Fixed version | Not Fixed |
Description
In github.com/chrismellard/docker-credential-acr-env/pkg/credhelper, the regular expression used by isACRRegistry to validate Azure Container Registry hostnames is unanchored. As a result, arbitrary hostnames containing the substring ".azurecr.io" (such as evil.azurecr.io.attacker.com) are treated as valid ACR registries, causing ACRCredHelper.Get to send the Azure Active Directory (AAD) access token to attacker-controlled hosts.
|
