What is CVE-2017-0247?

CVE-2017-0247 is a high-severity improper input validation vulnerability in Microsoft.AspNetCore.Mvc (nuget), affecting versions >= 1.1.0, < 1.1.3. It is fixed in 1.1.3, 1.0.4, 4.1.2, 4.3.2, 4.0.1, 4.3.1, 4.5.4. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.

How severe is CVE-2017-0247?

CVE-2017-0247 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which packages are affected by CVE-2017-0247?

Microsoft.AspNetCore.Mvc (nuget) versions >= 1.1.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, < 1.0.4.

Is there a fix for CVE-2017-0247?

Yes. CVE-2017-0247 is fixed in 1.1.3, 1.0.4, 4.1.2, 4.3.2, 4.0.1, 4.3.1, 4.5.4. Upgrade to this version or later.

Is CVE-2017-0247 exploitable, and should I be worried?

Whether CVE-2017-0247 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2017-0247 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2017-0247 in Microsoft.AspNetCore.Mvc

Q: How severe is CVE-2017-0247?

CVE-2017-0247 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which packages are affected by CVE-2017-0247?

Microsoft.AspNetCore.Mvc (nuget) versions >= 1.1.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, = 1.0.0, < 1.0.4.

Q: Is there a fix for CVE-2017-0247?

Yes. CVE-2017-0247 is fixed in 1.1.3, 1.0.4, 4.1.2, 4.3.2, 4.0.1, 4.3.1, 4.5.4. Upgrade to this version or later.

Q: Is CVE-2017-0247 exploitable, and should I be worried?

Whether CVE-2017-0247 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2017-0247 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2017-0247?

Upgrade: Microsoft.AspNetCore.Mvc to 1.1.3 or later, Microsoft.AspNetCore.Mvc to 1.0.4 or later, Microsoft.AspNetCore.Mvc.Core to 1.0.4 or later, Microsoft.AspNetCore.Mvc.Core to 1.1.3 or later, System.Net.Http to 4.1.2 or later, System.Net.Http to 4.3.2 or later, System.Text.Encodings.Web to 4.0.1 or later, System.Text.Encodings.Web to 4.3.1 or later, System.Net.Http.WinHttpHandler to 4.0.1 or later, System.Net.Security to 4.0.1 or later, System.Net.Security to 4.3.1 or later, System.Net.WebSockets.Client to 4.0.1 or later, System.Net.WebSockets.Client to 4.3.1 or later, Microsoft.AspNetCore.Mvc.Abstractions to 1.0.4 or later, Microsoft.AspNetCore.Mvc.Abstractions to 1.1.3 or later, Microsoft.AspNetCore.Mvc.ApiExplorer to 1.0.4 or later, Microsoft.AspNetCore.Mvc.ApiExplorer to 1.1.3 or later, Microsoft.AspNetCore.Mvc.Cors to 1.0.4 or later, Microsoft.AspNetCore.Mvc.Cors to 1.1.3 or later, Microsoft.AspNetCore.Mvc.DataAnnotations to 1.0.4 or later, Microsoft.AspNetCore.Mvc.DataAnnotations to 1.1.3 or later, Microsoft.AspNetCore.Mvc.Formatters.Json to 1.0.4 or later, Microsoft.AspNetCore.Mvc.Formatters.Json to 1.1.3 or later, Microsoft.AspNetCore.Mvc.Formatters.Xml to 1.0.4 or later, Microsoft.AspNetCore.Mvc.Formatters.Xml to 1.1.3 or later, Microsoft.AspNetCore.Mvc.Localization to 1.0.4 or later, Microsoft.AspNetCore.Mvc.Localization to 1.1.3 or later, Microsoft.AspNetCore.Mvc.Razor.Host to 1.0.4 or later, Microsoft.AspNetCore.Mvc.Razor.Host to 1.1.3 or later, Microsoft.AspNetCore.Mvc.Razor to 1.0.4 or later, Microsoft.AspNetCore.Mvc.Razor to 1.1.3 or later, Microsoft.AspNetCore.Mvc.TagHelpers to 1.0.4 or later, Microsoft.AspNetCore.Mvc.TagHelpers to 1.1.3 or later, Microsoft.AspNetCore.Mvc.ViewFeatures to 1.0.4 or later, Microsoft.AspNetCore.Mvc.ViewFeatures to 1.1.3 or later, Microsoft.AspNetCore.Mvc.WebApiCompatShim to 1.0.4 or later, Microsoft.AspNetCore.Mvc.WebApiCompatShim to 1.1.3 or later, System.Net.Http.WinHttpHandler to 4.5.4 or later.

Summary

ASP.NET Core fails to properly validate web requests

