Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

NuGet package

duende.accesstokenmanagement.openidconnect

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.3NuGetPublished

    HTTP Client uses incorrect token after refresh

    CVE-2024-51987 · GHSA-7mr7-4f54-vcx5

    Affected
    • NuGet duende.accesstokenmanagement.openidconnect >= 3.0.0, <= 3.0.0
    Fixed in
    3.0.1· Vendor fix available
    Issue
    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.

    Recommended action: Upgrade to 3.0.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →