CVE-2017-0248High

Microsoft security update for CVE-2017-0248 — Microsoft .NET Framework

Published
May 9, 2017
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2017-0248 →

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2017-0248. This page also shows what EchelonGraph holds for CVE-2017-0248, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products70

  • Microsoft .NET Framework 2.0 Service Pack 2 on Windows Server 2008 for 32-bit Systems Service Pack 2
  • Microsoft .NET Framework 2.0 Service Pack 2 on Windows Server 2008 for Itanium-Based Systems Service Pack 2
  • Microsoft .NET Framework 2.0 Service Pack 2 on Windows Server 2008 for x64-based Systems Service Pack 2
  • Microsoft .NET Framework 3.5 on Windows 10 Version 1511 for 32-bit Systems
  • Microsoft .NET Framework 3.5 on Windows 10 Version 1511 for x64-based Systems
  • Microsoft .NET Framework 3.5 on Windows 10 Version 1607 for 32-bit Systems
  • Microsoft .NET Framework 3.5 on Windows 10 Version 1607 for x64-based Systems
  • Microsoft .NET Framework 3.5 on Windows 10 Version 1703 for 32-bit Systems
  • Microsoft .NET Framework 3.5 on Windows 10 Version 1703 for x64-based Systems
  • Microsoft .NET Framework 3.5 on Windows 10 for 32-bit Systems
  • Microsoft .NET Framework 3.5 on Windows 10 for x64-based Systems
  • Microsoft .NET Framework 3.5 on Windows 8.1 for 32-bit systems
  • Microsoft .NET Framework 3.5 on Windows 8.1 for x64-based systems
  • Microsoft .NET Framework 3.5 on Windows Server 2012
  • Microsoft .NET Framework 3.5 on Windows Server 2012 (Server Core installation)
  • Microsoft .NET Framework 3.5 on Windows Server 2012 R2
  • Microsoft .NET Framework 3.5 on Windows Server 2012 R2 (Server Core installation)
  • Microsoft .NET Framework 3.5 on Windows Server 2016
  • Microsoft .NET Framework 3.5 on Windows Server 2016 (Server Core installation)
  • Microsoft .NET Framework 3.5.1 on Windows 7 for 32-bit Systems Service Pack 1
  • Microsoft .NET Framework 3.5.1 on Windows 7 for x64-based Systems Service Pack 1
  • Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for Itanium-Based Systems Service Pack 1
  • Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for x64-based Systems Service Pack 1
  • Microsoft .NET Framework 3.5.1 on Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
  • Microsoft .NET Framework 4.5.2 on Windows 7 for 32-bit Systems Service Pack 1
  • Microsoft .NET Framework 4.5.2 on Windows 7 for x64-based Systems Service Pack 1
  • Microsoft .NET Framework 4.5.2 on Windows 8.1 for 32-bit systems
  • Microsoft .NET Framework 4.5.2 on Windows 8.1 for x64-based systems
  • Microsoft .NET Framework 4.5.2 on Windows RT 8.1
  • Microsoft .NET Framework 4.5.2 on Windows Server 2008 R2 for x64-based Systems Service Pack 1
  • +40 more not shown

✅ Updates Microsoft lists: 12 KB articles and 1 other update

13 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
KB4019115Monthly Rollup—
KB4019109Security Only—
KB4019113Monthly Rollup—
KB4019110Security Only—
KB4019112Monthly Rollup—
KB4019108Security Only—
KB4019114Monthly Rollup—
KB4019111Security Only—
KB4019472Security Update—
KB4019474Security Update—
KB4019473Security Update—
KB4016871Security Update—
—Monthly Rollup—

🧭 EchelonGraph on CVE-2017-0248

EchelonGraph score
7.5 HIGH
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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

Published by Microsoft Corporation, the CVE Numbering Authority that assigned CVE-2017-0248, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (13)