Duende.BFF 4.2.2
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 change default behavior. Read Breaking changes below before you upgrade.
The same fixes are released in 4.3.4, 4.2.2, 4.1.4 and 4.0.5. The fix for GHSA-x394-gwr7-4885 is also released in 3.1.3, 3.0.2, 2.3.2 and 2.2.2.
Security fixes
- GHSA-x394-gwr7-4885: Responses from proxied APIs can set session cookies, and signing in then reuses that planted server-side session.
- GHSA-6gxg-chg2-rm9v: Static asset proxying can forward requests to arbitrary URLs.
Breaking changes
- Proxied APIs can no longer set cookies. If you rely on cookies set by a proxied API, for example load balancer affinity cookies, you can turn this off with
BffOptions.RemoveCookieHeadersFromProxiedResponses = false. Only do this if you trust every API that the BFF proxies. The same setting applies to responses from the static assets server. - Static asset proxy requests use their own HTTP client, named
Duende.Bff.StaticAssetsProxyClient(Constants.HttpClientNames.StaticAssetsProxyClientName). If you configured headers, credentials, certificates or handlers for these requests throughBffOptions.StaticAssetsClientNameorBffOptions.BackchannelHttpHandler, move them to this client withAddHttpClient(Constants.HttpClientNames.StaticAssetsProxyClientName). Custom handlers on this client must not follow redirects. The BFF returns a 502 response when the static assets server redirects. - 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
IServerTicketStorewith your own implementation, upgrading doesn't fix the vulnerability for you; see the advisory for the change to make.
Full Changelog: bff-4.2.1...bff-4.2.2