CVE-2017-0248

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 1.1%, top 22% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 6%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
7.5
EG Score
7.5(medium)
EPSS
91.9%
KEV
Not listed

Published

May 12, 2017

Last Modified

May 13, 2026

Affected Packages

(19 across 1 ecosystem)
NuGet(19)
PackageVulnerable rangeFixed inDependents
Microsoft.AspNetCore.Mvc1.1.0, 1.1.1, 1.1.21.1.3
Microsoft.AspNetCore.Mvc.Abstractions1.1.0, 1.1.1, 1.1.21.1.3
Microsoft.AspNetCore.Mvc.ApiExplorer1.1.0, 1.1.1, 1.1.21.1.3
Microsoft.AspNetCore.Mvc.Core1.1.0, 1.1.1, 1.1.21.1.3
Microsoft.AspNetCore.Mvc.Cors1.1.0, 1.1.1, 1.1.21.1.3
Microsoft.AspNetCore.Mvc.DataAnnotations1.1.0, 1.1.1, 1.1.21.1.3
Microsoft.AspNetCore.Mvc.Formatters.Json1.1.0, 1.1.1, 1.1.21.1.3
Microsoft.AspNetCore.Mvc.Formatters.Xml1.1.0, 1.1.1, 1.1.21.1.3
Microsoft.AspNetCore.Mvc.Localization1.1.0, 1.1.1, 1.1.21.1.3
Microsoft.AspNetCore.Mvc.Razor1.1.0, 1.1.1, 1.1.21.1.3
Microsoft.AspNetCore.Mvc.Razor.Host1.1.0, 1.1.1, 1.1.21.1.3
Microsoft.AspNetCore.Mvc.TagHelpers1.1.0, 1.1.1, 1.1.21.1.3
Microsoft.AspNetCore.Mvc.ViewFeatures1.1.0, 1.1.1, 1.1.21.1.3
Microsoft.AspNetCore.Mvc.WebApiCompatShim1.1.0, 1.1.1, 1.1.21.1.3
System.Net.Http4.3.14.3.2
System.Net.Http.WinHttpHandler4.3.04.3.1
System.Net.Security4.3.04.3.1
System.Net.WebSockets.Client4.3.04.3.1
System.Text.Encodings.Web4.3.04.3.1

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 10× in last 7d / 40× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:43 UTCEPSS rescore
  2. 2026-07-12 05:43 UTCEPSS rescore
  3. 2026-07-11 08:24 UTCEPSS rescore
  4. 2026-07-09 19:06 UTCEPSS rescore
  5. 2026-07-08 15:10 UTCEPSS rescore
  6. 2026-07-07 13:42 UTCEPSS rescore
  7. 2026-07-06 16:24 UTCEPSS rescore
  8. 2026-07-06 16:24 UTCEPSS rescore
  9. 2026-07-06 02:20 UTCEPSS rescore
  10. 2026-07-06 02:20 UTCEPSS rescore
  11. 2026-07-05 02:27 UTCEPSS rescore
  12. 2026-07-04 06:28 UTCEPSS rescore
  13. 2026-07-01 15:02 UTCEPSS rescore
  14. 2026-06-30 23:19 UTCEPSS rescore
  15. 2026-06-30 23:19 UTCEPSS rescore
  16. 2026-06-29 14:03 UTCEPSS rescore
  17. 2026-06-28 14:04 UTCEPSS rescore
  18. 2026-06-28 04:53 UTCEPSS rescore
  19. 2026-06-27 03:05 UTCEPSS rescore
  20. 2026-06-25 13:47 UTCEPSS rescore
  21. 2026-06-24 14:02 UTCEPSS rescore
  22. 2026-06-23 21:30 UTCEPSS rescore
  23. 2026-06-22 14:23 UTCEPSS rescore
  24. 2026-06-21 14:54 UTCEPSS rescore
  25. 2026-06-21 14:54 UTCEPSS rescore
Show 54 more
  1. 2026-06-21 01:57 UTCEPSS rescore
  2. 2026-06-21 01:57 UTCEPSS rescore
  3. 2026-06-19 19:23 UTCEPSS rescore
  4. 2026-06-19 19:23 UTCEPSS rescore
  5. 2026-06-18 17:50 UTCEPSS rescore
  6. 2026-06-18 17:50 UTCEPSS rescore
  7. 2026-06-17 17:50 UTCEPSS rescore
  8. 2026-06-17 17:50 UTCEPSS rescore
  9. 2026-06-16 17:50 UTCEPSS rescore
  10. 2026-06-15 17:45 UTCEPSS rescore
  11. 2026-06-14 23:14 UTCEPSS rescore
  12. 2026-06-14 23:14 UTCEPSS rescore
  13. 2026-06-13 22:57 UTCEPSS rescore
  14. 2026-06-13 22:57 UTCEPSS rescore
  15. 2026-06-12 23:09 UTCEPSS rescore
  16. 2026-06-11 13:57 UTCEPSS rescore
  17. 2026-06-08 14:14 UTCEPSS rescore
  18. 2026-06-07 15:22 UTCEPSS rescore
  19. 2026-06-07 15:22 UTCEPSS rescore
  20. 2026-06-06 13:45 UTCEPSS rescore
  21. 2026-06-06 13:45 UTCEPSS rescore
  22. 2026-06-05 22:44 UTCEPSS rescore
  23. 2026-06-05 06:08 UTCEPSS rescore
  24. 2026-06-05 06:08 UTCEPSS rescore
  25. 2026-06-04 13:10 UTCEPSS rescore
  26. 2026-06-04 13:10 UTCEPSS rescore
  27. 2026-06-02 20:10 UTCEPSS rescore
  28. 2026-06-01 13:49 UTCEPSS rescore
  29. 2026-06-01 13:49 UTCEPSS rescore
  30. 2026-05-31 22:28 UTCEPSS rescore
  31. 2026-05-31 22:28 UTCEPSS rescore
  32. 2026-05-31 00:14 UTCEPSS rescore
  33. 2026-05-29 13:41 UTCEPSS rescore
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-27 13:38 UTCEPSS rescore
  37. 2026-05-27 13:38 UTCEPSS rescore
  38. 2026-05-26 13:42 UTCEPSS rescore
  39. 2026-05-26 13:42 UTCEPSS rescore
  40. 2026-05-26 07:17 UTCEPSS rescore
  41. 2026-05-24 16:44 UTCEPSS rescore
  42. 2026-05-23 00:10 UTCEG score recompute
  43. 2026-05-22 21:15 UTCEPSS rescore
  44. 2026-05-22 13:28 UTCEG score recompute
  45. 2026-05-22 13:28 UTCVendor advisory
  46. 2026-05-20 22:37 UTCEPSS rescore
  47. 2026-05-20 22:37 UTCEPSS rescore
  48. 2026-05-20 22:37 UTCEPSS rescore
  49. 2026-05-20 11:21 UTCEPSS rescore
  50. 2026-05-20 11:21 UTCEPSS rescore
  51. 2026-05-19 13:33 UTCOSV refresh
  52. 2026-05-18 21:30 UTCEPSS rescore
  53. 2026-05-18 21:30 UTCEPSS rescore
  54. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2017-0248?
CVE-2017-0248 is a high vulnerability published on May 12, 2017. 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."
When was CVE-2017-0248 disclosed?
CVE-2017-0248 was first published in the National Vulnerability Database on May 12, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-0248 actively exploited?
CVE-2017-0248 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-0248?
CVE-2017-0248 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2017-0248?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0248, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-0248

Explore →

Is Your Infrastructure Affected by CVE-2017-0248?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.