Utility for mitigations CVE-2017-5715 and CVE-2017-5754 status check

For those who have trouble with PowerShell script mentioned in the article I took named PowerShell script and turned it into .Net application (built with .Net framework 4.5).

http://www.mediafire.com/file/2321zihyiaefbzj/MitigationStatus.zip
MD5 hash for zip-file: D49BAAB27D509F0428069D714B99A082

As a bonus application has two buttons for disabling these mitigations and for enabling them back (through registry values mentioned in the article). But for these actions application should be started as Administrator.

Text in window of tool can be selected (either whole with Ctrl+A or partially) and copied to clipboard.

Update: Ashampoo has released a small free standalone Meltdowsn Spectre Cpu checker utility, which shows whether your system is currently vulnerable to one or both of these exploits
https://www.ashampoo.com/en/usd/pin/1304/security-software/spectre-meltdown-cpu-checker

Update: GNU/Linux status checker
https://www.ghacks.net/2018/01/11/check-linux-for-spectre-or-meltdown-vulnerability/

Update: Interpretation of information printed by original PowerShell version of mitigation status check
https://support.microsoft.com/en-us...-of-get-speculationcontrolsettings-powershell

 

you make us all another helpful tool? ?

Spoiler

Code:

PS C:\Windows\system32> Get-SpeculationControlSettings
Speculation control settings for CVE-2017-5715 [branch target injection]

Hardware support for branch target injection mitigation is present: False
Windows OS support for branch target injection mitigation is present: True
Windows OS support for branch target injection mitigation is enabled: False
Windows OS support for branch target injection mitigation is disabled by system policy: False
Windows OS support for branch target injection mitigation is disabled by absence of hardware support: True

Speculation control settings for CVE-2017-5754 [rogue data cache load]

Hardware requires kernel VA shadowing: True
Windows OS support for kernel VA shadow is present: True
Windows OS support for kernel VA shadow is enabled: True
Windows OS support for PCID optimization is enabled: True

Suggested actions

 * Install BIOS/firmware update provided by your device OEM that enables hardware support for the branch target injectio
n mitigation.
 * Follow the guidance for enabling Windows support for speculation control mitigations are described in https://support
.microsoft.com/help/4072698


BTIHardwarePresent             : False
BTIWindowsSupportPresent       : True
BTIWindowsSupportEnabled       : False
BTIDisabledBySystemPolicy      : False
BTIDisabledByNoHardwareSupport : True
KVAShadowRequired              : True
KVAShadowWindowsSupportPresent : True
KVAShadowWindowsSupportEnabled : True
KVAShadowPcidEnabled           : True

I am assuming this means patchs there but inactive till get needed microcode updates?

 

Inactive only mitigation for CVE-2017-5715 [branch target injection]. Second one is active. SO your rig is half-protected.

I should do it earlier, seeing several guys were unable to run PowerShell command, but thought just did not come.

 

yah i am having issue tring to run power shell commands on my dads pc it looks installed but sey Get-SpeculationControlSettings dont work
*edit*
i got it on his too dads pc says

Spoiler

Code:

PS C:\WINDOWS\system32> Get-SpeculationControlSettings
Speculation control settings for CVE-2017-5715 [branch target injection]

Hardware support for branch target injection mitigation is present: False
Windows OS support for branch target injection mitigation is present: True
Windows OS support for branch target injection mitigation is enabled: False
Windows OS support for branch target injection mitigation is disabled by system policy: False
Windows OS support for branch target injection mitigation is disabled by absence of hardware support: True

Speculation control settings for CVE-2017-5754 [rogue data cache load]

Hardware requires kernel VA shadowing: True
Windows OS support for kernel VA shadow is present: True
Windows OS support for kernel VA shadow is enabled: True
Windows OS support for PCID performance optimization is enabled: False [not required for security]

Suggested actions

 * Install BIOS/firmware update provided by your device OEM that enables hardware support for the branch target injectio
n mitigation.


BTIHardwarePresent             : False
BTIWindowsSupportPresent       : True
BTIWindowsSupportEnabled       : False
BTIDisabledBySystemPolicy      : False
BTIDisabledByNoHardwareSupport : True
KVAShadowRequired              : True
KVAShadowWindowsSupportPresent : True
KVAShadowWindowsSupportEnabled : True
KVAShadowPcidEnabled           : False

 

http://www.mediafire.com/file/2321zihyiaefbzj/MitigationStatus.zip
And utility got a little bonus - block of information about processor (name, description and CPUID).

 

Thanks so much for this! It makes our lives a little bit easier

 

Thanks so much for this!

 

Thank you very much mbk1969

 

tool

Code:

Speculation control settings for CVE-2017-5715 [branch target injection]

Hardware support for branch target injection mitigation is present: False
Windows OS support for branch target injection mitigation is present:False
Windows OS support for branch target injection mitigation is enabled: False



Speculation control settings for CVE-2017-5754 [rogue data cache load]

Hardware requires kernel VA shadowing: True
Windows OS support for kernel VA shadow is present: True
Windows OS support for kernel VA shadow is enabled: True
Windows OS support for PCID performance optimization is enabled: True [not required for security]



Additional CPU information

Name: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Description: Intel64 Family 6 Model 94 Stepping 3
CPUID: 000506E3

Powershell test

Code:

PS C:\Windows\system32> Get-SpeculationControlSettings
Speculation control settings for CVE-2017-5715 [branch target injection]

