Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 4.85% for the current model date.
BlackTreeCVE IntelligenceMicrosoft · ASP.NET Core
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| NuGetMicrosoft.AspNetCore.SpaServices | ECOSYSTEM: introduced 2.2.0; fixed 2.2.7 | 2.2.7 | OSV record ↗aggregator derived · 3 Dec 2024 |
| NuGetMicrosoft.AspNetCore.SpaServices | ECOSYSTEM: introduced 2.1.0; fixed 2.1.13 | 2.1.13 | OSV record ↗aggregator derived · 3 Dec 2024 |
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch availableAn 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'.
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'.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may gain additional privileges.
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'.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may gain additional privileges.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 11 Sept 2019 · Last source change 4 Aug 2024, 18:13 UTC · CWE-20 · Improper Input Validation
Core structured fields are present and their contributing authorities are shown above.