Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Microsoft Identity Denial of service vulnerability

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

CVE-2024-21319

This is a saved version of the risk data. The advisory details have their own history. Latest risk data.

No CISA KEV listing is included in this saved record. Exploitation may still have occurred.

FIRST EPSS: 2.89 % · percentile 87.18 % · scored 18 Nov 2026. This score is more than two days old.

Saved 18 Nov 2026 15:46:44 UTC · View this risk record (JSON)

cve-program · CVE-2024-21319

Published

Microsoft Identity Denial of service vulnerability

Source published
9 Jan 2024 18:59:01 UTC
Source modified
3 Jun 2025 14:29:52 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 6.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H/E:U/RL:O/RC:C

euvd · EUVD-2024-0259

Published

Microsoft Identity Denial of service vulnerability

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Jan 9, 2024, 6:59:01 PM

dateUpdated: Jun 3, 2025, 2:29:52 PM

13 related source bulletins · separate from aliases

NCSC-2025-0106: Kwetsbaarheden verholpen in Siemens producten

CVE-2022-21658 · CVE-2023-2975 · CVE-2023-3446 · CVE-2023-3817 · CVE-2023-4807 · CVE-2023-5363 · CVE-2023-5678 · CVE-2023-7104 · CVE-2024-0056 · CVE-2024-0232 · CVE-2024-0727 · CVE-2024-5535 · CVE-2024-9143 · CVE-2024-21319 · CVE-2024-23814 · CVE-2024-30105 · CVE-2024-41788 · CVE-2024-41789 · CVE-2024-41790 · CVE-2024-41791 · CVE-2024-41792 · CVE-2024-41793 · CVE-2024-41794 · CVE-2024-41795 · CVE-2024-41796 · CVE-2024-54091 · CVE-2024-54092 · CVE-2025-30280 · CVE-2025-1097 · CVE-2025-24514 · CVE-2025-24513 · CVE-2025-1974 · CVE-2025-1098 · CVE-2025-29999 · CVE-2025-30000

RHSA-2024:0158: security update for dotnet6.0

CVE-2023-46233 · CVE-2024-0056 · CVE-2024-0057 · CVE-2024-21319

ICSA-25-100-02: Siemens SIDIS Prime

CVE-2022-21658 · CVE-2023-2975 · CVE-2023-3446 · CVE-2023-4807 · CVE-2023-5363 · CVE-2023-5678 · CVE-2023-7104 · CVE-2024-0056 · CVE-2024-0232 · CVE-2024-0727 · CVE-2024-5535 · CVE-2024-9143 · CVE-2024-21319 · CVE-2024-30105

RHSA-2024:0152: security update for dotnet8.0

CVE-2024-0056 · CVE-2024-0057 · CVE-2024-21319

msrc_CVE-2024-21319: Microsoft Identity Denial of service vulnerability

CVE-2024-21319

RHSA-2024:0157: security update for dotnet7.0

CVE-2023-46233 · CVE-2024-0056 · CVE-2024-0057 · CVE-2024-21319

RHSA-2024:0156: security update for dotnet6.0

CVE-2023-46233 · CVE-2024-0056 · CVE-2024-0057 · CVE-2024-21319

WID-SEC-W-2024-0040: Microsoft Azure: Mehrere Schwachstellen

CVE-2024-21319 · CVE-2024-20676

SSA-277137: SSA-277137: Multiple Vulnerabilities in SIDIS Prime Before V4.0.700

CVE-2022-21658 · CVE-2023-2975 · CVE-2023-3446 · CVE-2023-4807 · CVE-2023-5363 · CVE-2023-5678 · CVE-2023-7104 · CVE-2024-0056 · CVE-2024-0232 · CVE-2024-0727 · CVE-2024-5535 · CVE-2024-9143 · CVE-2024-21319 · CVE-2024-30105

WID-SEC-W-2024-0039: Microsoft Developer Tools: Mehrere Schwachstellen

CVE-2024-21319 · CVE-2024-21312 · CVE-2024-20672 · CVE-2024-20656 · CVE-2024-0057 · CVE-2024-0056

RHSA-2024:0255: Red Hat Security Advisory: .NET 6.0 security, bug fix, and enhancement update

CVE-2024-0056 · CVE-2024-0057 · CVE-2024-21319

RHSA-2024:0150: security update for dotnet8.0

CVE-2024-0056 · CVE-2024-0057 · CVE-2024-21319

RHSA-2024:0151: security update for dotnet7.0

CVE-2023-46233 · CVE-2024-0056 · CVE-2024-0057 · CVE-2024-21319

Source published
Jan 9, 2024, 6:59:01 PM (timezone not stated)
Source modified
Jun 3, 2025, 2:29:52 PM (timezone not stated)
Saved here
21 Nov 2026 03:48:08 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 6.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H/E:U/RL:O/RC:C

nvd · CVE-2024-21319

Published

Microsoft Identity Denial of service vulnerability

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-20 · NVD-CWE-noinfo

Original publisher date fields

published: 2024-01-09T19:15:12.070

lastModified: 2026-06-17T07:08:59.820

