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
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.0.4, 1.1.3, 4.1.2, 4.3.2, 4.0.1, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
Summary
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."
Timeline
- CVE published
- Record last updated
Affected versions
- Microsoft Corporation Microsoft .NET Framework
Version range not reported
- Microsoft.AspNetCore.MvcNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.MvcNuGet
From 1.1.0 · fixed in 1.1.3
- Microsoft.AspNetCore.Mvc.CoreNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.Mvc.CoreNuGet
From 1.1.0 · fixed in 1.1.3
- System.Net.HttpNuGet
From 4.1.1 · fixed in 4.1.2
- System.Net.HttpNuGet
From 4.3.1 · fixed in 4.3.2
- System.Text.Encodings.WebNuGet
From 4.0.0 · fixed in 4.0.1
- System.Text.Encodings.WebNuGet
From 4.3.0 · fixed in 4.3.1
- System.Net.Http.WinHttpHandlerNuGet
From 4.0.0 · fixed in 4.0.1
- System.Net.Http.WinHttpHandlerNuGet
From 4.3.0 · fixed in 4.3.1
- System.Net.SecurityNuGet
From 4.0.0 · fixed in 4.0.1
- System.Net.SecurityNuGet
From 4.3.0 · fixed in 4.3.1
- System.Net.WebSockets.ClientNuGet
From 4.0.0 · fixed in 4.0.1
- System.Net.WebSockets.ClientNuGet
From 4.3.0 · fixed in 4.3.1
- Microsoft.AspNetCore.Mvc.AbstractionsNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.Mvc.AbstractionsNuGet
From 1.1.0 · fixed in 1.1.3
- Microsoft.AspNetCore.Mvc.ApiExplorerNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.Mvc.ApiExplorerNuGet
From 1.1.0 · fixed in 1.1.3
- Microsoft.AspNetCore.Mvc.CorsNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.Mvc.CorsNuGet
From 1.1.0 · fixed in 1.1.3
- Microsoft.AspNetCore.Mvc.DataAnnotationsNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.Mvc.DataAnnotationsNuGet
From 1.1.0 · fixed in 1.1.3
- Microsoft.AspNetCore.Mvc.Formatters.JsonNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.Mvc.Formatters.JsonNuGet
From 1.1.0 · fixed in 1.1.3
- Microsoft.AspNetCore.Mvc.Formatters.XmlNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.Mvc.Formatters.XmlNuGet
From 1.1.0 · fixed in 1.1.3
- Microsoft.AspNetCore.Mvc.LocalizationNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.Mvc.LocalizationNuGet
From 1.1.0 · fixed in 1.1.3
- Microsoft.AspNetCore.Mvc.Razor.HostNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.Mvc.Razor.HostNuGet
From 1.1.0 · fixed in 1.1.3
- Microsoft.AspNetCore.Mvc.RazorNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.Mvc.RazorNuGet
From 1.1.0 · fixed in 1.1.3
- Microsoft.AspNetCore.Mvc.TagHelpersNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.Mvc.TagHelpersNuGet
From 1.1.0 · fixed in 1.1.3
- Microsoft.AspNetCore.Mvc.ViewFeaturesNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.Mvc.ViewFeaturesNuGet
From 1.1.0 · fixed in 1.1.3
- Microsoft.AspNetCore.Mvc.WebApiCompatShimNuGet
From 1.0.0 · fixed in 1.0.4
- Microsoft.AspNetCore.Mvc.WebApiCompatShimNuGet
From 1.1.0 · fixed in 1.1.3