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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

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 pinpoints whether GHSA-655q-9gvg-q4cm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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 20.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.

GHSA-655q-9gvg-q4cm: Remote code execution in ASP.NET Core

EPSS Exploitation Probability

via FIRST.org ↗

20.0%probability of exploitation in next 30 days

Moderate Risk97th percentile+9.20%

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.

Blast Radius

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
.NETNuGet	`Microsoft.AspNetCore.App`	≥ 3.1.0&&< 3.1.1	3.1.1
.NETNuGet	`Microsoft.AspNetCore.App`	≥ 3.0.0&&< 3.0.1	3.0.1
.NETNuGet	`Microsoft.AspNetCore.App`	≥ 2.1.0&&< 2.1.15	2.1.15
.NETNuGet	`Microsoft.AspNetCore.Http.Connections`	≥ 1.0.0&&< 1.0.15	1.0.15
.NETNuGet	`Microsoft.AspNetCore.App.Runtime.linux-arm`	≥ 3.1.0&&< 3.1.1	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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 pinpoints whether GHSA-655q-9gvg-q4cm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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.

Frequently Asked Questions

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'.

O3 Security · Impact-Aware SCA

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

O3 detects GHSA-655q-9gvg-q4cm across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-655q-9gvg-q4cm