CVE-2017-0248: High severity microsoft .net framework 4 vulnerability

Published May 12, 2017
·
Updated

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

Affected Software

46 affected componentsFixes available
nuget/Microsoft.AspNetCore.Mvc.WebApiCompatShim>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc.WebApiCompatShim>=1.0.0<1.0.4
1.0.4
nuget/Microsoft.AspNetCore.Mvc.ViewFeatures>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc.ViewFeatures>=1.0.0<1.0.4
1.0.4
nuget/Microsoft.AspNetCore.Mvc.TagHelpers>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc.TagHelpers>=1.0.0<1.0.4
1.0.4
nuget/Microsoft.AspNetCore.Mvc.Razor>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc.Razor>=1.0.0<1.0.4
1.0.4
nuget/Microsoft.AspNetCore.Mvc.Razor.Host>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc.Razor.Host>=1.0.0<1.0.4
1.0.4
nuget/Microsoft.AspNetCore.Mvc.Localization>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc.Localization>=1.0.0<1.0.4
1.0.4
nuget/Microsoft.AspNetCore.Mvc.Formatters.Xml>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc.Formatters.Xml>=1.0.0<1.0.4
1.0.4
nuget/Microsoft.AspNetCore.Mvc.Formatters.Json>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc.Formatters.Json>=1.0.0<1.0.4
1.0.4
nuget/Microsoft.AspNetCore.Mvc.DataAnnotations>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc.DataAnnotations>=1.0.0<1.0.4
1.0.4
nuget/Microsoft.AspNetCore.Mvc.Cors>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc.Cors>=1.0.0<1.0.4
1.0.4
nuget/Microsoft.AspNetCore.Mvc.ApiExplorer>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc.ApiExplorer>=1.0.0<1.0.4
1.0.4
nuget/Microsoft.AspNetCore.Mvc.Abstractions>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc.Abstractions>=1.0.0<1.0.4
1.0.4
nuget/System.Net.WebSockets.Client=4.3.0
4.3.1
nuget/System.Net.WebSockets.Client=4.0.0
4.0.1
nuget/System.Net.Security=4.3.0
4.3.1
nuget/System.Net.Security=4.0.0
4.0.1
nuget/System.Net.Http.WinHttpHandler=4.3.0
4.3.1
nuget/System.Net.Http.WinHttpHandler=4.0.0
4.0.1
nuget/System.Text.Encodings.Web=4.3.0
4.3.1
nuget/System.Text.Encodings.Web=4.0.0
4.0.1
nuget/System.Net.Http=4.3.1
4.3.2
nuget/System.Net.Http=4.1.1
4.1.2
nuget/Microsoft.AspNetCore.Mvc.Core>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc.Core>=1.0.0<1.0.4
1.0.4
nuget/Microsoft.AspNetCore.Mvc>=1.1.0<1.1.3
1.1.3
nuget/Microsoft.AspNetCore.Mvc>=1.0.0<1.0.4
1.0.4
Microsoft .NET Framework=2.0-sp2
Microsoft .NET Framework=3.5
Microsoft .NET Framework=3.5.1
Microsoft .NET Framework=4.5.2
Microsoft .NET Framework=4.6
Microsoft .NET Framework=4.6.1
Microsoft .NET Framework=4.6.2
Microsoft .NET Framework=4.7

Remediation

Patch Available

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0248

Event History

May 12, 2017
CVE Published
via MITRE·02:00 PM
Data Sourced
via MITRE·02:00 PM
DescriptionWeakness
Oct 16, 2018
Advisory Published
via GitHub·07:58 PM

Frequently Asked Questions

1

What is the severity of CVE-2017-0248?

CVE-2017-0248 is rated as critical due to its potential to allow attackers to bypass security features.

2

How do I fix CVE-2017-0248?

To mitigate CVE-2017-0248, update your Microsoft .NET Framework to a version that is not vulnerable, such as 4.7 or later.

3

What versions of Microsoft .NET Framework are affected by CVE-2017-0248?

CVE-2017-0248 affects Microsoft .NET Framework versions 2.0, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, and 4.7.

4

Can CVE-2017-0248 affect applications using .NET Framework?

Yes, applications relying on the affected versions of the .NET Framework are vulnerable to CVE-2017-0248.

5

Is there a workaround for CVE-2017-0248 if I cannot immediately update?

While updating is the best solution, temporarily strengthening certificate validation might help mitigate the risk until a full update can be applied.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203