    stdlib 1.25.0 (golang)
pkg:golang/stdlib@1.25.0
# minio-release.dockerfile (76:76)
COPY --from=build /build/mc/mc /opt/bitnami/common/bin/mc
| Affected range | >=1.25.0
<1.25.5
| | Fixed version | 1.25.5 | | 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.25.0
<1.25.6
| | Fixed version | 1.25.6 | | EPSS Score | 0.023% | | EPSS Percentile | 5th 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.25.0
<1.25.2
| | Fixed version | 1.25.2 | | 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.25.0
<1.25.2
| | Fixed version | 1.25.2 | | 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.25.0
<1.25.2
| | Fixed version | 1.25.2 | | 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.25.0
<1.25.3
| | Fixed version | 1.25.3 | | 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.25.0
<1.25.6
| | Fixed version | 1.25.6 | | EPSS Score | 0.015% | | EPSS Percentile | 3rd 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.25.0
<1.25.5
| | Fixed version | 1.25.5 | | 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.25.0
<1.25.1
| | Fixed version | 1.25.1 | | EPSS Score | 0.008% | | EPSS Percentile | 1st percentile |
Description
When using http.CrossOriginProtection, the AddInsecureBypassPattern method can unexpectedly bypass more requests than intended. CrossOriginProtection then skips validation, but forwards the original request path, which may be served by a different handler without the intended security protections.
| Affected range | >=1.25.0
<1.25.6
| | Fixed version | 1.25.6 | | EPSS Score | 0.008% | | EPSS Percentile | 1st 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.25.0
<1.25.2
| | Fixed version | 1.25.2 | | 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.25.0
<1.25.2
| | Fixed version | 1.25.2 | | 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.25.0
<1.25.2
| | Fixed version | 1.25.2 | | 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.25.0
<1.25.2
| | Fixed version | 1.25.2 | | 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.25.0
<1.25.2
| | Fixed version | 1.25.2 | | 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.25.0
<1.25.2
| | Fixed version | 1.25.2 | | 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.
|
   openssl 3.0.17-1~deb12u3 (deb)
