    stdlib 1.24.2 (golang)
pkg:golang/stdlib@1.24.2
# 2.11.x/alpine3.21/Dockerfile (5:26)
RUN set -eux; \
apkArch="$(apk --print-arch)"; \
case "$apkArch" in \
aarch64) natsArch='arm64'; sha256='24a56aa64219aa6668a18e2d0ea9108d72472852e47677b384c856fc412ae4c7' ;; \
armhf) natsArch='arm6'; sha256='86fe21d7413b6c7ce68250c0645567b0550eacf2a18eea56374630c83f0f1a76' ;; \
armv7) natsArch='arm7'; sha256='1832b4f0e105a01b0366ea2e3071aa235870067f0d042db2ff4dfdb6ceb673a8' ;; \
x86_64) natsArch='amd64'; sha256='9cdab8b2e2488128caee6519e2f15f1aa33a78b4386ee1776a06b4818d7ec197' ;; \
x86) natsArch='386'; sha256='9173707ded6d71210c5e0eb9a29f3979888a7e658d52cb8fe32b7e498a852143' ;; \
s390x) natsArch='s390x'; sha256='61de816adafa99fbe7130ee77a350fd44f7c97c51bc28a210e0a53c0ced1621f' ;; \
ppc64le) natsArch='ppc64le'; sha256='5b1a2ea2bcd68d0751dd718ce434a7c57161415c202e5723191891360b1e5fd7' ;; \
*) echo >&2 "error: $apkArch is not supported!"; exit 1 ;; \
esac; \
\
wget -O nats-server.tar.gz "https://github.com/nats-io/nats-server/releases/download/v${NATS_SERVER}/nats-server-v${NATS_SERVER}-linux-${natsArch}.tar.gz"; \
echo "${sha256} *nats-server.tar.gz" | sha256sum -c -; \
\
apk add --no-cache ca-certificates tzdata; \
\
tar -xf nats-server.tar.gz; \
rm nats-server.tar.gz; \
mv "nats-server-v${NATS_SERVER}-linux-${natsArch}/nats-server" /usr/local/bin; \
rm -rf "nats-server-v${NATS_SERVER}-linux-${natsArch}";
| Affected range | <1.24.11 | | Fixed version | 1.24.11 | | EPSS Score | 0.017% | | EPSS Percentile | 3rd percentile |
Description
Within HostnameError.Error(), when constructing an error string, there is no limit to the number of hosts that will be printed out. Furthermore, the error string is constructed by repeated string concatenation, leading to quadratic runtime. Therefore, a certificate provided by a malicious actor can result in excessive resource consumption.
| Affected range | <1.24.12 | | Fixed version | 1.24.12 | | EPSS Score | 0.030% | | EPSS Percentile | 8th percentile |
Description
The net/url package does not set a limit on the number of query parameters in a query.
While the maximum size of query parameters in URLs is generally limited by the maximum request header size, the net/http.Request.ParseForm method can parse large URL-encoded forms. Parsing a large form containing many unique query parameters can cause excessive memory consumption.
| Affected range | <1.24.8 | | Fixed version | 1.24.8 | | EPSS Score | 0.031% | | EPSS Percentile | 8th percentile |
Description
The ParseAddress function constructs domain-literal address components through repeated string concatenation. When parsing large domain-literal components, this can cause excessive CPU consumption.
| Affected range | <1.24.8 | | Fixed version | 1.24.8 | | EPSS Score | 0.038% | | EPSS Percentile | 11th percentile |
Description
The processing time for parsing some invalid inputs scales non-linearly with respect to the size of the input.
This affects programs which parse untrusted PEM inputs.
| Affected range | <1.24.8 | | Fixed version | 1.24.8 | | EPSS Score | 0.018% | | EPSS Percentile | 4th percentile |
Description
Validating certificate chains which contain DSA public keys can cause programs to panic, due to a interface cast that assumes they implement the Equal method.
This affects programs which validate arbitrary certificate chains.
| Affected range | <1.24.9 | | Fixed version | 1.24.9 | | EPSS Score | 0.018% | | EPSS Percentile | 4th percentile |
Description
Due to the design of the name constraint checking algorithm, the processing time of some inputs scale non-linearly with respect to the size of the certificate.
This affects programs which validate arbitrary certificate chains.
| Affected range | >=1.24.0-0
<1.24.4
| | Fixed version | 1.24.4 | | EPSS Score | 0.016% | | EPSS Percentile | 3rd percentile |
Description
Calling Verify with a VerifyOptions.KeyUsages that contains ExtKeyUsageAny unintentionally disabledpolicy validation. This only affected certificate chains which contain policy graphs, which are rather uncommon.
| Affected range | >=1.24.0-0
<1.24.4
| | Fixed version | 1.24.4 | | EPSS Score | 0.011% | | EPSS Percentile | 1st percentile |
Description
Proxy-Authorization and Proxy-Authenticate headers persisted on cross-origin redirects potentially leaking sensitive information.
| Affected range | <1.24.12 | | Fixed version | 1.24.12 | | EPSS Score | 0.022% | | EPSS Percentile | 5th percentile |
Description
archive/zip uses a super-linear file name indexing algorithm that is invoked the first time a file in an archive is opened. This can lead to a denial of service when consuming a maliciously constructed ZIP archive.
| Affected range | <1.24.11 | | Fixed version | 1.24.11 | | EPSS Score | 0.010% | | EPSS Percentile | 1st percentile |
Description
An excluded subdomain constraint in a certificate chain does not restrict the usage of wildcard SANs in the leaf certificate. For example a constraint that excludes the subdomain test.example.com does not prevent a leaf certificate from claiming the SAN *.example.com.
| Affected range | >=1.24.0
<1.24.6
| | Fixed version | 1.24.6 | | EPSS Score | 0.020% | | EPSS Percentile | 4th percentile |
Description
If the PATH environment variable contains paths which are executables (rather than just directories), passing certain strings to LookPath ("", ".", and ".."), can result in the binaries listed in the PATH being unexpectedly returned.
| Affected range | >=1.24.0-0
<1.24.4
| | Fixed version | 1.24.4 | | EPSS Score | 0.009% | | EPSS Percentile | 1st percentile |
Description
os.OpenFile(path, os.O_CREATE|O_EXCL) behaved differently on Unix and Windows systems when the target path was a dangling symlink. On Unix systems, OpenFile with O_CREATE and O_EXCL flags never follows symlinks. On Windows, when the target path was a symlink to a nonexistent location, OpenFile would create a file in that location. OpenFile now always returns an error when the O_CREATE and O_EXCL flags are both set and the target path is a symlink.
| Affected range | <1.24.12 | | Fixed version | 1.24.12 | | EPSS Score | 0.024% | | EPSS Percentile | 6th percentile |
Description
During the TLS 1.3 handshake if multiple messages are sent in records that span encryption level boundaries (for instance the Client Hello and Encrypted Extensions messages), the subsequent messages may be processed before the encryption level changes. This can cause some minor information disclosure if a network-local attacker can inject messages during the handshake.
| Affected range | <1.24.8 | | Fixed version | 1.24.8 | | EPSS Score | 0.022% | | EPSS Percentile | 5th percentile |
Description
The Reader.ReadResponse function constructs a response string through repeated string concatenation of lines. When the number of lines in a response is large, this can cause excessive CPU consumption.
| Affected range | <1.24.8 | | Fixed version | 1.24.8 | | EPSS Score | 0.014% | | EPSS Percentile | 2nd percentile |
Description
When Conn.Handshake fails during ALPN negotiation the error contains attacker controlled information (the ALPN protocols sent by the client) which is not escaped.
| Affected range | <1.24.8 | | Fixed version | 1.24.8 | | EPSS Score | 0.030% | | EPSS Percentile | 8th percentile |
Description
Despite HTTP headers having a default limit of 1MB, the number of cookies that can be parsed does not have a limit. By sending a lot of very small cookies such as "a=;", an attacker can make an HTTP server allocate a large amount of structs, causing large memory consumption.
| Affected range | <1.24.8 | | Fixed version | 1.24.8 | | EPSS Score | 0.032% | | EPSS Percentile | 9th percentile |
Description
Parsing a maliciously crafted DER payload could allocate large amounts of memory, causing memory exhaustion.
| Affected range | <1.24.8 | | Fixed version | 1.24.8 | | EPSS Score | 0.032% | | EPSS Percentile | 9th percentile |
Description
The Parse function permits values other than IPv6 addresses to be included in square brackets within the host component of a URL. RFC 3986 permits IPv6 addresses to be included within the host component, enclosed within square brackets. For example: "http://[::1]/". IPv4 addresses and hostnames must not appear within square brackets. Parse did not enforce this requirement.
| Affected range | <1.24.13 | | Fixed version | 1.24.13 |
Description
During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between the initial handshake and the resumed handshake, the resumed handshake may succeed when it should have failed. This may happen when a user calls Config.Clone and mutates the returned Config, or uses Config.GetConfigForClient. This can cause a client to resume a session with a server that it would not have resumed with during the initial handshake, or cause a server to resume a session with a client that it would not have resumed with during the initial handshake.
| Affected range | <1.24.8 | | Fixed version | 1.24.8 | | EPSS Score | 0.016% | | EPSS Percentile | 3rd percentile |
Description
tar.Reader does not set a maximum size on the number of sparse region data blocks in GNU tar pax 1.0 sparse files. A maliciously-crafted archive containing a large number of sparse regions can cause a Reader to read an unbounded amount of data from the archive into memory. When reading from a compressed source, a small compressed input can result in large allocations.
| Affected range | >=1.24.0-0
<1.24.3
| | Fixed version | 1.24.3 | | EPSS Score | 0.005% | | EPSS Percentile | 0th percentile |
Description
It was possible to improperly access the parent directory of an os.Root by opening a filename ending in "../". For example, Root.Open("../") would open the parent directory of the Root. This escape only permits opening the parent directory itself, not ancestors of the parent or files contained within the parent.
|
openssl 
busybox 
