How severe is GHSA-3rp6-rjw4-cq39?

GHSA-3rp6-rjw4-cq39 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-3rp6-rjw4-cq39?

GHSA-3rp6-rjw4-cq39 affects the following packages: Microsoft.AspNetCore.Mvc.Core (NuGet), Microsoft.AspNetCore.Mvc.Core (NuGet), Microsoft.AspNetCore.Mvc.Cors (NuGet), Microsoft.AspNetCore.Mvc.Cors (NuGet). Ecosystems affected: NuGet.

How do I fix GHSA-3rp6-rjw4-cq39?

Update Microsoft.AspNetCore.Mvc.Core to 1.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3rp6-rjw4-cq39 is resolved across your whole dependency graph.

How do I detect GHSA-3rp6-rjw4-cq39 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.AspNetCore.Mvc.Core. 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-3rp6-rjw4-cq39 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-3rp6-rjw4-cq39?

O3 pinpoints whether GHSA-3rp6-rjw4-cq39 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-3rp6-rjw4-cq39 actively exploited in the wild?

No public exploit code has been indexed for GHSA-3rp6-rjw4-cq39 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-3rp6-rjw4-cq39 published, and has it been updated?

GHSA-3rp6-rjw4-cq39 was published on May 13, 2022 and was last updated on December 5, 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

GHSA-3rp6-rjw4-cq39

HIGH

GHSA-3rp6-rjw4-cq39 is a high-severity (CVSS 7.5) vulnerability in Microsoft.AspNetCore.Mvc.Core. O3 Security confirms whether GHSA-3rp6-rjw4-cq39 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Cross-origin Resource Sharing bypass in ASP.NET Core

Also known asCVE-2017-8700

Published

May 13, 2022

Updated

Dec 5, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Blast Radius

4 pkgs affected

.NETMicrosoft.AspNetCore.Mvc.Core.NETMicrosoft.AspNetCore.Mvc.Core.NETMicrosoft.AspNetCore.Mvc.Cors.NETMicrosoft.AspNetCore.Mvc.Cors

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

ASP.NET Core 1.0, 1.1, and 2.0 allow an attacker to bypass Cross-origin Resource Sharing (CORS) configurations and retrieve normally restricted content from a web application, aka "ASP.NET Core Information Disclosure Vulnerability".

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Microsoft.AspNetCore.Mvc.Core`	≥ 1.0.0&&< 1.0.6	1.0.6
.NETNuGet	`Microsoft.AspNetCore.Mvc.Core`	≥ 1.1.0&&< 1.1.6	1.1.6
.NETNuGet	`Microsoft.AspNetCore.Mvc.Cors`	≥ 1.0.0&&< 1.0.6	1.0.6
.NETNuGet	`Microsoft.AspNetCore.Mvc.Cors`	≥ 1.1.0&&< 1.1.6	1.1.6

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.Mvc.Core. 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.Mvc.Core to 1.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3rp6-rjw4-cq39 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-3rp6-rjw4-cq39 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-3rp6-rjw4-cq39. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-3rp6-rjw4-cq39 in your dependencies?

O3 detects GHSA-3rp6-rjw4-cq39 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