Duende.AccessTokenManagement.OpenIdConnect
Affected
- introduced
3.0.0, fixed3.0.1(ecosystem)
Fixed versions
3.0.1
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2024-51987
HTTP Client uses incorrect token after refresh
Impact
HTTP Clients created by AddUserAccessTokenHttpClient may use a different user's access token after a token refresh. This occurs because a refreshed token will be captured in pooled HttpClient instances, which may be used by a different user.
Workarounds
Instead of using AddUserAccessTokenHttpClient to create an HttpClient that automatically adds a managed token to outgoing requests, you can use the HttpConext.GetUserAccessTokenAsync extension method or the IUserTokenManagementService.GetAccessTokenAsync method.
Patches
This issue is fixed in Duende.AccessTokenManagement.OpenIdConnect 3.0.1.
Medium Basis: The source's own band: MODERATE
3.0.0, fixed 3.0.1 (ecosystem)3.0.1
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0