Skip to content

← Actionable
Unrated

Moderate severity vulnerability that affects Microsoft.AspNetCore.Mvc and Microsoft.AspNetCore.Mvc.Core

CVE-2017-0248GHSA-ch6p-4jcm-h8vh

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (system.text.encodings.web 4.3.1, 4.0.1; microsoft.aspnetcore.mvc.core 1.1.3, 1.0.4; system.net.http.winhttphandler 4.3.1, 4.0.1; microsoft.aspnetcore.mvc.dataannotations 1.1.3, 1.0.4; microsoft.aspnetcore.mvc.webapicompatshim 1.1.3, 1.0.4; 14 more packages under Affected packages), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-ch6p-4jcm-h8vh lists affected ranges: NuGet microsoft.aspnetcore.mvc >=1.0.0 =1.1.0 =1.0.0 =1.1.0 =4.1.1 =4.3.1 =4.0.0 =4.3.0 =4.0.0 =4.3.0 =4.0.0 =4.3.0 =4.0.0…

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2017-0248: 5.51% estimated exploitation activity in the next 30 days; percentile 92.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Microsoft .NET Framework 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2 and 4.7 allow an attacker to bypass Enhanced Security Usage taggings when they present a certificate that is invalid for a specific use, aka ".NET Security Feature Bypass Vulnerability."

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-ch6p-4jcm-h8vh

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2017-0248

Advisory: Moderate severity vulnerability that affects Microsoft.AspNetCore.Mvc and Microsoft.AspNetCore.Mvc.Core
IDs: CVE-2017-0248, GHSA-ch6p-4jcm-h8vh
Record: https://patchnext.com/advisories/cve-2017-0248 (revision 1, source checked 26 Oct 2026, 17:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: system.text.encodings.web 4.3.1, 4.0.1; microsoft.aspnetcore.mvc.core 1.1.3, 1.0.4; system.net.http.winhttphandler 4.3.1, 4.0.1; microsoft.aspnetcore.mvc.dataannotations 1.1.3, 1.0.4; microsoft.aspnetcore.mvc.webapicompatshim 1.1.3, 1.0.4; microsoft.aspnetcore.mvc.razor 1.1.3, 1.0.4; microsoft.aspnetcore.mvc.cors 1.1.3, 1.0.4; microsoft.aspnetcore.mvc.taghelpers 1.1.3, 1.0.4; microsoft.aspnetcore.mvc.razor.host 1.1.3, 1.0.4; microsoft.aspnetcore.mvc 1.1.3, 1.0.4; microsoft.aspnetcore.mvc.abstractions 1.1.3, 1.0.4; microsoft.aspnetcore.mvc.formatters.json 1.1.3, 1.0.4; microsoft.aspnetcore.mvc.viewfeatures 1.1.3, 1.0.4; microsoft.aspnetcore.mvc.formatters.xml 1.1.3, 1.0.4; system.net.http 4.3.2, 4.1.2; microsoft.aspnetcore.mvc.apiexplorer 1.1.3, 1.0.4; system.net.websockets.client 4.3.1, 4.0.1; system.net.security 4.3.1, 4.0.1; microsoft.aspnetcore.mvc.localization 1.1.3, 1.0.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- NuGet system.text.encodings.web: affected >= 4.0.0, <= 4.0.0; >= 4.3.0, <= 4.3.0; fixed in 4.3.1, 4.0.1
- NuGet microsoft.aspnetcore.mvc.core: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3
- NuGet system.net.http.winhttphandler: affected >= 4.0.0, <= 4.0.0; >= 4.3.0, <= 4.3.0; fixed in 4.3.1, 4.0.1
- NuGet microsoft.aspnetcore.mvc.dataannotations: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3
- NuGet microsoft.aspnetcore.mvc.webapicompatshim: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3
- NuGet microsoft.aspnetcore.mvc.razor: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3
- NuGet microsoft.aspnetcore.mvc.cors: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3
- NuGet microsoft.aspnetcore.mvc.taghelpers: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3
- NuGet microsoft.aspnetcore.mvc.razor.host: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3
- NuGet microsoft.aspnetcore.mvc: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3
- NuGet microsoft.aspnetcore.mvc.abstractions: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3
- NuGet microsoft.aspnetcore.mvc.formatters.json: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3
- NuGet microsoft.aspnetcore.mvc.viewfeatures: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3
- NuGet microsoft.aspnetcore.mvc.formatters.xml: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3
- NuGet system.net.http: affected >= 4.1.1, <= 4.1.1; >= 4.3.1, <= 4.3.1; fixed in 4.3.2, 4.1.2
- NuGet microsoft.aspnetcore.mvc.apiexplorer: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3
- NuGet system.net.websockets.client: affected >= 4.0.0, <= 4.0.0; >= 4.3.0, <= 4.3.0; fixed in 4.3.1, 4.0.1
- NuGet system.net.security: affected >= 4.0.0, <= 4.0.0; >= 4.3.0, <= 4.3.0; fixed in 4.3.1, 4.0.1
- NuGet microsoft.aspnetcore.mvc.localization: affected >= 1.0.0, < 1.0.4; >= 1.1.0, < 1.1.3; fixed in 1.0.4, 1.1.3

## Suggested inspection (read-only)
- NuGet system.text.encodings.web: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc.core: check the installed version with your package manager.
- NuGet system.net.http.winhttphandler: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc.dataannotations: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc.webapicompatshim: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc.razor: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc.cors: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc.taghelpers: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc.razor.host: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc.abstractions: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc.formatters.json: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc.viewfeatures: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc.formatters.xml: check the installed version with your package manager.
- NuGet system.net.http: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc.apiexplorer: check the installed version with your package manager.
- NuGet system.net.websockets.client: check the installed version with your package manager.
- NuGet system.net.security: check the installed version with your package manager.
- NuGet microsoft.aspnetcore.mvc.localization: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on system.text.encodings.web, microsoft.aspnetcore.mvc.core, system.net.http.winhttphandler, microsoft.aspnetcore.mvc.dataannotations, microsoft.aspnetcore.mvc.webapicompatshim, microsoft.aspnetcore.mvc.razor, microsoft.aspnetcore.mvc.cors, microsoft.aspnetcore.mvc.taghelpers, microsoft.aspnetcore.mvc.razor.host, microsoft.aspnetcore.mvc, microsoft.aspnetcore.mvc.abstractions, microsoft.aspnetcore.mvc.formatters.json, microsoft.aspnetcore.mvc.viewfeatures, microsoft.aspnetcore.mvc.formatters.xml, system.net.http, microsoft.aspnetcore.mvc.apiexplorer, system.net.websockets.client, system.net.security, microsoft.aspnetcore.mvc.localization.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-ch6p-4jcm-h8vh (GitHub-reviewed advisory GHSA-ch6p-4jcm-h8vh lists affected ranges: NuGet microsoft.aspnetcore.mvc >=1.0.0 =1.1.0 =1.0.0 =1.1.0 =4.1.1 =4.3.1 =4.0.0 =4.3.0 =4.0.0 =4.3.0 =4.0.0 =4.3.0 =4.0.0…)

Commands are suggestions: review each one before running it.

Loading voting…