CVE-2024-51987 – duende.accesstokenmanagement.openidconnect

Package

Manager: nuget
Name: duende.accesstokenmanagement.openidconnect
Vulnerable Version: =3.0.0 || >=3.0.0 <3.0.1

Severity

Level: Medium

CVSS v3.1: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

CVSS v4.0: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

EPSS: 0.00094 pctl0.27194

Details

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.

Metadata

Created: 2024-11-07T21:57:52Z
Modified: 2024-11-08T13:55:27Z
Source: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/11/GHSA-7mr7-4f54-vcx5/GHSA-7mr7-4f54-vcx5.json
CWE IDs: ["CWE-270"]
Alternative ID: GHSA-7mr7-4f54-vcx5
Finding: F115
Auto approve: 1