A denial of service vulnerability exists when the ASP.NET Core fails to properly validate web requests. NOTE: Microsoft has not commented on third-party claims that the issue is that the TextEncoder.EncodeCore function in the System.Text.Encodings.Web package in ASP.NET Core Mvc before 1.0.4 and 1.1.x before 1.1.3 allows remote attackers to cause a denial of service by leveraging failure to properly calculate the length of 4-byte characters in the Unicode Non-Character range.

Impact

The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths. Typical impact: varies by context: data corruption, logic bypass, or denial of service.

CVE-2017-0247 has a CVSS score of 7.5 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.1.3, 1.0.4, 4.1.2, 4.3.2, 4.0.1, 4.3.1, 4.5.4); upgrading removes the vulnerable code path.

Affected versions

Microsoft.AspNetCore.Mvc (>= 1.1.0, < 1.1.3) Microsoft.AspNetCore.Mvc (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.Core (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.Core (>= 1.1.0, < 1.1.3) System.Net.Http (= 4.1.1) System.Net.Http (= 4.3.1) System.Text.Encodings.Web (= 4.0.0) System.Text.Encodings.Web (= 4.3.0) System.Net.Http.WinHttpHandler (= 4.0.0) System.Net.Security (= 4.0.0) System.Net.Security (= 4.3.0) System.Net.WebSockets.Client (= 4.0.0) System.Net.WebSockets.Client (= 4.3.0) Microsoft.AspNetCore.Mvc.Abstractions (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.Abstractions (>= 1.1.0, < 1.1.3) Microsoft.AspNetCore.Mvc.ApiExplorer (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.ApiExplorer (>= 1.1.0, < 1.1.3) Microsoft.AspNetCore.Mvc.Cors (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.Cors (>= 1.1.0, < 1.1.3) Microsoft.AspNetCore.Mvc.DataAnnotations (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.DataAnnotations (>= 1.1.0, < 1.1.3) Microsoft.AspNetCore.Mvc.Formatters.Json (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.Formatters.Json (>= 1.1.0, < 1.1.3) Microsoft.AspNetCore.Mvc.Formatters.Xml (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.Formatters.Xml (>= 1.1.0, < 1.1.3) Microsoft.AspNetCore.Mvc.Localization (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.Localization (>= 1.1.0, < 1.1.3) Microsoft.AspNetCore.Mvc.Razor.Host (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.Razor.Host (>= 1.1.0, < 1.1.3) Microsoft.AspNetCore.Mvc.Razor (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.Razor (>= 1.1.0, < 1.1.3) Microsoft.AspNetCore.Mvc.TagHelpers (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.TagHelpers (>= 1.1.0, < 1.1.3) Microsoft.AspNetCore.Mvc.ViewFeatures (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.ViewFeatures (>= 1.1.0, < 1.1.3) Microsoft.AspNetCore.Mvc.WebApiCompatShim (>= 1.0.0, < 1.0.4) Microsoft.AspNetCore.Mvc.WebApiCompatShim (>= 1.1.0, < 1.1.3) System.Net.Http.WinHttpHandler (>= 4.3.0, < 4.5.4)

Security releases

Microsoft.AspNetCore.Mvc → 1.1.3 (nuget) Microsoft.AspNetCore.Mvc → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.Core → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.Core → 1.1.3 (nuget) System.Net.Http → 4.1.2 (nuget) System.Net.Http → 4.3.2 (nuget) System.Text.Encodings.Web → 4.0.1 (nuget) System.Text.Encodings.Web → 4.3.1 (nuget) System.Net.Http.WinHttpHandler → 4.0.1 (nuget) System.Net.Security → 4.0.1 (nuget) System.Net.Security → 4.3.1 (nuget) System.Net.WebSockets.Client → 4.0.1 (nuget) System.Net.WebSockets.Client → 4.3.1 (nuget) Microsoft.AspNetCore.Mvc.Abstractions → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.Abstractions → 1.1.3 (nuget) Microsoft.AspNetCore.Mvc.ApiExplorer → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.ApiExplorer → 1.1.3 (nuget) Microsoft.AspNetCore.Mvc.Cors → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.Cors → 1.1.3 (nuget) Microsoft.AspNetCore.Mvc.DataAnnotations → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.DataAnnotations → 1.1.3 (nuget) Microsoft.AspNetCore.Mvc.Formatters.Json → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.Formatters.Json → 1.1.3 (nuget) Microsoft.AspNetCore.Mvc.Formatters.Xml → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.Formatters.Xml → 1.1.3 (nuget) Microsoft.AspNetCore.Mvc.Localization → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.Localization → 1.1.3 (nuget) Microsoft.AspNetCore.Mvc.Razor.Host → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.Razor.Host → 1.1.3 (nuget) Microsoft.AspNetCore.Mvc.Razor → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.Razor → 1.1.3 (nuget) Microsoft.AspNetCore.Mvc.TagHelpers → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.TagHelpers → 1.1.3 (nuget) Microsoft.AspNetCore.Mvc.ViewFeatures → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.ViewFeatures → 1.1.3 (nuget) Microsoft.AspNetCore.Mvc.WebApiCompatShim → 1.0.4 (nuget) Microsoft.AspNetCore.Mvc.WebApiCompatShim → 1.1.3 (nuget) System.Net.Http.WinHttpHandler → 4.5.4 (nuget)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

Microsoft.AspNetCore.Mvc to 1.1.3 or later; Microsoft.AspNetCore.Mvc to 1.0.4 or later; Microsoft.AspNetCore.Mvc.Core to 1.0.4 or later; Microsoft.AspNetCore.Mvc.Core to 1.1.3 or later; System.Net.Http to 4.1.2 or later; System.Net.Http to 4.3.2 or later; System.Text.Encodings.Web to 4.0.1 or later; System.Text.Encodings.Web to 4.3.1 or later; System.Net.Http.WinHttpHandler to 4.0.1 or later; System.Net.Security to 4.0.1 or later; System.Net.Security to 4.3.1 or later; System.Net.WebSockets.Client to 4.0.1 or later; System.Net.WebSockets.Client to 4.3.1 or later; Microsoft.AspNetCore.Mvc.Abstractions to 1.0.4 or later; Microsoft.AspNetCore.Mvc.Abstractions to 1.1.3 or later; Microsoft.AspNetCore.Mvc.ApiExplorer to 1.0.4 or later; Microsoft.AspNetCore.Mvc.ApiExplorer to 1.1.3 or later; Microsoft.AspNetCore.Mvc.Cors to 1.0.4 or later; Microsoft.AspNetCore.Mvc.Cors to 1.1.3 or later; Microsoft.AspNetCore.Mvc.DataAnnotations to 1.0.4 or later; Microsoft.AspNetCore.Mvc.DataAnnotations to 1.1.3 or later; Microsoft.AspNetCore.Mvc.Formatters.Json to 1.0.4 or later; Microsoft.AspNetCore.Mvc.Formatters.Json to 1.1.3 or later; Microsoft.AspNetCore.Mvc.Formatters.Xml to 1.0.4 or later; Microsoft.AspNetCore.Mvc.Formatters.Xml to 1.1.3 or later; Microsoft.AspNetCore.Mvc.Localization to 1.0.4 or later; Microsoft.AspNetCore.Mvc.Localization to 1.1.3 or later; Microsoft.AspNetCore.Mvc.Razor.Host to 1.0.4 or later; Microsoft.AspNetCore.Mvc.Razor.Host to 1.1.3 or later; Microsoft.AspNetCore.Mvc.Razor to 1.0.4 or later; Microsoft.AspNetCore.Mvc.Razor to 1.1.3 or later; Microsoft.AspNetCore.Mvc.TagHelpers to 1.0.4 or later; Microsoft.AspNetCore.Mvc.TagHelpers to 1.1.3 or later; Microsoft.AspNetCore.Mvc.ViewFeatures to 1.0.4 or later; Microsoft.AspNetCore.Mvc.ViewFeatures to 1.1.3 or later; Microsoft.AspNetCore.Mvc.WebApiCompatShim to 1.0.4 or later; Microsoft.AspNetCore.Mvc.WebApiCompatShim to 1.1.3 or later; System.Net.Http.WinHttpHandler to 4.5.4 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2017-0247? CVE-2017-0247 is a high-severity improper input validation vulnerability in Microsoft.AspNetCore.Mvc (nuget), affecting versions >= 1.1.0, < 1.1.3. It is fixed in 1.1.3, 1.0.4, 4.1.2, 4.3.2, 4.0.1, 4.3.1, 4.5.4. The application does not adequately validate input before processing it, allowing unexpected values to reach sensitive code paths.
How severe is CVE-2017-0247? CVE-2017-0247 has a CVSS score of 7.5 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which packages are affected by CVE-2017-0247?
- Microsoft.AspNetCore.Mvc (nuget) (versions >= 1.1.0, < 1.1.3)
- Microsoft.AspNetCore.Mvc.Core (nuget) (versions >= 1.0.0, < 1.0.4)
- System.Net.Http (nuget) (versions = 4.1.1)
- System.Text.Encodings.Web (nuget) (versions = 4.0.0)
- System.Net.Http.WinHttpHandler (nuget) (versions = 4.0.0)
- System.Net.Security (nuget) (versions = 4.0.0)
- System.Net.WebSockets.Client (nuget) (versions = 4.0.0)
- Microsoft.AspNetCore.Mvc.Abstractions (nuget) (versions >= 1.0.0, < 1.0.4)
- Microsoft.AspNetCore.Mvc.ApiExplorer (nuget) (versions >= 1.0.0, < 1.0.4)
- Microsoft.AspNetCore.Mvc.Cors (nuget) (versions >= 1.0.0, < 1.0.4)
- Microsoft.AspNetCore.Mvc.DataAnnotations (nuget) (versions >= 1.0.0, < 1.0.4)
- Microsoft.AspNetCore.Mvc.Formatters.Json (nuget) (versions >= 1.0.0, < 1.0.4)
- Microsoft.AspNetCore.Mvc.Formatters.Xml (nuget) (versions >= 1.0.0, < 1.0.4)
- Microsoft.AspNetCore.Mvc.Localization (nuget) (versions >= 1.0.0, < 1.0.4)
- Microsoft.AspNetCore.Mvc.Razor.Host (nuget) (versions >= 1.0.0, < 1.0.4)
- Microsoft.AspNetCore.Mvc.Razor (nuget) (versions >= 1.0.0, < 1.0.4)
- Microsoft.AspNetCore.Mvc.TagHelpers (nuget) (versions >= 1.0.0, < 1.0.4)
- Microsoft.AspNetCore.Mvc.ViewFeatures (nuget) (versions >= 1.0.0, < 1.0.4)
- Microsoft.AspNetCore.Mvc.WebApiCompatShim (nuget) (versions >= 1.0.0, < 1.0.4)
Is there a fix for CVE-2017-0247? Yes. CVE-2017-0247 is fixed in 1.1.3, 1.0.4, 4.1.2, 4.3.2, 4.0.1, 4.3.1, 4.5.4. Upgrade to this version or later.
Is CVE-2017-0247 exploitable, and should I be worried? Whether CVE-2017-0247 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2017-0247 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2017-0247?
- Upgrade Microsoft.AspNetCore.Mvc to 1.1.3 or later
- Upgrade Microsoft.AspNetCore.Mvc to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.Core to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.Core to 1.1.3 or later
- Upgrade System.Net.Http to 4.1.2 or later
- Upgrade System.Net.Http to 4.3.2 or later
- Upgrade System.Text.Encodings.Web to 4.0.1 or later
- Upgrade System.Text.Encodings.Web to 4.3.1 or later
- Upgrade System.Net.Http.WinHttpHandler to 4.0.1 or later
- Upgrade System.Net.Security to 4.0.1 or later
- Upgrade System.Net.Security to 4.3.1 or later
- Upgrade System.Net.WebSockets.Client to 4.0.1 or later
- Upgrade System.Net.WebSockets.Client to 4.3.1 or later
- Upgrade Microsoft.AspNetCore.Mvc.Abstractions to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.Abstractions to 1.1.3 or later
- Upgrade Microsoft.AspNetCore.Mvc.ApiExplorer to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.ApiExplorer to 1.1.3 or later
- Upgrade Microsoft.AspNetCore.Mvc.Cors to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.Cors to 1.1.3 or later
- Upgrade Microsoft.AspNetCore.Mvc.DataAnnotations to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.DataAnnotations to 1.1.3 or later
- Upgrade Microsoft.AspNetCore.Mvc.Formatters.Json to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.Formatters.Json to 1.1.3 or later
- Upgrade Microsoft.AspNetCore.Mvc.Formatters.Xml to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.Formatters.Xml to 1.1.3 or later
- Upgrade Microsoft.AspNetCore.Mvc.Localization to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.Localization to 1.1.3 or later
- Upgrade Microsoft.AspNetCore.Mvc.Razor.Host to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.Razor.Host to 1.1.3 or later
- Upgrade Microsoft.AspNetCore.Mvc.Razor to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.Razor to 1.1.3 or later
- Upgrade Microsoft.AspNetCore.Mvc.TagHelpers to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.TagHelpers to 1.1.3 or later
- Upgrade Microsoft.AspNetCore.Mvc.ViewFeatures to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.ViewFeatures to 1.1.3 or later
- Upgrade Microsoft.AspNetCore.Mvc.WebApiCompatShim to 1.0.4 or later
- Upgrade Microsoft.AspNetCore.Mvc.WebApiCompatShim to 1.1.3 or later
- Upgrade System.Net.Http.WinHttpHandler to 4.5.4 or later

Other vulnerabilities in Microsoft.AspNetCore.Mvc

CVE-IDSeverityPackage summary

CVE-2017-0248MediumMicrosoft.AspNetCore.Mvc: Moderate severity vulnerability that affects Microsoft.AspNetCore.Mvc and Microsoft.AspNetCore.Mvc.Core CVE-2017-0256MediumMicrosoft.AspNetCore.Mvc: Moderate severity vulnerability that affects Microsoft.AspNetCore.Mvc CVE-2017-0249HighMicrosoft.AspNetCore.Mvc: High severity vulnerability that affects Microsoft.AspNetCore.Mvc