github DuendeSoftware/products is-8.0.11
Duende IdentityServer 8.0.11

latest releases: aaj-1.0.3, bff-2.2.2, bff-2.3.2...
35 minutes ago

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 fixes that aren't SAML-specific are also released in 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-wcc6-7mjx-g6j5: Incorrectly formatted SAML messages can cause a denial of service.
  • GHSA-hmrv-xfgm-wgh2: The SAML service provider doesn't validate bearer SubjectConfirmationData.
  • GHSA-478v-p4g7-f7g4: id_token_hint isn't validated thoroughly enough.
  • GHSA-6xhh-5qhq-m9vf: The SAML service provider ends a session when it receives a logout request from a different identity provider.
  • GHSA-hhqg-4hp5-4v5h: The SAML service provider accepts a changed RelayState in signed HTTP-Redirect messages.

Upgrade notes

  • mTLS: if you call AddMutualTlsSecretValidators(), make sure the certificate authentication scheme (MutualTls.ClientCertificateAuthenticationScheme, Certificate by default) is registered, usually with AddCertificate(). Clients with a thumbprint (X509Thumbprint) secret that present a self-signed certificate keep working only if AllowedCertificateTypes includes CertificateTypes.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_hint that isn't an ID token, or that has no sub claim, is ignored, and the user sees the sign-out prompt. If your ID tokens have a custom typ header, add it to IdentityServerOptions.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 IServerSideTicketStore with 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 the Handler of JwtRequestValidator, or registered your own secret validator for client assertions, see the advisory for what your code must check.

  • SAML XML limits: SAML messages whose XML elements are nested deeper than MaxXmlNestingDepth (32 by default) are rejected. You can change the limit for the identity provider (SamlOptions.MaxXmlNestingDepth), for service providers configured in code (SamlServiceProviderOptions.MaxXmlNestingDepth) and for SAML dynamic providers. The service provider now also rejects messages that contain a DTD and drops XML processing instructions, as the identity provider already did.

  • SAML logout with an external login callback: if you use SAML dynamic providers (AddSamlDynamicProvider()), or AddSamlServiceProvider() with the external cookie as its sign-in scheme, your external login callback creates the IdentityServer session. Copy the SAML sign-in claims into that session, or IdP-initiated logout stays exposed after the upgrade. In our templates, add this to CaptureExternalLoginContext in Pages/ExternalLogin/Callback.cshtml.cs, right after the block that copies the sid claim:

    localClaims.AddRange(externalResult.Principal.Claims.Where(claim => claim.Type
        is "https://duendesoftware.com/Saml2/Scheme"
        or "https://duendesoftware.com/Saml2/LogoutNameIdentifier"
        or "https://duendesoftware.com/Saml2/SessionIndex"));
  • SAML logout and SameSite: if your session cookie uses SameSite=Lax or SameSite=Strict and an identity provider sends its LogoutRequest with the HTTP-POST binding, the logout no longer ends the IdentityServer session. The default, SameSite=None, isn't affected.

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-8.0.10...is-8.0.11

Don't miss a new products release

NewReleases is sending notifications on new releases.