Skip to content

CVE-2024-51987 HTTP Client uses incorrect token after refresh in Duende.AccessTokenManagement.OpenIdConnect

MediumCVSS 5.4 EPSS 0.24%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial

Description

Duende.AccessTokenManagement.OpenIdConnect is a set of .NET libraries that manage OAuth and OpenId Connect access tokens. HTTP Clients created by AddUserAccessTokenHttpClient may use a different user's access token after a token refresh occurs. This occurs because a refreshed token will be captured in pooled HttpClient instances, which may be used by a different user. 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. This issue is fixed in Duende.AccessTokenManagement.OpenIdConnect 3.0.1. All users are advised to upgrade. There are no known workarounds for this vulnerability.

Upgrade path

2 packages: 1 fixed.

PackageAffectedFixed inStatus
nuget Duende.AccessTokenManagement.OpenIdConnect(NuGet) = 3.0.0; >= 3.0.0, < 3.0.1 3.0.1 Fixed
DuendeSoftware Duende.AccessTokenManagement = = 3.0.0 No fix listed Versions listed

Affected products

ProductAffected versionsFixed in
nuget Duende.AccessTokenManagement.OpenIdConnect(NuGet) >= 3.0.0, < 3.0.1 3.0.1
nuget Duende.AccessTokenManagement.OpenIdConnect(NuGet) = 3.0.0 No fix listed
DuendeSoftware Duende.AccessTokenManagement = = 3.0.0 No fix listed

References