Ory Hydra has a SQL injection via forged pagination tokens
ory hydra
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/ory/hydra Go |
| No fix yet |
| github.com/ory/hydra/v2 Go |
|
|
ory hydra
| Product | Affected | Fixed in |
|---|---|---|
| github.com/ory/hydra Go |
| No fix yet |
| github.com/ory/hydra/v2 Go |
|
|
Ory Hydra is an OAuth 2.0 Server and OpenID Connect Provider. Prior to version 26.2.0, the listOAuth2Clients, listOAuth2ConsentSessions, and listTrustedOAuth2JwtGrantIssuers Admin APIs in Ory Hydra are vulnerable to SQL injection due to flaws in its pagination implementation. Pagination tokens are encrypted using the secret configured in `secrets.pagination`. If this value is not set, Hydra falls back to using `secrets.system`. An attacker who knows this secret can craft their own tokens, including malicious tokens that lead to SQL injection. This issue can be exploited when one or more admin APIs listed above are directly or indirectly accessible to the attacker; the attacker can pass a raw pagination token to the affected API; and the configuration value `secrets.pagination` is set and known to the attacker, or `secrets.pagination` is not set and `secrets.system` is known to the attacker. An attacker can execute arbitrary SQL queries through forged pagination tokens. As a first line of defense, immediately configure a custom value for `secrets.pagination` by generating a cryptographically secure random secret. Next, upgrade Hydra to the fixed version, 26.2.0 as soon as possible.
From the CVE record · GitHub_M
Ory Hydra’s listOAuth2Clients, listOAuth2ConsentSessions, and listTrustedOAuth2JwtGrantIssuers Admin APIs are vulnerable to SQL injection through forged pagination tokens. An attacker can execute arbitrary SQL queries if they can pass a raw token to an affected API and know the configured pagination secret, or the system secret when no pagination secret is set. No user interaction is described; exploitation requires direct or indirect access to an affected Admin API.
Teams running Ory Hydra before 26.2.0, Go package github.com/ory/hydra/v2 before 2.3.1-0.20260320110106-0b84568fffcc, or github.com/ory/hydra versions up to 1.11.10 should check.