How severe is CVE-2019-1302?

CVE-2019-1302 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2019-1302?

CVE-2019-1302 affects the following packages: Microsoft.AspNetCore.SpaServices (NuGet), Microsoft.AspNetCore.SpaServices (NuGet). Ecosystems affected: NuGet.

How do I fix CVE-2019-1302?

Update Microsoft.AspNetCore.SpaServices to 2.2.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-1302 is resolved across your whole dependency graph.

How do I detect CVE-2019-1302 in my NuGet dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.AspNetCore.SpaServices. 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 CVE-2019-1302 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 CVE-2019-1302?

O3 pinpoints whether CVE-2019-1302 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 CVE-2019-1302 actively exploited in the wild?

No public exploit code has been indexed for CVE-2019-1302 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 type of vulnerability is CVE-2019-1302?

CVE-2019-1302 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2019-1302 published, and has it been updated?

CVE-2019-1302 was published on September 11, 2019 and was last updated on July 8, 2026. 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

CVE-2019-1302

HIGH

CVE-2019-1302 is a high-severity (CVSS 8.8) Improper Input Validation vulnerability in Microsoft.AspNetCore.SpaServices. O3 Security confirms whether CVE-2019-1302 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Elevation of privilege in ASP.NET Core

Also known asGHSA-xr8f-59pp-rxxh

Published

Sep 11, 2019

Updated

Jul 8, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

.NETMicrosoft.AspNetCore.SpaServices.NETMicrosoft.AspNetCore.SpaServices

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

An elevation of privilege vulnerability exists when a ASP.NET Core web application, created using vulnerable project templates, fails to properly sanitize web requests, aka 'ASP.NET Core Elevation Of Privilege Vulnerability'.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Microsoft.AspNetCore.SpaServices`	≥ 2.2.0&&< 2.2.7	2.2.7
.NETNuGet	`Microsoft.AspNetCore.SpaServices`	≥ 2.1.0&&< 2.1.13	2.1.13

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.SpaServices. 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.SpaServices to 2.2.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2019-1302 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 CVE-2019-1302 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 CVE-2019-1302. 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 CVE-2019-1302 in your dependencies?

O3 detects CVE-2019-1302 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