# Snyk test report

November 2nd 2025, 12:32:19 am (UTC+00:00)

Scanned the following paths:

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

38 known vulnerabilities
101 vulnerable dependency paths
969 dependencies

## Incorrect Implementation of Authentication Algorithm

critical severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/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.24.0

### Detailed paths

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

## Overview

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

Affected versions of this package are vulnerable to Incorrect Implementation of Authentication Algorithm when the key passed in the last call before a connection is established is assumed to be the key used for authentication. It is not necessarily the authentication key in use, and this allows attackers who can control the key cache by making their own carefully-timed connections to bypass authorization with subsequent legitimate `ServerConfig.PublicKeyCallback` callbacks.

Note: The assumed caching behavior of this callback is not documented and is therefore considered human error, but the project maintainers have observed reliance on it for authorization decisions in production. In fact, the assumption is negated in the documentation, which states "A call to this function does not guarantee that the key offered is in fact used to authenticate." The behavior after upgrading still allows the possibility of an attacker forcing their own key to be the one in the cache when the callback is invoked if the client is using a different authentication method such as `PasswordCallback`, `KeyboardInteractiveCallback`, or `NoClientAuth`. It is therefore recommended to rely on the return values of the connection itself, found in `ServerConn.Permissions` for further authorization steps.

## Remediation

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

## References

- GitHub Commit
- GitHub Issue
- go.dev Commit
- go.dev Issue
- Google Groups Forum
- Go Vulnerability Database
- PoC

More about this vulnerability

## Access of Resource Using Incompatible Type ('Type Confusion')

high severity

- Package Manager: alpine:3.20
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 and openssl/libcrypto3@3.3.1-r3

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libssl3@3.3.1-r3

## 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.20` relevant fixed versions and status.

Issue summary: Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address resulting in abnormal termination of the application process.

Impact summary: Abnormal termination of an application can a cause a denial of service.

Applications performing certificate name checks (e.g., TLS clients checking server certificates) may attempt to read an invalid memory address when comparing the expected name with an `otherName` subject alternative name of an X.509 certificate. This may result in an exception that terminates the application program.

Note that basic certificate chain validation (signatures, dates, ...) is not affected, the denial of service can occur only when the application also specifies an expected DNS name, Email address or IP address.

TLS servers rarely solicit client certificates, and even when they do, they generally don't perform a name check against a reference identifier (expected identity), but rather extract the presented identity after checking the certificate chain. So TLS servers are generally not affected and the severity of the issue is Moderate.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

## Remediation

Upgrade `Alpine:3.20` `openssl` to version 3.3.2-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/05f360d9e849a1b277db628f1f13083a7f8dd04f
- https://github.com/openssl/openssl/commit/06d1dc3fa96a2ba5a3e22735a033012aadc9f0d6
- https://github.com/openssl/openssl/commit/621f3729831b05ee828a3203eddb621d014ff2b2
- https://github.com/openssl/openssl/commit/7dfcee2cd2a63b2c64b9b4b0850be64cb695b0a0
- https://openssl-library.org/news/secadv/20240903.txt
- http://www.openwall.com/lists/oss-security/2024/09/03/4
- https://lists.freebsd.org/archives/freebsd-security/2024-September/000303.html
- https://security.netapp.com/advisory/ntap-20240912-0001/

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

high severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/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.21.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/oauth2/jws@v0.21.0
- Introduced through: github.com/dexidp/dex@* › golang.org/x/oauth2/jws@v0.21.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

## Server-side Request Forgery (SSRF)

high severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/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.26.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/net/http/httpproxy@v0.26.0
- Introduced through: github.com/dexidp/dex@* › golang.org/x/net/http/httpproxy@v0.27.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

## Denial of Service (DoS)

high severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/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.27.0

### Detailed paths

- Introduced through: github.com/dexidp/dex@* › golang.org/x/net/html@v0.27.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 Denial of Service (DoS) through the functions `parseDoctype`, `htmlIntegrationPoint`, `inBodyIM` and `inTableIM` due to inefficient usage of the method `strings.ToLower` combining with the `==` operator to convert strings to lowercase and then comparing them.

An attacker can cause the application to slow down significantly by crafting inputs that are processed non-linearly.

## 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/net/html` to version 0.33.0 or higher.

## References

