Microsoft .NET Framework 2.0 SP2, 3.0 SP2, 3.5, 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, .NET Core 1.0 and 2.0, and PowerShell Core 6.0.0 allow a security feature bypass vulnerability due to the way certificates are validated, aka ".NET Security Feature Bypass Vulnerability."
| Vulnerable Product | Search on Vulmon | Subscribe to Product |
|---|---|---|
microsoft .net core 1.0 |
||
microsoft .net core 2.0 |
||
microsoft powershell core 6.0 |
||
microsoft .net_framework 3.0 |
||
microsoft .net_framework 2.0 |
||
microsoft .net_framework 3.5 |
||
microsoft .net_framework 3.5.1 |
||
microsoft .net_framework 4.5.2 |
||
microsoft .net_framework 4.6 |
||
microsoft .net_framework 4.6.1 |
||
microsoft .net_framework 4.7 |
||
microsoft .net_framework 4.6.2 |
||
microsoft .net_framework 4.7.1 |
It's 2018 and a Word doc can still pwn your Windows computer
Patch Tuesday In case you've been hiding under a rock for the entirety of this new year (and we don't blame you if you have) there are a handful of major security flaws that have been dominating the news, and feature prominently in this month's Patch Tuesday update load. First, let's look at the latest developments in the Meltdown/Spectre saga: Nvidia has got around to kicking out graphics driver updates that address the Spectre flaws present in its code – for example, here are some patches fo...
Vulmon