Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets
Managed socket transport for the ASP.NET Core Kestrel cross-platform web server.
Activity
- Latest release
- 6d ago
- Total releases
- 22
- Cadence
- ~35 days
- Last 12 months
- 6
Details
- First release
- May 10, 2017
| Version | Released | |
|---|---|---|
2.3.13
patch
|
2.3.13
patch
Dependencies (3)
|
|
2.3.12
patch
|
2.3.12
patch
Dependencies (3)
|
|
2.3.11
patch
|
2.3.11
patch
Dependencies (3)
|
|
2.3.10
patch
|
2.3.10
patch
Dependencies (3)
|
|
2.3.9
patch
|
2.3.9
patch
Dependencies (3)
|
|
2.3.8
patch
|
2.3.8
patch
Dependencies (3)
|
|
2.3.0
minor
|
2.3.0
minor
Dependencies (3)
|
|
2.1.40
patch
|
2.1.40
patch
Dependencies (3)
|
|
2.2.1
patch
|
2.2.1
patch
Dependencies (3)
|
|
2.2.0
minor
|
2.2.0
minor
Dependencies (3)
|
|
2.2.0-preview3-35497
pre
|
2.2.0-preview3-35497
pre
Dependencies (3)
|
|
2.2.0-preview2-35157
pre
|
2.2.0-preview2-35157
pre
Dependencies (3)
|
|
2.2.0-preview1-35029
pre
|
2.2.0-preview1-35029
pre
Dependencies (3)
|
|
2.1.3
patch
1 CVE
CVE-2023-38180
GHSA-vmch-3w2x-vhgq
BIT-aspnet-core-2023-38180
BIT-dotnet-2023-38180
BIT-dotnet-sdk-2023-38180
Aug 09, 2023
.NET Denial of Service Vulnerability
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
Microsoft Security Advisory CVE-2023-38180: .NET Denial of Service VulnerabilityExecutive summaryMicrosoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 2.1, .NET 6.0, and .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in Kestrel where, on detecting a potentially malicious client, Kestrel will sometimes fail to disconnect it, resulting in denial of service. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/269 Mitigation factorsIf your application is running behind a reverse proxy, or Web Application Firewall, which has its own mitigations against HTTP based attacks this issue may be mitigated by the proxy or WAF Affected software
If your application uses the following package versions, ensure you update to the latest version of .NET. .NET 7Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 7.0.0, <= 7.0.9 | 7.0.10 .NET 6Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 6.0.0, <= 6.0.20 | 6.0.21 ASP.NET Core 2.1Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | <= 2.1.39 | 2.1.40 Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets | <= 2.1.39 | 2.1.40 Advisory FAQHow 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, you're exposed to the vulnerability. How do I fix the issue?
.NET 6.0 and and .NET 7.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 targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. Other InformationReporting Security IssuesIf you have found a potential security issue in .NET 6.0 or .NET 7.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. SupportYou 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. DisclaimerThe 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 LinksRevisionsV1.0 (August 08, 2023): Advisory published. Version 1.0 Last Updated 2023-08-08 Affected versions
0.0.1-alpha
2.0.0-preview1-final
2.0.0-preview2-final
2.1.0
2.1.0-preview1-final
2.1.0-preview2-final
2.1.0-rc1-final
2.1.1
2.1.2
2.1.3
Fixed in
2.1.40
References
Updated Oct 22, 2025 · Source: OSV.dev |
2.1.3
patch
Dependencies (3)
|
|
2.1.2
patch
1 CVE
CVE-2023-38180
GHSA-vmch-3w2x-vhgq
BIT-aspnet-core-2023-38180
BIT-dotnet-2023-38180
BIT-dotnet-sdk-2023-38180
Aug 09, 2023
.NET Denial of Service Vulnerability
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
Microsoft Security Advisory CVE-2023-38180: .NET Denial of Service VulnerabilityExecutive summaryMicrosoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 2.1, .NET 6.0, and .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in Kestrel where, on detecting a potentially malicious client, Kestrel will sometimes fail to disconnect it, resulting in denial of service. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/269 Mitigation factorsIf your application is running behind a reverse proxy, or Web Application Firewall, which has its own mitigations against HTTP based attacks this issue may be mitigated by the proxy or WAF Affected software
If your application uses the following package versions, ensure you update to the latest version of .NET. .NET 7Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 7.0.0, <= 7.0.9 | 7.0.10 .NET 6Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 6.0.0, <= 6.0.20 | 6.0.21 ASP.NET Core 2.1Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | <= 2.1.39 | 2.1.40 Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets | <= 2.1.39 | 2.1.40 Advisory FAQHow 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, you're exposed to the vulnerability. How do I fix the issue?
.NET 6.0 and and .NET 7.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 targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. Other InformationReporting Security IssuesIf you have found a potential security issue in .NET 6.0 or .NET 7.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. SupportYou 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. DisclaimerThe 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 LinksRevisionsV1.0 (August 08, 2023): Advisory published. Version 1.0 Last Updated 2023-08-08 Affected versions
0.0.1-alpha
2.0.0-preview1-final
2.0.0-preview2-final
2.1.0
2.1.0-preview1-final
2.1.0-preview2-final
2.1.0-rc1-final
2.1.1
2.1.2
2.1.3
Fixed in
2.1.40
References
Updated Oct 22, 2025 · Source: OSV.dev |
2.1.2
patch
Dependencies (3)
|
|
2.1.1
patch
1 CVE
CVE-2023-38180
GHSA-vmch-3w2x-vhgq
BIT-aspnet-core-2023-38180
BIT-dotnet-2023-38180
BIT-dotnet-sdk-2023-38180
Aug 09, 2023
.NET Denial of Service Vulnerability
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
Microsoft Security Advisory CVE-2023-38180: .NET Denial of Service VulnerabilityExecutive summaryMicrosoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 2.1, .NET 6.0, and .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in Kestrel where, on detecting a potentially malicious client, Kestrel will sometimes fail to disconnect it, resulting in denial of service. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/269 Mitigation factorsIf your application is running behind a reverse proxy, or Web Application Firewall, which has its own mitigations against HTTP based attacks this issue may be mitigated by the proxy or WAF Affected software
If your application uses the following package versions, ensure you update to the latest version of .NET. .NET 7Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 7.0.0, <= 7.0.9 | 7.0.10 .NET 6Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 6.0.0, <= 6.0.20 | 6.0.21 ASP.NET Core 2.1Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | <= 2.1.39 | 2.1.40 Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets | <= 2.1.39 | 2.1.40 Advisory FAQHow 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, you're exposed to the vulnerability. How do I fix the issue?
.NET 6.0 and and .NET 7.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 targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. Other InformationReporting Security IssuesIf you have found a potential security issue in .NET 6.0 or .NET 7.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. SupportYou 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. DisclaimerThe 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 LinksRevisionsV1.0 (August 08, 2023): Advisory published. Version 1.0 Last Updated 2023-08-08 Affected versions
0.0.1-alpha
2.0.0-preview1-final
2.0.0-preview2-final
2.1.0
2.1.0-preview1-final
2.1.0-preview2-final
2.1.0-rc1-final
2.1.1
2.1.2
2.1.3
Fixed in
2.1.40
References
Updated Oct 22, 2025 · Source: OSV.dev |
2.1.1
patch
Dependencies (3)
|
|
2.1.0
initial
1 CVE
CVE-2023-38180
GHSA-vmch-3w2x-vhgq
BIT-aspnet-core-2023-38180
BIT-dotnet-2023-38180
BIT-dotnet-sdk-2023-38180
Aug 09, 2023
.NET Denial of Service Vulnerability
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
Microsoft Security Advisory CVE-2023-38180: .NET Denial of Service VulnerabilityExecutive summaryMicrosoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 2.1, .NET 6.0, and .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in Kestrel where, on detecting a potentially malicious client, Kestrel will sometimes fail to disconnect it, resulting in denial of service. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/269 Mitigation factorsIf your application is running behind a reverse proxy, or Web Application Firewall, which has its own mitigations against HTTP based attacks this issue may be mitigated by the proxy or WAF Affected software
If your application uses the following package versions, ensure you update to the latest version of .NET. .NET 7Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 7.0.0, <= 7.0.9 | 7.0.10 .NET 6Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 6.0.0, <= 6.0.20 | 6.0.21 ASP.NET Core 2.1Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | <= 2.1.39 | 2.1.40 Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets | <= 2.1.39 | 2.1.40 Advisory FAQHow 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, you're exposed to the vulnerability. How do I fix the issue?
.NET 6.0 and and .NET 7.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 targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. Other InformationReporting Security IssuesIf you have found a potential security issue in .NET 6.0 or .NET 7.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. SupportYou 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. DisclaimerThe 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 LinksRevisionsV1.0 (August 08, 2023): Advisory published. Version 1.0 Last Updated 2023-08-08 Affected versions
0.0.1-alpha
2.0.0-preview1-final
2.0.0-preview2-final
2.1.0
2.1.0-preview1-final
2.1.0-preview2-final
2.1.0-rc1-final
2.1.1
2.1.2
2.1.3
Fixed in
2.1.40
References
Updated Oct 22, 2025 · Source: OSV.dev |
2.1.0
initial
Dependencies (3)
|
|
2.1.0-rc1-final
pre
1 CVE
CVE-2023-38180
GHSA-vmch-3w2x-vhgq
BIT-aspnet-core-2023-38180
BIT-dotnet-2023-38180
BIT-dotnet-sdk-2023-38180
Aug 09, 2023
.NET Denial of Service Vulnerability
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
Microsoft Security Advisory CVE-2023-38180: .NET Denial of Service VulnerabilityExecutive summaryMicrosoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 2.1, .NET 6.0, and .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in Kestrel where, on detecting a potentially malicious client, Kestrel will sometimes fail to disconnect it, resulting in denial of service. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/269 Mitigation factorsIf your application is running behind a reverse proxy, or Web Application Firewall, which has its own mitigations against HTTP based attacks this issue may be mitigated by the proxy or WAF Affected software
If your application uses the following package versions, ensure you update to the latest version of .NET. .NET 7Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 7.0.0, <= 7.0.9 | 7.0.10 .NET 6Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 6.0.0, <= 6.0.20 | 6.0.21 ASP.NET Core 2.1Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | <= 2.1.39 | 2.1.40 Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets | <= 2.1.39 | 2.1.40 Advisory FAQHow 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, you're exposed to the vulnerability. How do I fix the issue?
.NET 6.0 and and .NET 7.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 targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. Other InformationReporting Security IssuesIf you have found a potential security issue in .NET 6.0 or .NET 7.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. SupportYou 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. DisclaimerThe 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 LinksRevisionsV1.0 (August 08, 2023): Advisory published. Version 1.0 Last Updated 2023-08-08 Affected versions
0.0.1-alpha
2.0.0-preview1-final
2.0.0-preview2-final
2.1.0
2.1.0-preview1-final
2.1.0-preview2-final
2.1.0-rc1-final
2.1.1
2.1.2
2.1.3
Fixed in
2.1.40
References
Updated Oct 22, 2025 · Source: OSV.dev |
2.1.0-rc1-final
pre
Dependencies (3)
|
|
2.1.0-preview2-final
pre
1 CVE
CVE-2023-38180
GHSA-vmch-3w2x-vhgq
BIT-aspnet-core-2023-38180
BIT-dotnet-2023-38180
BIT-dotnet-sdk-2023-38180
Aug 09, 2023
.NET Denial of Service Vulnerability
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
Microsoft Security Advisory CVE-2023-38180: .NET Denial of Service VulnerabilityExecutive summaryMicrosoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 2.1, .NET 6.0, and .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in Kestrel where, on detecting a potentially malicious client, Kestrel will sometimes fail to disconnect it, resulting in denial of service. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/269 Mitigation factorsIf your application is running behind a reverse proxy, or Web Application Firewall, which has its own mitigations against HTTP based attacks this issue may be mitigated by the proxy or WAF Affected software
If your application uses the following package versions, ensure you update to the latest version of .NET. .NET 7Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 7.0.0, <= 7.0.9 | 7.0.10 .NET 6Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 6.0.0, <= 6.0.20 | 6.0.21 ASP.NET Core 2.1Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | <= 2.1.39 | 2.1.40 Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets | <= 2.1.39 | 2.1.40 Advisory FAQHow 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, you're exposed to the vulnerability. How do I fix the issue?
.NET 6.0 and and .NET 7.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 targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. Other InformationReporting Security IssuesIf you have found a potential security issue in .NET 6.0 or .NET 7.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. SupportYou 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. DisclaimerThe 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 LinksRevisionsV1.0 (August 08, 2023): Advisory published. Version 1.0 Last Updated 2023-08-08 Affected versions
0.0.1-alpha
2.0.0-preview1-final
2.0.0-preview2-final
2.1.0
2.1.0-preview1-final
2.1.0-preview2-final
2.1.0-rc1-final
2.1.1
2.1.2
2.1.3
Fixed in
2.1.40
References
Updated Oct 22, 2025 · Source: OSV.dev |
2.1.0-preview2-final
pre
Dependencies (3)
|
|
2.1.0-preview1-final
pre
1 CVE
CVE-2023-38180
GHSA-vmch-3w2x-vhgq
BIT-aspnet-core-2023-38180
BIT-dotnet-2023-38180
BIT-dotnet-sdk-2023-38180
Aug 09, 2023
.NET Denial of Service Vulnerability
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
Microsoft Security Advisory CVE-2023-38180: .NET Denial of Service VulnerabilityExecutive summaryMicrosoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 2.1, .NET 6.0, and .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in Kestrel where, on detecting a potentially malicious client, Kestrel will sometimes fail to disconnect it, resulting in denial of service. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/269 Mitigation factorsIf your application is running behind a reverse proxy, or Web Application Firewall, which has its own mitigations against HTTP based attacks this issue may be mitigated by the proxy or WAF Affected software
If your application uses the following package versions, ensure you update to the latest version of .NET. .NET 7Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 7.0.0, <= 7.0.9 | 7.0.10 .NET 6Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 6.0.0, <= 6.0.20 | 6.0.21 ASP.NET Core 2.1Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | <= 2.1.39 | 2.1.40 Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets | <= 2.1.39 | 2.1.40 Advisory FAQHow 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, you're exposed to the vulnerability. How do I fix the issue?
.NET 6.0 and and .NET 7.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 targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. Other InformationReporting Security IssuesIf you have found a potential security issue in .NET 6.0 or .NET 7.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. SupportYou 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. DisclaimerThe 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 LinksRevisionsV1.0 (August 08, 2023): Advisory published. Version 1.0 Last Updated 2023-08-08 Affected versions
0.0.1-alpha
2.0.0-preview1-final
2.0.0-preview2-final
2.1.0
2.1.0-preview1-final
2.1.0-preview2-final
2.1.0-rc1-final
2.1.1
2.1.2
2.1.3
Fixed in
2.1.40
References
Updated Oct 22, 2025 · Source: OSV.dev |
2.1.0-preview1-final
pre
Dependencies (3)
|
|
2.0.0-preview2-final
pre
1 CVE
CVE-2023-38180
GHSA-vmch-3w2x-vhgq
BIT-aspnet-core-2023-38180
BIT-dotnet-2023-38180
BIT-dotnet-sdk-2023-38180
Aug 09, 2023
.NET Denial of Service Vulnerability
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
Microsoft Security Advisory CVE-2023-38180: .NET Denial of Service VulnerabilityExecutive summaryMicrosoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 2.1, .NET 6.0, and .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in Kestrel where, on detecting a potentially malicious client, Kestrel will sometimes fail to disconnect it, resulting in denial of service. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/269 Mitigation factorsIf your application is running behind a reverse proxy, or Web Application Firewall, which has its own mitigations against HTTP based attacks this issue may be mitigated by the proxy or WAF Affected software
If your application uses the following package versions, ensure you update to the latest version of .NET. .NET 7Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 7.0.0, <= 7.0.9 | 7.0.10 .NET 6Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 6.0.0, <= 6.0.20 | 6.0.21 ASP.NET Core 2.1Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | <= 2.1.39 | 2.1.40 Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets | <= 2.1.39 | 2.1.40 Advisory FAQHow 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, you're exposed to the vulnerability. How do I fix the issue?
.NET 6.0 and and .NET 7.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 targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. Other InformationReporting Security IssuesIf you have found a potential security issue in .NET 6.0 or .NET 7.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. SupportYou 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. DisclaimerThe 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 LinksRevisionsV1.0 (August 08, 2023): Advisory published. Version 1.0 Last Updated 2023-08-08 Affected versions
0.0.1-alpha
2.0.0-preview1-final
2.0.0-preview2-final
2.1.0
2.1.0-preview1-final
2.1.0-preview2-final
2.1.0-rc1-final
2.1.1
2.1.2
2.1.3
Fixed in
2.1.40
References
Updated Oct 22, 2025 · Source: OSV.dev |
2.0.0-preview2-final
pre
Dependencies (3)
|
|
2.0.0-preview1-final
pre
1 CVE
CVE-2023-38180
GHSA-vmch-3w2x-vhgq
BIT-aspnet-core-2023-38180
BIT-dotnet-2023-38180
BIT-dotnet-sdk-2023-38180
Aug 09, 2023
.NET Denial of Service Vulnerability
7.5
/ 10
High
Network
Low
None
None
Unchanged
None
None
High
Microsoft Security Advisory CVE-2023-38180: .NET Denial of Service VulnerabilityExecutive summaryMicrosoft is releasing this security advisory to provide information about a vulnerability in ASP.NET Core 2.1, .NET 6.0, and .NET 7.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. A vulnerability exists in Kestrel where, on detecting a potentially malicious client, Kestrel will sometimes fail to disconnect it, resulting in denial of service. AnnouncementAnnouncement for this issue can be found at https://github.com/dotnet/announcements/issues/269 Mitigation factorsIf your application is running behind a reverse proxy, or Web Application Firewall, which has its own mitigations against HTTP based attacks this issue may be mitigated by the proxy or WAF Affected software
If your application uses the following package versions, ensure you update to the latest version of .NET. .NET 7Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 7.0.0, <= 7.0.9 | 7.0.10 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 7.0.0, <= 7.0.9 | 7.0.10 .NET 6Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-arm64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x64 | >= 6.0.0, <= 6.0.20 | 6.0.21 Microsoft.AspNetCore.App.Runtime.win-x86 | >= 6.0.0, <= 6.0.20 | 6.0.21 ASP.NET Core 2.1Package name | Affected version | Patched version ------------ | ---------------- | ------------------------- Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv | <= 2.1.39 | 2.1.40 Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets | <= 2.1.39 | 2.1.40 Advisory FAQHow 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, you're exposed to the vulnerability. How do I fix the issue?
.NET 6.0 and and .NET 7.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 targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed. Other InformationReporting Security IssuesIf you have found a potential security issue in .NET 6.0 or .NET 7.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. SupportYou 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. DisclaimerThe 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 LinksRevisionsV1.0 (August 08, 2023): Advisory published. Version 1.0 Last Updated 2023-08-08 Affected versions
0.0.1-alpha
2.0.0-preview1-final
2.0.0-preview2-final
2.1.0
2.1.0-preview1-final
2.1.0-preview2-final
2.1.0-rc1-final
2.1.1
2.1.2
2.1.3
Fixed in
2.1.40
References
Updated Oct 22, 2025 · Source: OSV.dev |
2.0.0-preview1-final
pre
Dependencies (3)
|