What is CVE-2024-51987?

CVE-2024-51987 is a medium-severity security vulnerability in Duende.AccessTokenManagement.OpenIdConnect (nuget), affecting versions = 3.0.0. It is fixed in 3.0.1.

How severe is CVE-2024-51987?

CVE-2024-51987 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of Duende.AccessTokenManagement.OpenIdConnect are affected by CVE-2024-51987?

Duende.AccessTokenManagement.OpenIdConnect (nuget) versions = 3.0.0 is affected.

Is there a fix for CVE-2024-51987?

Yes. CVE-2024-51987 is fixed in 3.0.1. Upgrade to this version or later.

Is CVE-2024-51987 exploitable, and should I be worried?

Whether CVE-2024-51987 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-51987 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2024-51987?

Upgrade Duende.AccessTokenManagement.OpenIdConnect to 3.0.1 or later.

CVE-2024-51987

Summary

HTTP Client uses incorrect token after refresh

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.

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.

CVE-2024-51987 has a CVSS score of 5.4 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.0.1); upgrading removes the vulnerable code path.

Affected versions

Duende.AccessTokenManagement.OpenIdConnect (= 3.0.0)

Security releases

Duende.AccessTokenManagement.OpenIdConnect → 3.0.1 (nuget)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

This issue is fixed in Duende.AccessTokenManagement.OpenIdConnect 3.0.1.

Frequently Asked Questions

What is CVE-2024-51987? CVE-2024-51987 is a medium-severity security vulnerability in Duende.AccessTokenManagement.OpenIdConnect (nuget), affecting versions = 3.0.0. It is fixed in 3.0.1.
How severe is CVE-2024-51987? CVE-2024-51987 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of Duende.AccessTokenManagement.OpenIdConnect are affected by CVE-2024-51987? Duende.AccessTokenManagement.OpenIdConnect (nuget) versions = 3.0.0 is affected.
Is there a fix for CVE-2024-51987? Yes. CVE-2024-51987 is fixed in 3.0.1. Upgrade to this version or later.
Is CVE-2024-51987 exploitable, and should I be worried? Whether CVE-2024-51987 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-51987 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-51987? Upgrade Duende.AccessTokenManagement.OpenIdConnect to 3.0.1 or later.