Hardware support for branch target injection mitigation is present: False
Windows OS support for branch target injection mitigation is present: True
Windows OS support for branch target injection mitigation is enabled: False
Windows OS support for branch target injection mitigation is disabled by system policy: False
Windows OS support for branch target injection mitigation is disabled by absence of hardware support: True

Speculation control settings for CVE-2017-5754 [rogue data cache load]

Hardware requires kernel VA shadowing: True
Windows OS support for kernel VA shadow is present: True
Windows OS support for kernel VA shadow is enabled: True
Windows OS support for PCID optimization is enabled: True

Suggested actions

 * Install BIOS/firmware update provided by your device OEM that enables hardware support for the branch target injectio
n mitigation.
 * Follow the guidance for enabling Windows support for speculation control mitigations are described in https://support
.microsoft.com/help/4072698


BTIHardwarePresent             : False
BTIWindowsSupportPresent       : True
BTIWindowsSupportEnabled       : False
BTIDisabledBySystemPolicy      : False
BTIDisabledByNoHardwareSupport : True
KVAShadowRequired              : True
KVAShadowWindowsSupportPresent : True
KVAShadowWindowsSupportEnabled : True
KVAShadowPcidEnabled           : True

there is discrepancy in there

your tool says
Windows OS support for branch target injection mitigation is present:False

power shell says
Windows OS support for branch target injection mitigation is present: True

which is correct and which is wrong?

 

Source file for tool is at work, so I can`t tell right now. Btw, you can locate "SpeculationControl.psm1" and check the version inside. I downloaded script of "Version 1.3.":

Code:

function Get-SpeculationControlSettings {
  <#
  .SYNOPSIS
  This function queries the speculation control settings for the system.
  .DESCRIPTION
  This function queries the speculation control settings for the system.
  Version 1.3.
 
  #>

If you installed psm1-file of older version you can update it. Btw, "psm1" means "PowerShell Module" (with "1" just ignored traditional suffix appended to extension of all PowerShell script files).

 

ok i got it to update to this

https://www.powershellgallery.com/packages/SpeculationControl/1.0.3

using update-module command it it got 1.0.3 installed which now present in"C:\Program Files\WindowsPowerShell\Modules\SpeculationControl" but there is 1.0.1 and 1.0.3 folder now the if PS is using 1.0.3 or 1.0.1 module for the Get-SpeculationControlSettings command i dont know but it still say the opposite of what yours does

 

Getting this:


Speculation control settings for CVE-2017-5715 [branch target injection]

Hardware support for branch target injection mitigation is present: False
Windows OS support for branch target injection mitigation is present:False
Windows OS support for branch target injection mitigation is enabled: False



Speculation control settings for CVE-2017-5754 [rogue data cache load]

Hardware requires kernel VA shadowing: True
Windows OS support for kernel VA shadow is present: False
Windows OS support for kernel VA shadow is enabled: False



Protected or not protected? I managed to get the latest micro code installed with VMWare utility and after running your utility as admin nothing changes even after rebooting.

 

Not protected at all. Have you installed Windows updates lately?
It happens that VMware method of microcode update fails to assist namely in security mitigations because it is loaded by OS on too late stage, when kernel already turned mitigations off due to lack of HW support.

PS Also try this updated version
http://www.mediafire.com/file/2321zihyiaefbzj/MitigationStatus.zip

 

http://www.mediafire.com/file/2321zihyiaefbzj/MitigationStatus.zip

Try this updated version. Also try to execute as Administrator just to check whether it matters.

 

Ashampoo has released a small free standalone Meltdowsn Spectre Cpu checker utility, which shows whether your system is currently vulnerable to one or both of these exploits
https://www.ashampoo.com/en/usd/pin/1304/security-software/spectre-meltdown-cpu-checker

So you can try it too.

 

I have tried my utility in Win7 and looks like Win API function used for checking of mitigations status doesn`t work in Win7.

Update: Probably, this behaviour is normal for Win7 without installed Specter/Metldown updates.

 

Gives me an error on my Ivy Bridge machine. Your NET tool works fine though, gives the same results as PS script.

 

Haven't tried your tool yet but on WIndows 7 did you tried it without previously installed Windows Management Framework 5.1?

 

For sure. I have a work rig which has no access to internet and we can`t update anything on it (don`t ask).

WMI is used in that utility but only to obtain information about CPU (and I added a piece for obtaining info about OS). But main part of utility is Win API function NtQuerySystemInformation, and it returns error on Win7:
STATUS_INVALID_INFO_CLASS - 0xC0000003L - The specified information class is not a valid information class for the specified object.

 

I don't have any problem with your tool

Code:

Speculation control settings for CVE-2017-5715 [branch target injection]

Hardware support for branch target injection mitigation is present: True
Windows OS support for branch target injection mitigation is present:True
Windows OS support for branch target injection mitigation is enabled: True



Speculation control settings for CVE-2017-5754 [rogue data cache load]

Hardware requires kernel VA shadowing: True
Windows OS support for kernel VA shadow is present: True
Windows OS support for kernel VA shadow is enabled: True
Windows OS support for PCID performance optimization is enabled: False [not required for security]



Additional CPU information

Name: Intel(R) Core(TM) i5-4690K CPU @ 3.50GHz
Description: Intel64 Family 6 Model 60 Stepping 3
CPUID: 000306C3



Additional OS information

Name: Microsoft Windows 7 Ultimate
Architecture: 64-bit
Build: 7601
SKU: 1
Service Pack: 1.0