Skip to content

Duende.AspNetCore.Authentication.OAuth2Introspection 7.0.3

Latest

Choose a tag to compare

@Erwinvandervalk Erwinvandervalk released this 16 Nov 18:11
02a7f36

This patch release fixes a security vulnerability: with more than one introspection scheme, a token that one scheme accepted could also authenticate on another scheme. We strongly recommend updating.

Security fixes

  • GHSA-84rm-mhfq-f476 (High): An application can register more than one introspection scheme, each with its own authorization server and client credentials. A token that one scheme's introspection endpoint reported as active could also authenticate on another scheme, without that scheme ever asking its own endpoint. Two things let an introspection result cross schemes: the cache key did not include the scheme, and concurrent requests for the same token shared one introspection call whatever scheme they were for. Each scheme now only accepts results from its own introspection endpoint. This also holds for two hosts in one process that use the same scheme name. Applications with a single introspection scheme are not affected. #394

Upgrade notes

  • Cache keys: the handler now puts the scheme name in front of the cache key, including keys from a custom CacheKeyGenerator. Results cached by earlier versions, including in a shared distributed cache, are no longer found, so each token is introspected once more after the upgrade. If your own code reads these cache entries by key, the key is now {length of scheme name}:{scheme name}:{key from CacheKeyGenerator}.

This release targets .NET 8, .NET 9 and .NET 10.

Full Changelog: intro-7.0.2...intro-7.0.3