3 source CPE criteria · context only
  • cpe:2.3:a:microsoft:.net:*:*:*:*:*:*:*:*
  • cpe:2.3:a:microsoft:identity_model:*:*:*:*:*:.net:*:*
  • cpe:2.3:a:microsoft:visual_studio_2022:*:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
9 Jan 2024 19:15:12 UTC
Source modified
17 Jun 2026 07:08:59 UTC
Saved here
24 Oct 2026 23:17:16 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 6.8 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H

osv · GHSA-59j7-ghrg-fj52

Published

A Denial of Service vulnerability exists in ASP.NET Core project templates which utilize JWT-based authentication tokens. This vulnerability allows an unauthenticated client to consume arbitrarily large amounts of server memory, potentially triggering an out-of-memory condition on the server and making the server no longer able to respond to legitimate requests. ## Announcement Announcement for this issue can be found at https://github.com/dotnet/announcements/issues/290 ### Mitigation factors This impacts only .NET Core-based projects that were created using any version of project templates listed in affected software. Other project templates e.g., console applications, MAUI applications, Windows Forms or WPF applications, are not affected. ## Affected software This impacts only .NET Core-based projects that were created using any version of the below project templates. - ASP.NET Core Web App (Model-View-Controller) - ASP.NET Core Web API - ASP.NET Core Web App (Razor Pages) - Blazor Server App - Blazor WebAssembly App ## Advisory FAQ ### How do I know if I am affected? If you are you using project templates listed in affected software, you may be exposed to the vulnerability. ### How do I fix the issue? #### For existing projects: If you ever created any of these projects via the dotnet new command or via Visual Studio's File -> New Project gesture, and if you enabled federated authentication at project creation time, your project may be vulnerable. To remediate the vulnerability, use your package manager to update any references you may have to the Microsoft.AspNetCore.Authentication.JwtBearer, Microsoft.AspNetCore.Authentication.OpenIdConnect, and Microsoft.IdentityModel.JsonWebTokens packages to their respective latest versions. - [Microsoft.AspNetCore.Authentication.JwtBearer](https://www.nuget.org/packages/Microsoft.AspNetCore.Authentication.JwtBearer/) - [Microsoft.AspNetCore.Authentication.OpenIdConnect](https://www.nuget.org/packages/Microsoft.AspNetCore.Authentication.OpenIdConnect/) If your project does not reference any of those three packages, you are not exposed to this vulnerability. #### For new projects: To remediate this issue please update to the latest SDK listed below. Simply installing the SDK update is not sufficient to remediate projects already-created / already-deployed projects which existed prior to this update being released. * To fix the issue please install the latest version of .NET 6.0 or .NET 7.0. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs. * If you are using one of the affected packages, please update to the patched version listed above. * If you have .NET 6.0 or greater installed, you can list the versions you have installed by running the `dotnet --info` command. You will see output like the following; ``` .NET Core SDK (reflecting any global.json): Version: 7.0.200 Commit: 8473146e7d Runtime Environment: OS Name: Windows OS Version: 10.0.18363 OS Platform: Windows RID: win10-x64 Base Path: C:\Program Files\dotnet\sdk\7.0.300\ Host (useful for support): Version: 76.0.5 Commit: 8473146e7d .NET Core SDKs installed: 7.0.200 [C:\Program Files\dotnet\sdk] .NET Core runtimes installed: Microsoft.AspNetCore.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App] Microsoft.NETCore.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App] Microsoft.WindowsDesktop.App 7.0.5 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App] To install additional .NET Core runtimes or SDKs: https://aka.ms/dotnet-download ``` * If you're using .NET 8.0, you should download and install .NET 8.0.101 SDK (for Visual Studio 2022 v17.8) from https://dotnet.microsoft.com/download/dotnet-core/8.0. * If you're using .NET 7.0, you should download and install .NET SDK 7.0.115 (for Visual Studio 2022 v17.4) from https://dotnet.microsoft.com/download/dotnet-core/7.0. * If you're using .NET 6.0, you should download and install .NET SDK 6.0.321 (for Visual Studio 2022 v17.2) from https://dotnet.microsoft.com/download/dotnet-core/6.0. .NET 6.0, .NET 7.0, .NET 8.0 updates are also available from Microsoft Update. To access this either type "Check for updates" in your Windows search, or open Settings, choose Update & Security and then click Check for Updates. Once you have installed the updated runtime or SDK, restart your apps for the update to take effect. Additionally, if you've deployed [self-contained applications](https://docs.microsoft.com/dotnet/core/deploying/#self-contained-deployments-scd) targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. ## Other Information ### Reporting Security Issues If you have found a potential security issue in .NET 8.0 or .NET 7.0 or .NET 6.0, please email details to [email protected]. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at <https://aka.ms/corebounty>. ### Support You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime and https://github.com/dotnet/aspnet/. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue. ### Disclaimer The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply. ### Acknowledgement Morgan Brown, Microsoft Corp.

Source published
9 Jan 2024 19:35:02 UTC
Source modified
7 Aug 2026 08:12:11 UTC
Saved here
23 Oct 2026 16:01:25 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H

Publisher rating · MODERATE

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 22 Nov 17:35 UTC · 274 of 275 readable · 270 fully read · documentation 469/469 current