NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
.NET
.NET NuGet
Not in CISA KEV
HIGH severity

CVE-2017-0249 — Microsoft.AspNetCore.Mvc

HIGH

CVE-2017-0249 is a high-severity (CVSS 7.3) Improper Input Validation vulnerability in Microsoft.AspNetCore.Mvc. A fix is available for Microsoft.AspNetCore.Mvc — see the affected versions and patch details below.

High severity vulnerability that affects Microsoft.AspNetCore.Mvc

Published
Updated
Affected
39 pkgs
Patched
38 / 39
Exploits
None indexed
Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
4.2%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs91th percentile — riskier than 91% of all scored CVEsHighest risk
3.63%4.52%5.40%6.29%5.8%4.2%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

39 pkgs affected
.NETMicrosoft.AspNetCore.Mvc.NETMicrosoft.AspNetCore.Mvc.NETMicrosoft.AspNetCore.Mvc.Core.NETMicrosoft.AspNetCore.Mvc.Core.NETSystem.Net.Http.NETSystem.Net.Http.NETSystem.Text.Encodings.Web.NETSystem.Text.Encodings.Web+31 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

Affected Packages

39 total 38 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.AspNetCore.Mvc≥ 1.0.0&&< 1.0.41.0.4dotnet add package Microsoft.AspNetCore.Mvc --version 1.0.4
.NETNuGetMicrosoft.AspNetCore.Mvc≥ 1.1.0&&< 1.1.31.1.3dotnet add package Microsoft.AspNetCore.Mvc --version 1.1.3
.NETNuGetMicrosoft.AspNetCore.Mvc.Core≥ 1.0.0&&< 1.0.41.0.4dotnet add package Microsoft.AspNetCore.Mvc.Core --version 1.0.4
.NETNuGetMicrosoft.AspNetCore.Mvc.Core≥ 1.1.0&&< 1.1.31.1.3dotnet add package Microsoft.AspNetCore.Mvc.Core --version 1.1.3
.NETNuGetSystem.Net.Http≥ 4.1.1&&< 4.1.24.1.2dotnet add package System.Net.Http --version 4.1.2
.NETNuGetSystem.Net.Http≥ 4.3.1&&< 4.3.24.3.2dotnet add package System.Net.Http --version 4.3.2

Affected Products

18 products · 101 configurations
Application
asp.net model view controllermicrosoft
7 versions
1.0.01.0.11.0.21.0.31.1.01.1.11.1.2
Application
microsoft.aspnetcore.mvc.abstractionsmicrosoft
7 versions
1.0.01.0.11.0.21.0.31.1.01.1.11.1.2
Application
microsoft.aspnetcore.mvc.apiexplorermicrosoft
7 versions
1.0.01.0.11.0.21.0.31.1.01.1.11.1.2
Application
microsoft.aspnetcore.mvc.corsmicrosoft
7 versions
1.0.01.0.11.0.21.0.31.1.01.1.11.1.2
Application
microsoft.aspnetcore.mvc.dataannotationsmicrosoft
7 versions
1.0.01.0.11.0.21.0.31.1.01.1.11.1.2
Application
microsoft.aspnetcore.mvc.formatters.jsonmicrosoft
7 versions
1.0.01.0.11.0.21.0.31.1.01.1.11.1.2

Detection & mitigation playbook

Open-source dependency
  1. Detect

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

  2. Fix

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

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

Frequently Asked Questions

See https://nvd.nist.gov/vuln/detail/CVE-2017-0249 & https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-0249
O3 Security · Impact-Aware SCA

Is CVE-2017-0249 in your dependencies?

Find it across NuGet, including transitive dependencies.

CVE-2017-0249: Microsoft.AspNetCore.Mvc — Fixed in 1.0.4