We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.

Please see our statement on Data Privacy.

Crisp.chat (Helpdesk and Chat)

Ok

THREATINT
PUBLISHED

CVE-2024-51987

HTTP Client uses incorrect token after refresh in Duende.AccessTokenManagement.OpenIdConnect



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.

Reserved 2024-11-04 | Published 2024-11-07 | Updated 2024-11-08 | Assigner GitHub_M


MEDIUM: 5.4CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Problem types

CWE-270: Privilege Context Switching Error

Product status

= 3.0.0
affected

References

github.com/...gement/security/advisories/GHSA-7mr7-4f54-vcx5

cve.org (CVE-2024-51987)

nvd.nist.gov (CVE-2024-51987)

Download JSON

Share this page
https://cve.threatint.com/CVE/CVE-2024-51987

Support options

Helpdesk Chat, Email, Knowledgebase
Telegram Chat
Subscribe to our newsletter to learn more about our work.