← Übersicht Traefik

Traefik Enterprise OIDC and OAuthClientCreds middlewares store session and token payloads with unauthenticated AES-CTR encryption and a non-cryptographic CSRF signature

GHSA-qcr9-wmgw-2q4c

Hoch · CVSS 7.0 Netzwerk · ohne Login Fix verfügbar

Veröffentlicht
08.10.2026 14:56
Zuletzt geändert
08.10.2026
EPSS (30 Tage)
unbekannt
CVSS-Vektor
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

Beschreibung

Originaltext der Quelle, nicht übersetzt.

## Summary There is a high severity vulnerability in Traefik Enterprise's `OIDC` and `OAuthClientCreds` middlewares. The data they store outside the gateway (session cookies, state cookies, KV session data and cached OAuth tokens) is encrypted with AES in CTR mode, which provides no integrity check, so a tampered payload is decrypted and accepted instead of being rejected. The encryption keys are the configured secrets used as is, so a payload written for one authentication source or middleware decrypts in another one that shares the same secret, and the CSRF token of the `OIDC` middleware is "signed" with the non-cryptographic FNV-1a hash and compared in non-constant time. An attacker holding a valid payload (for example, the cookie of their own session) can modify it in a predictable way, or reuse it in a context it was not issued for, to alter the session data or the cached token the middleware trusts. The CSRF protection of the middleware can also be weakened, as the token is not a keyed MAC. ## Patches - https://github.com/traefik/enterprise/releases/tag/v2.12.11 Session and state cookies, KV sessions and cached tokens written before the upgrade cannot be decoded by the patched versions: users log in once more and the middleware fetches one fresh token. No configuration change is required. ## For more information If you have any questions or comments about this advisory, please [open a Zendesk ticket](https://traefik.zendesk.com).

Betroffene Pakete im beobachteten Stack

GitHubtraefik/enterprise/Traefik Enterprise2.2.0 → 2.12.11GHSA-qcr9-wmgw-2q4c

Empfohlene Prüfung

  1. Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
  2. Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
  3. Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.

Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.