Microsoft Microsoft .Net Framework

10 CVEs affecting Microsoft Microsoft .Net Framework. Latest disclosed: 2019-01-08. Critical: 2, High: 7.

Top CVEs affecting Microsoft Microsoft .Net Framework
CVESeverityScorePublishedSummary
CVE-2018-8540Critical9.82018-12-12A remote code execution vulnerability exists when the Microsoft .NET Framework fails to validate input properly, aka ".NET Framework Remote Code Injection Vuln…
CVE-2018-8421Critical9.82018-09-13A remote code execution vulnerability exists when Microsoft .NET Framework processes untrusted input, aka ".NET Framework Remote Code Execution Vulnerability."…
CVE-2018-8260High8.82018-07-11A Remote Code Execution vulnerability exists in .NET software when the software fails to check the source markup of a file, aka ".NET Framework Remote Code Exe…
CVE-2018-8284High8.12018-07-11A remote code execution vulnerability exists when the Microsoft .NET Framework fails to validate input properly, aka ".NET Framework Remote Code Injection Vuln…
CVE-2018-8202High7.82018-07-11An elevation of privilege vulnerability exists in .NET Framework which could allow an attacker to elevate their privilege level, aka ".NET Framework Elevation…
CVE-2018-1039High7.82018-05-09A security feature bypass vulnerability exists in .Net Framework which could allow an attacker to bypass Device Guard, aka ".NET Framework Device Guard Securit…
CVE-2019-0545High7.52019-01-08An information disclosure vulnerability exists in .NET Framework and .NET Core which allows bypassing Cross-origin Resource Sharing (CORS) configurations, aka…
CVE-2018-8517High7.52018-12-12A denial of service vulnerability exists when .NET Framework improperly handles special web requests, aka ".NET Framework Denial Of Service Vulnerability." Thi…
CVE-2018-8360High7.52018-08-15An information disclosure vulnerability exists in Microsoft .NET Framework that could allow an attacker to access information in multi-tenant environments, aka…
CVE-2018-8356Medium5.52018-07-11A security feature bypass vulnerability exists when Microsoft .NET Framework components do not correctly validate certificates, aka ".NET Framework Security Fe…