How severe is GHSA-655q-9gvg-q4cm?

No CVSS score has been assigned to GHSA-655q-9gvg-q4cm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-655q-9gvg-q4cm?

GHSA-655q-9gvg-q4cm affects the following packages: Microsoft.AspNetCore.All (NuGet), Microsoft.AspNetCore.App (NuGet), Microsoft.AspNetCore.App (NuGet), Microsoft.AspNetCore.App (NuGet), Microsoft.AspNetCore.Http.Connections (NuGet), Microsoft.AspNetCore.App.Runtime.linux-arm (NuGet), Microsoft.AspNetCore.App.Runtime.linux-arm64 (NuGet), Microsoft.AspNetCore.App.Runtime.linux-musl-arm64 (NuGet), and 6 more. Ecosystems affected: NuGet.

How do I fix GHSA-655q-9gvg-q4cm?

Update Microsoft.AspNetCore.All to 2.1.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-655q-9gvg-q4cm is resolved across your whole dependency graph.

How do I detect GHSA-655q-9gvg-q4cm in my NuGet dependencies?

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

How do I mitigate GHSA-655q-9gvg-q4cm 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-655q-9gvg-q4cm?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-655q-9gvg-q4cm can be triaged on real exposure rather than presence alone.

Is GHSA-655q-9gvg-q4cm actively exploited in the wild?

No public exploit code has been indexed for GHSA-655q-9gvg-q4cm 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.

What is the EPSS score for GHSA-655q-9gvg-q4cm?

GHSA-655q-9gvg-q4cm has an EPSS (Exploit Prediction Scoring System) score of 21.0%, placing it in the 97th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is GHSA-655q-9gvg-q4cm?

GHSA-655q-9gvg-q4cm is classified as Out-of-bounds Write (CWE-787). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-655q-9gvg-q4cm published, and has it been updated?

GHSA-655q-9gvg-q4cm was published on May 24, 2022 and was last updated on November 28, 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-655q-9gvg-q4cm — Microsoft.AspNetCore.All

GHSA-655q-9gvg-q4cm is a Out-of-bounds Write vulnerability in Microsoft.AspNetCore.All. EPSS puts its 30-day exploitation probability at 21.0% (97th percentile). A fix is available for Microsoft.AspNetCore.All — see the affected versions and patch details below.

Remote code execution in ASP.NET Core

Also known asBIT-aspnet-core-2020-0603CVE-2020-0603

Published

May 24, 2022

Updated

Nov 28, 2024

Affected

14 pkgs

Patched

14 / 14

Exploits

None indexed

Exploitation data as of Sep 23, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

21.0%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs97th percentile — riskier than 97% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

14 pkgs affected

.NETMicrosoft.AspNetCore.All.NETMicrosoft.AspNetCore.App.NETMicrosoft.AspNetCore.App.NETMicrosoft.AspNetCore.App.NETMicrosoft.AspNetCore.Http.Connections.NETMicrosoft.AspNetCore.App.Runtime.linux-arm.NETMicrosoft.AspNetCore.App.Runtime.linux-arm64.NETMicrosoft.AspNetCore.App.Runtime.linux-musl-arm64+6 more

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

A remote code execution vulnerability exists in ASP.NET Core software when the software fails to handle objects in memory.An attacker who successfully exploited the vulnerability could run arbitrary code in the context of the current user, aka 'ASP.NET Core Remote Code Execution Vulnerability'.

Affected Packages

14 total 14 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Microsoft.AspNetCore.All`	≥ 2.1.0&&< 2.1.15	2.1.15`dotnet add package Microsoft.AspNetCore.All --version 2.1.15`
.NETNuGet	`Microsoft.AspNetCore.App`	≥ 3.1.0&&< 3.1.1	3.1.1`dotnet add package Microsoft.AspNetCore.App --version 3.1.1`
.NETNuGet	`Microsoft.AspNetCore.App`	≥ 3.0.0&&< 3.0.1	3.0.1`dotnet add package Microsoft.AspNetCore.App --version 3.0.1`
.NETNuGet	`Microsoft.AspNetCore.App`	≥ 2.1.0&&< 2.1.15	2.1.15`dotnet add package Microsoft.AspNetCore.App --version 2.1.15`
.NETNuGet	`Microsoft.AspNetCore.Http.Connections`	≥ 1.0.0&&< 1.0.15	1.0.15`dotnet add package Microsoft.AspNetCore.Http.Connections --version 1.0.15`
.NETNuGet	`Microsoft.AspNetCore.App.Runtime.linux-arm`	≥ 3.1.0&&< 3.1.1	3.1.1`dotnet add package Microsoft.AspNetCore.App.Runtime.linux-arm --version 3.1.1`

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.All, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update Microsoft.AspNetCore.All to 2.1.15 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-655q-9gvg-q4cm 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-655q-9gvg-q4cm can be triaged on real exposure rather than presence alone.

Tailored to GHSA-655q-9gvg-q4cm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatCritical

Product	Fixed in	Advisory
.NET Core on Red Hat Enterprise Linux	`rh-dotnet30-dotnet-0:3.0.102-3.el7`	RHSA-2020:0134
Red Hat Enterprise Linux 8	`dotnet3.0-0:3.0.102-2.el8_1`	RHSA-2020:0130

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-655q-9gvg-q4cm in your dependencies?

O3 Security finds GHSA-655q-9gvg-q4cm 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