How severe is GHSA-3m2r-q8x3-xmf7?

No CVSS score has been assigned to GHSA-3m2r-q8x3-xmf7 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-3m2r-q8x3-xmf7?

GHSA-3m2r-q8x3-xmf7 affects the following packages: Microsoft.AspNetCore.Server.Kestrel.Core (NuGet), Microsoft.AspNetCore.Server.Kestrel.Transport.Abstractions (NuGet), Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv (NuGet), Microsoft.AspNetCore.All (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-3m2r-q8x3-xmf7?

Update Microsoft.AspNetCore.Server.Kestrel.Core to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3m2r-q8x3-xmf7 is resolved across your whole dependency graph.

How do I detect GHSA-3m2r-q8x3-xmf7 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.AspNetCore.Server.Kestrel.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-3m2r-q8x3-xmf7 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-3m2r-q8x3-xmf7?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3m2r-q8x3-xmf7 can be triaged on real exposure rather than presence alone.

Is GHSA-3m2r-q8x3-xmf7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3m2r-q8x3-xmf7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-3m2r-q8x3-xmf7 published, and has it been updated?

GHSA-3m2r-q8x3-xmf7 was published on October 16, 2018 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

Not in CISA KEV

GHSA-3m2r-q8x3-xmf7 — Microsoft.AspNetCore.Serv…

GHSA-3m2r-q8x3-xmf7 is a security vulnerability in Microsoft.AspNetCore.Server.Kestrel.Core. A fix is available for Microsoft.AspNetCore.Server.Kestrel.Core — see the affected versions and patch details below.

Moderate severity vulnerability that affects Microsoft.AspNetCore.All, Microsoft.AspNetCore.Server.Kestrel.Core, Microsoft.AspNetCore.Server.Kestrel.Transport.Abstractions, and Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv

Published

Oct 16, 2018

Updated

Dec 2, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected

.NETMicrosoft.AspNetCore.Server.Kestrel.Core.NETMicrosoft.AspNetCore.Server.Kestrel.Transport.Abstractions.NETMicrosoft.AspNetCore.Server.Kestrel.Transport.Libuv.NETMicrosoft.AspNetCore.All

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Microsoft made an internal discovery of a security vulnerability in version 2.x of ASP.NET Core where a specially crafted request can cause excess resource consumption in Kestrel.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Microsoft.AspNetCore.Server.Kestrel.Core`	≥ 2.0.0&&< 2.0.3	2.0.3`dotnet add package Microsoft.AspNetCore.Server.Kestrel.Core --version 2.0.3`
.NETNuGet	`Microsoft.AspNetCore.Server.Kestrel.Transport.Abstractions`	≥ 2.0.0&&< 2.0.3	2.0.3`dotnet add package Microsoft.AspNetCore.Server.Kestrel.Transport.Abstractions --version 2.0.3`
.NETNuGet	`Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv`	≥ 2.0.0&&< 2.0.3	2.0.3`dotnet add package Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv --version 2.0.3`
.NETNuGet	`Microsoft.AspNetCore.All`	≥ 2.0.0&&< 2.0.8	2.0.8`dotnet add package Microsoft.AspNetCore.All --version 2.0.8`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.AspNetCore.Server.Kestrel.Core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Microsoft.AspNetCore.Server.Kestrel.Core to 2.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3m2r-q8x3-xmf7 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-3m2r-q8x3-xmf7 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-3m2r-q8x3-xmf7. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Microsoft made an internal discovery of a security vulnerability in version 2.x of ASP.NET Core where a specially crafted request can cause excess resource consumption in Kestrel.

O3 Security · Impact-Aware SCA

Is GHSA-3m2r-q8x3-xmf7 in your dependencies?

O3 Security finds GHSA-3m2r-q8x3-xmf7 across NuGet dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works