- GitHub Commit
- GitHub Issue
- Google Groups Forum

More about this vulnerability

## Improper Handling of Unexpected Data Type

high severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/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.24.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh/agent@v0.24.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

## Allocation of Resources Without Limits or Throttling

high severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/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.24.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › golang.org/x/crypto/ssh@v0.24.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

## Asymmetric Resource Consumption (Amplification)

high severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/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

## Insertion of Sensitive Information into Log File

medium severity

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

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › google.golang.org/grpc/metadata@v1.64.0

## Overview

google.golang.org/grpc/metadata is a package that defines the structure of the metadata supported by the gRPC library

Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File in the form of gRPC metadata. If the metadata contains sensitive information an attacker can expose it.

## Remediation

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

## References

- GitHub Commit

More about this vulnerability

## Improper Validation of Syntactic Correctness of Input

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/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.27.0

### Detailed paths

- Introduced through: github.com/dexidp/dex@* › golang.org/x/net/html@v0.27.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 Improper Validation of Syntactic Correctness of Input in the tokenizer in `token.go`, which incorrectly interprets tags as closing tags, allowing malicious input to be incorrectly processed and the DOM to be corrupted.

## 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.38.0 or higher.

## References

- GitHub Commit
- GitHub Issue
- Google Groups Announcement

More about this vulnerability

## Observable Discrepancy

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Vulnerable module: github.com/hashicorp/vault/api/auth/userpass
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/vault/api/auth/userpass@v0.7.0

### Detailed paths

- Introduced through: github.com/hairyhenderson/gomplate/v4@* › github.com/hashicorp/vault/api/auth/userpass@v0.7.0

## Overview

Affected versions of this package are vulnerable to Observable Discrepancy via `userpass` auth method. An attacker can enumerate valid usernames on this auth method through brute force or a list of known usernames.

##Workaround

This issue can be partially mitigated by using rate-limit quotas in Vault or enabling network level controls for rate limiting that restrict access to Vault. Customers may also consider enforcing login MFA for the userpass auth mounts.

## Remediation

There is no fixed version for `github.com/hashicorp/vault/api/auth/userpass`.

## References

- HashiCorp Discussion
- Security Report

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/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.14.0

### Detailed paths

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

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/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.41.1/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.41.1/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.41.1/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.41.1/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.41.1/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.6

### Detailed paths

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

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/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.41.1/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.41.1/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.41.1/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.41.1/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.41.1/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.41.1/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.41.1/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.41.1/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.41.1/hairyhenderson/gomplate/v4 › /usr/local/bin/gomplate
- Package Manager: golang
- Module: github.com/hashicorp/consul/api
- Introduced through: github.com/hairyhenderson/gomplate/v4@* and github.com/hashicorp/consul/api@v1.29.1

### Detailed paths

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

MPL-2.0 license

More about this vulnerability

## MPL-2.0 license

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/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.41.1/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.8.1

### Detailed paths

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

MPL-2.0 license

More about this vulnerability

## Allocation of Resources Without Limits or Throttling

medium severity

- Manifest file: ghcr.io/dexidp/dex:v2.41.1/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.0.4

## 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

## CVE-2025-9230

low severity

- Package Manager: alpine:3.20
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 and openssl/libcrypto3@3.3.1-r3

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libssl3@3.3.1-r3

## 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.20` 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.20` `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

More about this vulnerability

## CVE-2025-9231

low severity

- Package Manager: alpine:3.20
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 and openssl/libcrypto3@3.3.1-r3

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libssl3@3.3.1-r3

## 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.20` 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.20` `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

More about this vulnerability

## CVE-2025-9232

low severity

- Package Manager: alpine:3.20
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 and openssl/libcrypto3@3.3.1-r3

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libssl3@3.3.1-r3

## 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.20` 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.20` `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

More about this vulnerability

## CVE-2024-9143

low severity

- Package Manager: alpine:3.20
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 and openssl/libcrypto3@3.3.1-r3

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libssl3@3.3.1-r3

## 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.20` relevant fixed versions and status.

Issue summary: Use of the low-level GF(2^m) elliptic curve APIs with untrusted explicit values for the field polynomial can lead to out-of-bounds memory reads or writes.

