Microsoft Security Advisory CVE-2025-26682: .NET Denial of Service Vulnerability #64476
leecow
announced in
Security advisories
Replies: 2 comments
-
|
@leecow |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
@tboby this has do with certain code flow patterns where resources are allocated before the resource limit check. Using this flow is the "improper" bit. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Microsoft Security Advisory CVE-2025-26682: .NET Denial of Service Vulnerability
Executive summary
Microsoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 9.0, and ASP.NET Core 8.0. This advisory also provides guidance on what developers can do to update their applications to address this vulnerability.
A vulnerability exists in ASP.NET Core where using HTTP/3 improperly may result in a Denial of Service by allocation of resources without limits or throttling.
Announcement
Announcement for this issue can be found at dotnet/announcements#352
Mitigation factors
Microsoft has not identified any mitigating factors for this vulnerability.
Affected software
Affected Packages
The vulnerability affects any Microsoft .NET Core project if it uses any of affected packages versions listed below
ASP.NET Core 9
ASP.NET Core 8
Advisory FAQ
How do I know if I am affected?
If you have a runtime or SDK with a version listed, or an affected package listed in affected software or affected packages, you're exposed to the vulnerability.
How do I fix the issue?
dotnet --infocommand. You will see output like the following;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 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 9.0, please email details to secure@microsoft.com. 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/aspnetcore. 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.
External Links
Acknowledgement
CVE-2025-26682
Revisions
V1.0 (April 8, 2025): Advisory published.
Version 1.0
Last Updated 2025-04-08
Beta Was this translation helpful? Give feedback.
All reactions