Advisory

GHSA-7mr7-4f54-vcx5

Also known as: CVE-2024-51987

Summary

HTTP Client uses incorrect token after refresh

Details

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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2024-11-07 21:57 UTC
Modified
2024-11-08 13:55 UTC

Affected packages and fixes

Duende.AccessTokenManagement.OpenIdConnect

NuGet · All systems

Affected

  • introduced 3.0.0, fixed 3.0.1 (ecosystem)

Fixed versions

3.0.1

Fix

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

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences