Duende.Accesstokenmanagement
Approved changes feed: RSS · Atom
cpe:2.3:a:duendesoftware:duende.accesstokenmanagement:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Duendesoftware (7656334b-da79-552a-870a-c3a062b7294a) |
|---|---|
| Product | Duende.Accesstokenmanagement (2d567fcd-b728-520f-9006-5ac32d12d250) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-51987 |
vulnerable | 2026-06-08 06:52:14.551204 |
HTTP Client uses incorrect token after refresh in Duende.AccessTokenManagement.OpenIdConnect
MEDIUM (5.4)
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.
Published: 2024-11-07T23:36:16.989Z
Updated: 2024-11-08T15:57:51.304Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.