CVE-2024-51987
Duende.AccessTokenManagement.OpenIdConnect is a set of .NET …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/DuendeSoftware/Duende.AccessTokenManagement/security/advisories/GHSA-7mr7-4f54-
- github.com/DuendeSoftware/Duende.AccessTokenManagement/commit/09c73e32b182da5c6d7b55ec790c
- github.com/DuendeSoftware/Duende.AccessTokenManagement/releases/tag/3.0.1
- nvd.nist.gov/vuln/detail/CVE-2024-51987
- github.com/advisories/GHSA-7mr7-4f54-vcx5
- nvd.nist.gov/vuln/detail/CVE-2024-51987
- cve.org/CVERecord?id=CVE-2024-51987
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.