Impact summary: Out of bound memory writes can lead to an application crash or even a possibility of a remote code execution, however, in all the protocols involving Elliptic Curve Cryptography that we're aware of, either only "named curves" are supported, or, if explicit curve parameters are supported, they specify an X9.62 encoding of binary (GF(2^m)) curves that can't represent problematic input values. Thus the likelihood of existence of a vulnerable application is low.

In particular, the X9.62 encoding is used for ECC keys in X.509 certificates, so problematic inputs cannot occur in the context of processing X.509 certificates. Any problematic use-cases would have to be using an "exotic" curve encoding.

The affected APIs include: EC_GROUP_new_curve_GF2m(), EC_GROUP_new_from_params(), and various supporting BN_GF2m_*() functions.

Applications working with "exotic" explicit binary (GF(2^m)) curve parameters, that make it possible to represent invalid field polynomials with a zero constant term, via the above or similar APIs, may terminate abruptly as a result of reading or writing outside of array bounds. Remote code execution cannot easily be ruled out.

The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.

## Remediation

Upgrade `Alpine:3.20` `openssl` to version 3.3.2-r3 or higher.

## References

- https://github.com/openssl/openssl/commit/72ae83ad214d2eef262461365a1975707f862712
- https://github.com/openssl/openssl/commit/bc7e04d7c8d509fb78fc0e285aa948fb0da04700
- https://github.com/openssl/openssl/commit/c0d3e4d32d2805f49bec30547f225bc4d092e1f4
- https://github.com/openssl/openssl/commit/fdf6723362ca51bd883295efe206cb5b1cfa5154
- https://github.openssl.org/openssl/extended-releases/commit/8efc0cbaa8ebba8e116f7b81a876a4123594d86a
- https://github.openssl.org/openssl/extended-releases/commit/9d576994cec2b7aa37a91740ea7e680810957e41
- https://openssl-library.org/news/secadv/20241016.txt
- http://www.openwall.com/lists/oss-security/2024/10/16/1
- http://www.openwall.com/lists/oss-security/2024/10/23/1
- http://www.openwall.com/lists/oss-security/2024/10/24/1
- https://security.netapp.com/advisory/ntap-20241101-0001/

More about this vulnerability

## CVE-2024-13176

low severity

- Package Manager: alpine:3.20
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 and openssl/libcrypto3@3.3.1-r3

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libssl3@3.3.1-r3

## 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.20` relevant fixed versions and status.

Issue summary: A timing side-channel which could potentially allow recovering the private key exists in the ECDSA signature computation.

Impact summary: A timing side-channel in ECDSA signature computations could allow recovering the private key by an attacker. However, measuring the timing would require either local access to the signing application or a very fast network connection with low latency.

There is a timing signal of around 300 nanoseconds when the top word of the inverted ECDSA nonce value is zero. This can happen with significant probability only for some of the supported elliptic curves. In particular the NIST P-521 curve is affected. To be able to measure this leak, the attacker process must either be located in the same physical computer or must have a very fast network connection with low latency. For that reason the severity of this vulnerability is Low.

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

## Remediation

Upgrade `Alpine:3.20` `openssl` to version 3.3.2-r2 or higher.

## References

- https://github.com/openssl/openssl/commit/07272b05b04836a762b4baa874958af51d513844
- https://github.com/openssl/openssl/commit/2af62e74fb59bc469506bc37eb2990ea408d9467
- https://github.com/openssl/openssl/commit/392dcb336405a0c94486aa6655057f59fd3a0902
- https://github.com/openssl/openssl/commit/4b1cb94a734a7d4ec363ac0a215a25c181e11f65
- https://github.com/openssl/openssl/commit/77c608f4c8857e63e98e66444e2e761c9627916f
- https://github.openssl.org/openssl/extended-releases/commit/0d5fd1ab987f7571e2c955d8d8b638fc0fb54ded
- https://github.openssl.org/openssl/extended-releases/commit/a2639000db19878d5d89586ae7b725080592ae86
- https://openssl-library.org/news/secadv/20250120.txt
- http://www.openwall.com/lists/oss-security/2025/01/20/2
- https://security.netapp.com/advisory/ntap-20250124-0005/
- https://security.netapp.com/advisory/ntap-20250418-0010/
- https://lists.debian.org/debian-lts-announce/2025/05/msg00028.html

More about this vulnerability

## CVE-2024-12797

low severity