pkg:deb/debian/openssl@3.0.17-1~deb12u3?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (53:59)
RUN apt-get update && apt-get install -y --no-install-recommends \
ca-certificates \
jq \
curl \
procps \
bash \
&& rm -rf /var/lib/apt/lists/*
| Affected range | <3.0.18-1~deb12u2 | | Fixed version | 3.0.18-1~deb12u2 | | EPSS Score | 0.032% | | EPSS Percentile | 9th percentile |
Description
Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function. Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files. The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. Exploiting this issue requires an attacker to provide a malformed PKCS#12 file to an application that processes it. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
| Affected range | <3.0.18-1~deb12u2 | | Fixed version | 3.0.18-1~deb12u2 | | EPSS Score | 0.086% | | EPSS Percentile | 25th percentile |
Description
Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file. Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service. The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash. Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity. The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this issue.
| Affected range | <3.0.18-1~deb12u2 | | Fixed version | 3.0.18-1~deb12u2 | | EPSS Score | 0.057% | | EPSS Percentile | 18th percentile |
Description
Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer. Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service. The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer. The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this issue.
| Affected range | <3.0.18-1~deb12u2 | | Fixed version | 3.0.18-1~deb12u2 | | EPSS Score | 0.018% | | EPSS Percentile | 4th percentile |
Description
Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file. Impact summary: An application processing a malformed PKCS#12 file can be caused to dereference an invalid or NULL pointer on memory read, resulting in a Denial of Service. A type confusion vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid pointer read. The location is constrained to a 1-byte address space, meaning any attempted pointer manipulation can only target addresses between 0x00 and 0xFF. This range corresponds to the zero page, which is unmapped on most modern operating systems and will reliably result in a crash, leading only to a Denial of Service. Exploiting this issue also requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For these reasons, the issue was assessed as Low severity. The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue. OpenSSL 1.0.2 is not affected by this issue.
| Affected range | <3.0.18-1~deb12u2 | | Fixed version | 3.0.18-1~deb12u2 | | EPSS Score | 0.087% | | EPSS Percentile | 25th percentile |
Description
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data. Impact summary: An application performing signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service. The function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash. Exploiting this vulnerability requires an attacker to provide a malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons the issue was assessed as Low severity. The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
| Affected range | <3.0.18-1~deb12u2 | | Fixed version | 3.0.18-1~deb12u2 | | EPSS Score | 0.014% | | EPSS Percentile | 2nd percentile |
Description
Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write. Impact summary: This out-of-bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service for an application. The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in TLS/SSL data paths. In OpenSSL command-line applications, it is typically only pushed onto stdout/stderr on VMS systems. Third-party applications that explicitly use this filter with a BIO chain that can short-write and that write large, newline-free data influenced by an attacker would be affected. However, the circumstances where this could happen are unlikely to be under attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated data controlled by an attacker. For that reason the issue was assessed as Low severity. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the BIO implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.
| Affected range | <3.0.18-1~deb12u2 | | Fixed version | 3.0.18-1~deb12u2 | | EPSS Score | 0.005% | | EPSS Percentile | 0th percentile |
Description
Issue summary: When using the low-level OCB API directly with AES-NI or
other hardware-accelerated code paths, inputs whose length is not a multiple
of 16 bytes can leave the final partial block unencrypted and unauthenticated.
Impact summary: The trailing 1-15 bytes of a message may be exposed in
cleartext on encryption and are not covered by the authentication tag,
allowing an attacker to read or tamper with those bytes without detection.
The low-level OCB encrypt and decrypt routines in the hardware-accelerated
stream path process full 16-byte blocks but do not advance the input/output
pointers. The subsequent tail-handling code then operates on the original
base pointers, effectively reprocessing the beginning of the buffer while
leaving the actual trailing bytes unprocessed. The authentication checksum
also excludes the true tail bytes.
However, typical OpenSSL consumers using EVP are not affected because the
higher-level EVP and provider OCB implementations split inputs so that full
blocks and trailing partial blocks are processed in separate calls, avoiding
the problematic code path. Additionally, TLS does not use OCB ciphersuites.
The vulnerability only affects applications that call the low-level
CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with
non-block-aligned lengths in a single call on hardware-accelerated builds.
For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected
by this issue, as OCB mode is not a FIPS-approved algorithm.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.
| Affected range | <=3.0.18-1~deb12u1 | | Fixed version | Not Fixed | | EPSS Score | 0.046% | | EPSS Percentile | 14th percentile |
Description
OpenSSL 3.0.0 through 3.3.2 on the PowerPC architecture is vulnerable to a Minerva attack, exploitable by measuring the time of signing of random messages using the EVP_DigestSign API, and then using the private key to extract the K value (nonce) from the signatures. Next, based on the bit size of the extracted nonce, one can compare the signing time of full-sized nonces to signatures that used smaller nonces, via statistical tests. There is a side-channel in the P-364 curve that allows private key extraction (also, there is a dependency between the bit size of K and the size of the side channel). NOTE: This CVE is disputed because the OpenSSL security policy explicitly notes that any side channels which require same physical system to be detected are outside of the threat model for the software. The timing signal is so small that it is infeasible to be detected without having the attacking process running on the same physical system.
| Affected range | <3.0.18-1~deb12u2 | | Fixed version | 3.0.18-1~deb12u2 | | EPSS Score | 0.387% | | EPSS Percentile | 59th percentile |
Description
Issue summary: Parsing CMS AuthEnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow. Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution. When parsing CMS AuthEnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack-based out-of-bounds write before any authentication or tag verification occurs. Applications and services that parse untrusted CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable. Because the overflow occurs prior to authentication, no valid key material is required to trigger it. While exploitability to remote code execution depends on platform and toolchain mitigations, the stack-based write primitive represents a severe risk. The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary. OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue. OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.
| Affected range | >=3.0.11-1~deb12u2 | | Fixed version | Not Fixed | | EPSS Score | 0.094% | | EPSS Percentile | 27th percentile |
Description |
  stdlib 1.25.3 (golang)
pkg:golang/stdlib@1.25.3
# minio-release.dockerfile (76:76)
COPY --from=build /build/mc/mc /opt/bitnami/common/bin/mc
| Affected range | >=1.25.0
<1.25.5
| | Fixed version | 1.25.5 | | 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.25.0
<1.25.6
| | Fixed version | 1.25.6 | | EPSS Score | 0.023% | | EPSS Percentile | 5th 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.25.0
<1.25.6
| | Fixed version | 1.25.6 | | EPSS Score | 0.015% | | EPSS Percentile | 3rd 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.25.0
<1.25.5
| | Fixed version | 1.25.5 | | 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.25.0
<1.25.6
| | Fixed version | 1.25.6 | | EPSS Score | 0.008% | | EPSS Percentile | 1st 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.
|
  golang.org/x/crypto 0.37.0 (golang)
pkg:golang/golang.org/x/crypto@0.37.0
# minio-release.dockerfile (80:80)
COPY --from=build /build/minio/minio /opt/bitnami/common/bin/minio
| Affected range | <0.43.0 | | Fixed version | 0.43.0 | | EPSS Score | 0.033% | | EPSS Percentile | 9th percentile |
Description
SSH clients receiving SSH_AGENT_SUCCESS when expecting a typed response will panic and cause early termination of the client process.
 Allocation of Resources Without Limits or Throttling
| Affected range | <0.45.0 | | Fixed version | 0.45.0 | | CVSS Score | 5.3 | | CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | | EPSS Score | 0.083% | | EPSS Percentile | 24th percentile |
Description
SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption.
 Out-of-bounds Read
| Affected range | <0.45.0 | | Fixed version | 0.45.0 | | CVSS Score | 5.3 | | CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | | EPSS Score | 0.018% | | EPSS Percentile | 4th percentile |
Description
SSH Agent servers do not validate the size of messages when processing new identity requests, which may cause the program to panic if the message is malformed due to an out of bounds read.
|
golang.org/x/crypto 0.40.0 (golang)
pkg:golang/golang.org/x/crypto@0.40.0
# minio-release.dockerfile (76:76)
COPY --from=build /build/mc/mc /opt/bitnami/common/bin/mc
| Affected range | <0.43.0 | | Fixed version | 0.43.0 | | EPSS Score | 0.033% | | EPSS Percentile | 9th percentile |
Description
SSH clients receiving SSH_AGENT_SUCCESS when expecting a typed response will panic and cause early termination of the client process.
Allocation of Resources Without Limits or Throttling
| Affected range | <0.45.0 | | Fixed version | 0.45.0 | | CVSS Score | 5.3 | | CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | | EPSS Score | 0.083% | | EPSS Percentile | 24th percentile |
Description
SSH servers parsing GSSAPI authentication requests do not validate the number of mechanisms specified in the request, allowing an attacker to cause unbounded memory consumption.
Out-of-bounds Read
| Affected range | <0.45.0 | | Fixed version | 0.45.0 | | CVSS Score | 5.3 | | CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | | EPSS Score | 0.018% | | EPSS Percentile | 4th percentile |
Description
SSH Agent servers do not validate the size of messages when processing new identity requests, which may cause the program to panic if the message is malformed due to an out of bounds read.
|
 pam 1.5.2-6+deb12u1 (deb)
pkg:deb/debian/pam@1.5.2-6%2Bdeb12u1?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (36:36)
FROM debian:bookworm-slim
| Affected range | <1.5.2-6+deb12u2 | | Fixed version | 1.5.2-6+deb12u2 | | EPSS Score | 0.030% | | EPSS Percentile | 8th percentile |
Description
A flaw was found in linux-pam. The module pam_namespace may use access user-controlled paths without proper protection, allowing local users to elevate their privileges to root via multiple symlink attacks and race conditions.
[experimental] - pam 1.7.0-4
| Affected range | <1.5.2-6+deb12u2 | | Fixed version | 1.5.2-6+deb12u2 | | EPSS Score | 0.084% | | EPSS Percentile | 24th percentile |
Description
linux-pam (aka Linux PAM) before 1.6.0 allows attackers to cause a denial of service (blocked login process) via mkfifo because the openat call (for protect_dir) lacks O_DIRECTORY.
[experimental] - pam 1.5.3-2
|
  gnupg2 2.2.40-1.1+deb12u1 (deb)
pkg:deb/debian/gnupg2@2.2.40-1.1%2Bdeb12u1?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (36:36)
FROM debian:bookworm-slim
| Affected range | <2.2.40-1.1+deb12u2 | | Fixed version | 2.2.40-1.1+deb12u2 | | EPSS Score | 0.019% | | EPSS Percentile | 4th percentile |
Description
In GnuPG before 2.4.9, armor_filter in g10/armor.c has two increments of an index variable where one is intended, leading to an out-of-bounds write for crafted input. (For ExtendedLTS, 2.2.51 and later are fixed versions.)
| Affected range | <=2.2.40-1.1+deb12u2 | | Fixed version | Not Fixed | | EPSS Score | 0.019% | | EPSS Percentile | 4th percentile |
Description
GnuPG can be made to spin on a relatively small input by (for example) crafting a public key with thousands of signatures attached, compressed down to just a few KB.
|
 tar 1.34+dfsg-1.2+deb12u1 (deb)
pkg:deb/debian/tar@1.34%2Bdfsg-1.2%2Bdeb12u1?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (36:36)
FROM debian:bookworm-slim
| Affected range | >=1.34+dfsg-1.2+deb12u1 | | Fixed version | Not Fixed | | EPSS Score | 0.060% | | EPSS Percentile | 19th percentile |
Description
GNU Tar through 1.35 allows file overwrite via directory traversal in crafted TAR archives, with a certain two-step process. First, the victim must extract an archive that contains a ../ symlink to a critical directory. Second, the victim must extract an archive that contains a critical file, specified via a relative pathname that begins with the symlink name and ends with that critical file's name. Here, the extraction follows the symlink and overwrites the critical file. This bypasses the protection mechanism of "Member name contains '..'" that would occur for a single TAR archive that attempted to specify the critical file via a ../ approach. For example, the first archive can contain "x -> ../../../../../home/victim/.ssh" and the second archive can contain x/authorized_keys. This can affect server applications that automatically extract any number of user-supplied TAR archives, and were relying on the blocking of traversal. This can also affect software installation processes in which "tar xf" is run more than once (e.g., when installing a package can automatically install two dependencies that are set up as untrusted tarballs instead of official packages).
Disputed tar issue, works as documented per upstream:
https://lists.gnu.org/archive/html/bug-tar/2025-08/msg00012.html
https://github.com/i900008/vulndb/blob/main/Gnu_tar_vuln.md
| Affected range | <=1.34+dfsg-1.2+deb12u1 | | Fixed version | Not Fixed | | EPSS Score | 2.806% | | EPSS Percentile | 86th percentile |
Description
Tar 1.15.1 does not properly warn the user when extracting setuid or setgid files, which may allow local users or remote attackers to gain privileges.
This is intended behaviour, after all tar is an archiving tool and you
need to give -p as a command line flag
|
github.com/eclipse/paho.mqtt.golang 1.5.0 (golang)
pkg:golang/github.com/eclipse/paho.mqtt.golang@1.5.0
# minio-release.dockerfile (80:80)
COPY --from=build /build/minio/minio /opt/bitnami/common/bin/minio
 Numeric Truncation Error
| Affected range | <1.5.1 | | Fixed version | 1.5.1 | | CVSS Score | 6.3 | | CVSS Vector | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N | | EPSS Score | 0.039% | | EPSS Percentile | 11th percentile |
Description
In Eclipse Paho Go MQTT v3.1 library (paho.mqtt.golang) versions <=1.5.0 UTF-8 encoded strings, passed into the library, may be incorrectly encoded if their length exceeds 65535 bytes. This may lead to unexpected content in packets sent to the server (for example, part of an MQTT topic may leak into the message body in a PUBLISH packet).
The issue arises because the length of the data passed in was converted from an int64/int32 (depending upon CPU) to an int16 without checks for overflows. The int16 length was then written, followed by the data (e.g. topic). This meant that when the data (e.g. topic) was over 65535 bytes then the amount of data written exceeds what the length field indicates. This could lead to a corrupt packet, or mean that the excess data leaks into another field (e.g. topic leaks into message body).
|
 glibc 2.36-9+deb12u13 (deb)
pkg:deb/debian/glibc@2.36-9%2Bdeb12u13?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (36:36)
FROM debian:bookworm-slim
| Affected range | <=2.36-9+deb12u13 | | Fixed version | Not Fixed | | EPSS Score | 0.841% | | EPSS Percentile | 74th percentile |
Description
In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(|)(\1\1)*' in grep, a different issue than CVE-2018-20796. NOTE: the software maintainer disputes that this is a vulnerability because the behavior occurs only with a crafted pattern
| Affected range | <=2.36-9+deb12u13 | | Fixed version | Not Fixed | | EPSS Score | 1.239% | | EPSS Percentile | 79th percentile |
Description
GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may guess the heap addresses of pthread_created thread. The component is: glibc. NOTE: the vendor's position is "ASLR bypass itself is not a vulnerability.
| Affected range | <=2.36-9+deb12u13 | | Fixed version | Not Fixed | | EPSS Score | 0.646% | | EPSS Percentile | 70th percentile |
Description
GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass ASLR using cache of thread stack and heap. The component is: glibc. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
| Affected range | <=2.36-9+deb12u13 | | Fixed version | Not Fixed | | EPSS Score | 0.313% | | EPSS Percentile | 54th percentile |
Description
GNU Libc current is affected by: Re-mapping current loaded library with malicious ELF file. The impact is: In worst case attacker may evaluate privileges. The component is: libld. The attack vector is: Attacker sends 2 ELF files to victim and asks to run ldd on it. ldd execute code. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
| Affected range | <=2.36-9+deb12u13 | | Fixed version | Not Fixed | | EPSS Score | 0.131% | | EPSS Percentile | 33rd percentile |
Description
GNU Libc current is affected by: Mitigation bypass. The impact is: Attacker may bypass stack guard protection. The component is: nptl. The attack vector is: Exploit stack buffer overflow vulnerability and use this bypass vulnerability to bypass stack guard. NOTE: Upstream comments indicate "this is being treated as a non-security bug and no real threat.
| Affected range | <=2.36-9+deb12u13 | | Fixed version | Not Fixed | | EPSS Score | 1.492% | | EPSS Percentile | 81st percentile |
Description
In the GNU C Library (aka glibc or libc6) through 2.29, check_dst_limits_calc_pos_1 in posix/regexec.c has Uncontrolled Recursion, as demonstrated by '(\227|)(\1\1|t1|\\2537)+' in grep.
| Affected range | <=2.36-9+deb12u13 | | Fixed version | Not Fixed | | EPSS Score | 0.394% | | EPSS Percentile | 60th percentile |
Description
The glob implementation in the GNU C Library (aka glibc or libc6) allows remote authenticated users to cause a denial of service (CPU and memory consumption) via crafted glob expressions that do not match any pathnames, as demonstrated by glob expressions in STAT commands to an FTP daemon, a different vulnerability than CVE-2010-2632.
- glibc (unimportant)
- eglibc (unimportant)
That's standard POSIX behaviour implemented by (e)glibc. Applications using
glob need to impose limits for themselves
|
 curl 7.88.1-10+deb12u14 (deb)
pkg:deb/debian/curl@7.88.1-10%2Bdeb12u14?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (53:59)
RUN apt-get update && apt-get install -y --no-install-recommends \
ca-certificates \
jq \
curl \
procps \
bash \
&& rm -rf /var/lib/apt/lists/*
| Affected range | <=7.88.1-10+deb12u14 | | Fixed version | Not Fixed | | EPSS Score | 0.059% | | EPSS Percentile | 18th percentile |
Description
When doing SSH-based transfers using either SCP or SFTP, and asked to do public key authentication, curl would wrongly still ask and authenticate using a locally running SSH agent.
| Affected range | <=7.88.1-10+deb12u14 | | Fixed version | Not Fixed | | EPSS Score | 0.031% | | EPSS Percentile | 9th percentile |
Description
When doing SSH-based transfers using either SCP or SFTP, and setting the known_hosts file, libcurl could still mistakenly accept connecting to hosts not present in the specified file if they were added as recognized in the libssh global known_hosts file.
| Affected range | <=7.88.1-10+deb12u14 | | Fixed version | Not Fixed | | EPSS Score | 0.007% | | EPSS Percentile | 0th percentile |
Description
When doing multi-threaded LDAPS transfers (LDAP over TLS) with libcurl, changing TLS options in one thread would inadvertently change them globally and therefore possibly also affect other concurrently setup transfers. Disabling certificate verification for a specific transfer could unintentionally disable the feature for other threads as well.
| Affected range | <=7.88.1-10+deb12u14 | | Fixed version | Not Fixed | | EPSS Score | 0.039% | | EPSS Percentile | 11th percentile |
Description
curl's code for managing SSH connections when SFTP was done using the wolfSSH powered backend was flawed and missed host verification mechanisms. This prevents curl from detecting MITM attackers and more.
| Affected range | <=7.88.1-10+deb12u14 | | Fixed version | Not Fixed | | EPSS Score | 2.076% | | EPSS Percentile | 84th percentile |
Description
When libcurl is asked to perform automatic gzip decompression of content-encoded HTTP responses with the CURLOPT_ACCEPT_ENCODING option, using zlib 1.2.0.3 or older, an attacker-controlled integer overflow would make libcurl perform a buffer overflow.
| Affected range | <=7.88.1-10+deb12u14 | | Fixed version | Not Fixed | | EPSS Score | 0.247% | | EPSS Percentile | 48th percentile |
Description
libcurl skips the certificate verification for a QUIC connection under certain conditions, when built to use wolfSSL. If told to use an unknown/bad cipher or curve, the error path accidentally skips the verification and returns OK, thus ignoring any certificate problems.
|
 openldap 2.5.13+dfsg-5 (deb)
pkg:deb/debian/openldap@2.5.13%2Bdfsg-5?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (53:59)
RUN apt-get update && apt-get install -y --no-install-recommends \
ca-certificates \
jq \
curl \
procps \
bash \
&& rm -rf /var/lib/apt/lists/*
| Affected range | <=2.5.13+dfsg-5 | | Fixed version | Not Fixed | | EPSS Score | 0.018% | | EPSS Percentile | 4th percentile |
Description
OpenLDAP Lightning Memory-Mapped Database (LMDB) versions up to and including 0.9.14, prior to commit 8e1fda8, contain a heap buffer underflow in the readline() function of mdb_load. When processing malformed input containing an embedded NUL byte, an unsigned offset calculation can underflow and cause an out-of-bounds read of one byte before the allocated heap buffer. This can cause mdb_load to crash, leading to a limited denial-of-service condition.
| Affected range | <=2.5.13+dfsg-5 | | Fixed version | Not Fixed | | EPSS Score | 0.216% | | EPSS Percentile | 44th percentile |
Description
libldap in certain third-party OpenLDAP packages has a certificate-validation flaw when the third-party package is asserting RFC6125 support. It considers CN even when there is a non-matching subjectAltName (SAN). This is fixed in, for example, openldap-2.4.46-10.el8 in Red Hat Enterprise Linux.
| Affected range | <=2.5.13+dfsg-5 | | Fixed version | Not Fixed | | EPSS Score | 1.643% | | EPSS Percentile | 82nd percentile |
Description
contrib/slapd-modules/nops/nops.c in OpenLDAP through 2.4.45, when both the nops module and the memberof overlay are enabled, attempts to free a buffer that was allocated on the stack, which allows remote attackers to cause a denial of service (slapd crash) via a member MODDN operation.
| Affected range | <=2.5.13+dfsg-5 | | Fixed version | Not Fixed | | EPSS Score | 0.123% | | EPSS Percentile | 32nd percentile |
Description
slapd in OpenLDAP 2.4.45 and earlier creates a PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for PID file modification before a root script executes a "kill cat /pathname" command, as demonstrated by openldap-initscript.
| Affected range | <=2.5.13+dfsg-5 | | Fixed version | Not Fixed | | EPSS Score | 2.938% | | EPSS Percentile | 86th percentile |
Description
The nss_parse_ciphers function in libraries/libldap/tls_m.c in OpenLDAP does not properly parse OpenSSL-style multi-keyword mode cipher strings, which might cause a weaker than intended cipher to be used and allow remote attackers to have unspecified impact via unknown vectors.
- openldap (unimportant)
Debian builds with GNUTLS, not NSS
|
 systemd 252.39-1~deb12u1 (deb)
pkg:deb/debian/systemd@252.39-1~deb12u1?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (36:36)
FROM debian:bookworm-slim
| Affected range | <=252.39-1~deb12u1 | | Fixed version | Not Fixed | | EPSS Score | 0.094% | | EPSS Percentile | 27th percentile |
Description
An issue was discovered in systemd 253. An attacker can modify the contents of past events in a sealed log file and then adjust the file such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."
| Affected range | <=252.39-1~deb12u1 | | Fixed version | Not Fixed | | EPSS Score | 0.100% | | EPSS Percentile | 28th percentile |
Description
An issue was discovered in systemd 253. An attacker can truncate a sealed log file and then resume log sealing such that checking the integrity shows no error, despite modifications. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."
| Affected range | <=252.39-1~deb12u1 | | Fixed version | Not Fixed | | EPSS Score | 0.128% | | EPSS Percentile | 33rd percentile |
Description
An issue was discovered in systemd 253. An attacker can modify a sealed log file such that, in some views, not all existing and sealed log messages are displayed. NOTE: the vendor reportedly sent "a reply denying that any of the finding was a security vulnerability."
| Affected range | <=252.39-1~deb12u1 | | Fixed version | Not Fixed | | EPSS Score | 0.042% | | EPSS Percentile | 12th percentile |
Description
systemd, when updating file permissions, allows local users to change the permissions and SELinux security contexts for arbitrary files via a symlink attack on unspecified files.
|
krb5 1.20.1-2+deb12u4 (deb)
pkg:deb/debian/krb5@1.20.1-2%2Bdeb12u4?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (53:59)
RUN apt-get update && apt-get install -y --no-install-recommends \
ca-certificates \
jq \
curl \
procps \
bash \
&& rm -rf /var/lib/apt/lists/*
| Affected range | <=1.20.1-2+deb12u4 | | Fixed version | Not Fixed | | EPSS Score | 0.062% | | EPSS Percentile | 19th percentile |
Description
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak vulnerability in /krb5/src/lib/gssapi/krb5/k5sealv3.c.
| Affected range | <=1.20.1-2+deb12u4 | | Fixed version | Not Fixed | | EPSS Score | 0.206% | | EPSS Percentile | 43rd percentile |
Description
Kerberos 5 (aka krb5) 1.21.2 contains a memory leak in /krb5/src/lib/rpc/pmap_rmt.c.
| Affected range | <=1.20.1-2+deb12u4 | | Fixed version | Not Fixed | | EPSS Score | 1.485% | | EPSS Percentile | 81st percentile |
Description
An issue was discovered in MIT Kerberos 5 (aka krb5) through 1.16. There is a variable "dbentry->n_key_data" in kadmin/dbutil/dump.c that can store 16-bit data but unknowingly the developer has assigned a "u4" variable to it, which is for 32-bit data. An attacker can use this vulnerability to affect other artifacts of the database as we know that a Kerberos database dump file contains trusted data.
|
 perl 5.36.0-7+deb12u3 (deb)
pkg:deb/debian/perl@5.36.0-7%2Bdeb12u3?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (36:36)
FROM debian:bookworm-slim
| Affected range | <=5.36.0-7+deb12u3 | | Fixed version | Not Fixed | | EPSS Score | 0.560% | | EPSS Percentile | 68th percentile |
Description
HTTP::Tiny before 0.083, a Perl core module since 5.13.9 and available standalone on CPAN, has an insecure default TLS configuration where users must opt in to verify certificates.
| Affected range | <=5.36.0-7+deb12u3 | | Fixed version | Not Fixed | | EPSS Score | 0.195% | | EPSS Percentile | 42nd percentile |
Description
_is_safe in the File::Temp module for Perl does not properly handle symlinks.
|
coreutils 9.1-1 (deb)
pkg:deb/debian/coreutils@9.1-1?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (36:36)
FROM debian:bookworm-slim
| Affected range | <=9.1-1 | | Fixed version | Not Fixed | | EPSS Score | 0.020% | | EPSS Percentile | 4th percentile |
Description
A flaw was found in GNU Coreutils. The sort utility's begfield() function is vulnerable to a heap buffer under-read. The program may access memory outside the allocated buffer if a user runs a crafted command using the traditional key format. A malicious input could lead to a crash or leak sensitive data.
| Affected range | <=9.1-1 | | Fixed version | Not Fixed | | EPSS Score | 0.056% | | EPSS Percentile | 17th percentile |
Description
In GNU Coreutils through 8.29, chown-core.c in chown and chgrp does not prevent replacement of a plain file with a symlink during use of the POSIX "-R -L" options, which allows local users to modify the ownership of arbitrary files by leveraging a race condition.
|
jq 1.6-2.1+deb12u1 (deb)
pkg:deb/debian/jq@1.6-2.1%2Bdeb12u1?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (53:59)
RUN apt-get update && apt-get install -y --no-install-recommends \
ca-certificates \
jq \
curl \
procps \
bash \
&& rm -rf /var/lib/apt/lists/*
| Affected range | <=1.6-2.1+deb12u1 | | Fixed version | Not Fixed | | EPSS Score | 0.024% | | EPSS Percentile | 6th percentile |
Description
A vulnerability was determined in jqlang jq up to 1.6. Impacted is the function run_jq_tests of the file jq_test.c of the component JSON Parser. Executing manipulation can lead to reachable assertion. The attack requires local access. The exploit has been publicly disclosed and may be utilized. Other versions might be affected as well.
| Affected range | <=1.6-2.1+deb12u1 | | Fixed version | Not Fixed | | EPSS Score | 0.099% | | EPSS Percentile | 28th percentile |
Description
jq is a command-line JSON processor. In versions up to and including 1.7.1, an integer overflow arises when assigning value using an index of 2147483647, the signed integer limit. This causes a denial of service. Commit de21386681c0df0104a99d9d09db23a9b2a78b1e contains a patch for the issue.
|
libgcrypt20 1.10.1-3 (deb)
pkg:deb/debian/libgcrypt20@1.10.1-3?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (36:36)
FROM debian:bookworm-slim
| Affected range | <=1.10.1-3 | | Fixed version | Not Fixed | | EPSS Score | 0.222% | | EPSS Percentile | 45th percentile |
Description
A timing-based side-channel flaw was found in libgcrypt's RSA implementation. This issue may allow a remote attacker to initiate a Bleichenbacher-style attack, which can lead to the decryption of RSA ciphertexts.
| Affected range | <=1.10.1-3 | | Fixed version | Not Fixed | | EPSS Score | 0.515% | | EPSS Percentile | 66th percentile |
Description
cipher/elgamal.c in Libgcrypt through 1.8.2, when used to encrypt messages directly, improperly encodes plaintexts, which allows attackers to obtain sensitive information by reading ciphertext data (i.e., it does not have semantic security in face of a ciphertext-only attack). The Decisional Diffie-Hellman (DDH) assumption does not hold for Libgcrypt's ElGamal implementation.
|
shadow 1:4.13+dfsg1-1+deb12u1 (deb)
pkg:deb/debian/shadow@1%3A4.13%2Bdfsg1-1%2Bdeb12u1?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (36:36)
FROM debian:bookworm-slim
| Affected range | <=1:4.13+dfsg1-1+deb12u2 | | Fixed version | Not Fixed | | EPSS Score | 0.264% | | EPSS Percentile | 50th percentile |
Description
initscripts in rPath Linux 1 sets insecure permissions for the /var/log/btmp file, which allows local users to obtain sensitive information regarding authentication attempts. NOTE: because sshd detects the insecure permissions and does not log certain events, this also prevents sshd from logging failed authentication attempts by remote attackers.
- shadow (unimportant)
See #290803, on Debian LOG_UNKFAIL_ENAB in login.defs is set to no so
unknown usernames are not recorded on login failures
|
apt 2.6.1 (deb)
pkg:deb/debian/apt@2.6.1?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (36:36)
FROM debian:bookworm-slim
| Affected range | <=2.6.1 | | Fixed version | Not Fixed | | EPSS Score | 1.509% | | EPSS Percentile | 81st percentile |
Description
It was found that apt-key in apt, all versions, do not correctly validate gpg keys with the master keyring, leading to a potential man-in-the-middle attack.
|
gnutls28 3.7.9-2+deb12u5 (deb)
pkg:deb/debian/gnutls28@3.7.9-2%2Bdeb12u5?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (36:36)
FROM debian:bookworm-slim
| Affected range | <=3.7.9-2+deb12u5 | | Fixed version | Not Fixed | | EPSS Score | 6.839% | | EPSS Percentile | 91st percentile |
Description
The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.
|
util-linux 2.38.1-5+deb12u3 (deb)
pkg:deb/debian/util-linux@2.38.1-5%2Bdeb12u3?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (36:36)
FROM debian:bookworm-slim
| Affected range | <=2.38.1-5+deb12u3 | | Fixed version | Not Fixed | | EPSS Score | 0.020% | | EPSS Percentile | 4th percentile |
Description
A flaw was found in the util-linux chfn and chsh utilities when compiled with Readline support. The Readline library uses an "INPUTRC" environment variable to get a path to the library config file. When the library cannot parse the specified file, it prints an error message containing data from the file. This flaw allows an unprivileged user to read root-owned files, potentially leading to privilege escalation. This flaw affects util-linux versions prior to 2.37.4.
|
gcc-12 12.2.0-14+deb12u1 (deb)
pkg:deb/debian/gcc-12@12.2.0-14%2Bdeb12u1?os_distro=bookworm&os_name=debian&os_version=12
# minio-release.dockerfile (36:36)
FROM debian:bookworm-slim
| Affected range | <=12.2.0-14+deb12u1 | | Fixed version | Not Fixed | | EPSS Score | 0.050% | | EPSS Percentile | 15th percentile |
Description
libiberty/rust-demangle.c in GNU GCC 11.2 allows stack consumption in demangle_const, as demonstrated by nm-new.
|
