CVE-2017-0248
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."
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (5.51%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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."
- CVSS 3.0
- 7.5 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- EPSS
- 5.51% probability · 92th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-295
- Affected
- microsoft/.net framework
- Source
- secure@microsoft.com
References
- http://www.securityfocus.com/bid/98117Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038458
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0248Patch, Vendor Advisory
- http://www.securityfocus.com/bid/98117Third Party Advisory, VDB Entry
- http://www.securitytracker.com/id/1038458
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0248Patch, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.