CVE-2024-51987: HTTP Client uses incorrect token after refresh
(updated )
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.
References
- github.com/DuendeSoftware/Duende.AccessTokenManagement
- github.com/DuendeSoftware/Duende.AccessTokenManagement/commit/09c73e32b182da5c6d7b55ec790cb2271cc4b63f
- github.com/DuendeSoftware/Duende.AccessTokenManagement/releases/tag/3.0.1
- github.com/DuendeSoftware/Duende.AccessTokenManagement/security/advisories/GHSA-7mr7-4f54-vcx5
- github.com/advisories/GHSA-7mr7-4f54-vcx5
- nvd.nist.gov/vuln/detail/CVE-2024-51987
Detect and mitigate CVE-2024-51987 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →