We've published several security advisories for Duende products including IdentityServer and BFF, along with updated packages that fix them. We strongly recommend updating to the latest patched releases.
The same fixes are released in 8.0.11, 7.4.15, 7.3.6, 7.2.6, 7.1.4 and 7.0.11.
Security fixes
- GHSA-mv65-jhg4-3qh6: mTLS client authentication can be bypassed with a self-signed certificate that matches the expected subject name.
- GHSA-4xw7-58r7-8h6h: Signing in with server-side sessions reuses an existing session key, which allows session fixation.
- GHSA-qqfr-626g-64rp: A DPoP proof key confusion allows leaked DPoP refresh and access tokens to be used.
- GHSA-478v-p4g7-f7g4: id_token_hint isn't validated thoroughly enough.
Upgrade notes
- mTLS: if you call
AddMutualTlsSecretValidators(), make sure the certificate authentication scheme (MutualTls.ClientCertificateAuthenticationScheme,Certificateby default) is registered, usually withAddCertificate(). Clients with a thumbprint (X509Thumbprint) secret that present a self-signed certificate keep working only ifAllowedCertificateTypesincludesCertificateTypes.SelfSigned. Clients that use a self-signed certificate with a subject name (X509Name) secret must switch to a thumbprint secret or a CA-issued certificate. - Introspection: public clients and implicit-only clients can no longer call the introspection endpoint; it returns 401 for them. Give applications that relied on this a confidential client.
- End session: an
id_token_hintthat isn't an ID token, or that has nosubclaim, is ignored, and the user sees the sign-out prompt. If your ID tokens have a customtypheader, add it toIdentityServerOptions.IdentityTokenJwtTypes. - Server-side sessions: a user who signs in on a browser that still carries another user's session is signed out, and has to sign in a second time. If you replaced
IServerSideTicketStorewith your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change to make. - DPoP: if you override
DefaultDPoPProofValidator.ValidateSignatureAsync, replaced theHandlerofJwtRequestValidator, or registered your own secret validator for client assertions, see the advisory for what your code must check.
Other changes
- Stopping an IdentityServer host synchronously from a thread with a single-threaded synchronization context, for example in xUnit v2 tests with
WebApplicationFactory, no longer hangs.
Full Changelog: is-7.4.14...is-7.4.15