- Package Manager: alpine:3.20
- Vulnerable module: openssl/libcrypto3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 and openssl/libcrypto3@3.3.1-r3

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3 › openssl/libcrypto3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › openssl/libssl3@3.3.1-r3

## 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.20` relevant fixed versions and status.

Issue summary: Clients using RFC7250 Raw Public Keys (RPKs) to authenticate a server may fail to notice that the server was not authenticated, because handshakes don't abort as expected when the SSL_VERIFY_PEER verification mode is set.

Impact summary: TLS and DTLS connections using raw public keys may be vulnerable to man-in-middle attacks when server authentication failure is not detected by clients.

RPKs are disabled by default in both TLS clients and TLS servers. The issue only arises when TLS clients explicitly enable RPK use by the server, and the server, likewise, enables sending of an RPK instead of an X.509 certificate chain. The affected clients are those that then rely on the handshake to fail when the server's RPK fails to match one of the expected public keys, by setting the verification mode to SSL_VERIFY_PEER.

Clients that enable server-side raw public keys can still find out that raw public key verification failed by calling SSL_get_verify_result(), and those that do, and take appropriate action, are not affected. This issue was introduced in the initial implementation of RPK support in OpenSSL 3.2.

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

## Remediation

Upgrade `Alpine:3.20` `openssl` to version 3.3.3-r0 or higher.

## References

- https://github.com/openssl/openssl/commit/738d4f9fdeaad57660dcba50a619fafced3fd5e9
- https://github.com/openssl/openssl/commit/798779d43494549b611233f92652f0da5328fbe7
- https://github.com/openssl/openssl/commit/87ebd203feffcf92ad5889df92f90bb0ee10a699
- https://openssl-library.org/news/secadv/20250211.txt
- http://www.openwall.com/lists/oss-security/2025/02/11/3
- http://www.openwall.com/lists/oss-security/2025/02/11/4
- https://security.netapp.com/advisory/ntap-20250214-0001/

More about this vulnerability

## CVE-2025-26519

low severity

- Package Manager: alpine:3.20
- Vulnerable module: musl/musl
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 and musl/musl@1.2.5-r0

### Detailed paths

- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › musl/musl@1.2.5-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › musl/musl@1.2.5-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › busybox/ssl_client@1.36.1-r29 › musl/musl@1.2.5-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › musl/musl-utils@1.2.5-r0 › musl/musl@1.2.5-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libcrypto3@3.3.1-r3 › musl/musl@1.2.5-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › openssl/libssl3@3.3.1-r3 › musl/musl@1.2.5-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › apk-tools/apk-tools@2.14.4-r0 › zlib/zlib@1.3.1-r1 › musl/musl@1.2.5-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › musl/musl-utils@1.2.5-r0 › pax-utils/scanelf@1.3.7-r2 › musl/musl@1.2.5-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › alpine-baselayout/alpine-baselayout@3.6.5-r0 › busybox/busybox-binsh@1.36.1-r29 › busybox/busybox@1.36.1-r29 › musl/musl@1.2.5-r0
- Introduced through: docker-image|ghcr.io/dexidp/dex@v2.41.1 › musl/musl-utils@1.2.5-r0

## 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.20` relevant fixed versions and status.

musl libc 0.9.13 through 1.2.5 before 1.2.6 has an out-of-bounds write vulnerability when an attacker can trigger iconv conversion of untrusted EUC-KR text to UTF-8.

## Remediation

Upgrade `Alpine:3.20` `musl` to version 1.2.5-r1 or higher.

## References

- https://git.musl-libc.org/cgit/musl/commit/?id=c47ad25ea3b484e10326f933e927c0bc8cded3da
- https://git.musl-libc.org/cgit/musl/commit/?id=e5adcd97b5196e29991b524237381a0202a60659
- https://www.openwall.com/lists/oss-security/2025/02/13/2
- http://www.openwall.com/lists/oss-security/2025/02/13/2
- http://www.openwall.com/lists/oss-security/2025/02/13/3
- http://www.openwall.com/lists/oss-security/2025/02/13/4
- http://www.openwall.com/lists/oss-security/2025/02/13/5
- http://www.openwall.com/lists/oss-security/2025/02/14/5
- http://www.openwall.com/lists/oss-security/2025/02/14/6

More about this vulnerability