Auf heise war folgender artikel veröffentlicht worden:
[Only registered and activated users can see links. Click Here To Register...]
Das verlinkte prüfwerkzeig habe ich benuzt und nachfolgende Ausgabe in der Powershell erhalten:
PS C:\Windows\system32> z:
PS Z:\> cd SpeculationControl
PS Z:\SpeculationControl> SaveExecutionPolicy = Get-ExecutionPolicy
#
SaveExecutionPolicy : The term 'SaveExecutionPolicy' is not recognized as the name of a cmdlet, function, script
file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:1 char:1
+ SaveExecutionPolicy = Get-ExecutionPolicy
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (SaveExecutionPolicy:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS Z:\SpeculationControl> .\SpeculationControl.psd1
PS Z:\SpeculationControl> Import-Module .\SpeculationControl.psd1
Import-Module : File Z:\SpeculationControl\SpeculationControl.psm1 cannot be loaded because running scripts is
disabled on this system. For more information, see about_Execution_Policies at
[Only registered and activated users can see links. Click Here To Register...].
At line:1 char:1
+ Import-Module .\SpeculationControl.psd1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : SecurityError: (:) [Import-Module], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess,Microsoft.PowerShell.Commands.I mportModuleCommand
PS Z:\SpeculationControl> Set-ExecutionPolicy RemoteSigned
PS Z:\SpeculationControl> Import-Module .\SpeculationControl.psd1
PS Z:\SpeculationControl> Get-SpeculationControlSettings
Speculation control settings for CVE-2017-5715 [branch target injection]
For more information about the output below, please refer to [Only registered and activated users can see links. Click Here To Register...]
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
Suggested actions
* Install BIOS/firmware update provided by your device OEM that enables hardware support for the branch target injecti
on mitigation.
* Install the latest available updates for Windows with support for speculation control mitigations.
* Follow the guidance for enabling Windows Client support for speculation control mitigations described in [Only registered and activated users can see links. Click Here To Register...]
port.microsoft.com/help/4073119
BTIHardwarePresent : False
BTIWindowsSupportPresent : False
BTIWindowsSupportEnabled : False
BTIDisabledBySystemPolicy : False
BTIDisabledByNoHardwareSupport : False
KVAShadowRequired : True
KVAShadowWindowsSupportPresent : False
KVAShadowWindowsSupportEnabled : False
KVAShadowPcidEnabled : False
MEin Laptop ist ein HP2170p, neustes Bios ist drauf, ob HP nochwas rausgibt, weis ich nicht. Das lezte Update von Microsoft vom 3.1.2018 hatte ich versucht zu instalieren, ergab aus bislang ungeklärten gründen eine n bluscrenn, per windows update wurde mir noch nix angeboten.
Das updatepack von winfuture hatte ich verwendet, bis auf KB4056897 konnte ich alle instalieren.
Diese update verursachte bei mir reproduzierbar einen bluescreen.
Leider wei ich nicht, was ich noch machen kann un d ob meine cpu betroffen ist, ich vermute, das die betroffen ist.
Weis jemand genaueres oder hätte inweise am lager?
Besten Dank im voraus.
Gruß
Verleihnix
[Only registered and activated users can see links. Click Here To Register...]
Das verlinkte prüfwerkzeig habe ich benuzt und nachfolgende Ausgabe in der Powershell erhalten:
PS C:\Windows\system32> z:
PS Z:\> cd SpeculationControl
PS Z:\SpeculationControl> SaveExecutionPolicy = Get-ExecutionPolicy
#
SaveExecutionPolicy : The term 'SaveExecutionPolicy' is not recognized as the name of a cmdlet, function, script
file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct
and try again.
At line:1 char:1
+ SaveExecutionPolicy = Get-ExecutionPolicy
+ ~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (SaveExecutionPolicy:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS Z:\SpeculationControl> .\SpeculationControl.psd1
PS Z:\SpeculationControl> Import-Module .\SpeculationControl.psd1
Import-Module : File Z:\SpeculationControl\SpeculationControl.psm1 cannot be loaded because running scripts is
disabled on this system. For more information, see about_Execution_Policies at
[Only registered and activated users can see links. Click Here To Register...].
At line:1 char:1
+ Import-Module .\SpeculationControl.psd1
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : SecurityError: (:) [Import-Module], PSSecurityException
+ FullyQualifiedErrorId : UnauthorizedAccess,Microsoft.PowerShell.Commands.I mportModuleCommand
PS Z:\SpeculationControl> Set-ExecutionPolicy RemoteSigned
PS Z:\SpeculationControl> Import-Module .\SpeculationControl.psd1
PS Z:\SpeculationControl> Get-SpeculationControlSettings
Speculation control settings for CVE-2017-5715 [branch target injection]
For more information about the output below, please refer to [Only registered and activated users can see links. Click Here To Register...]
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
Suggested actions
* Install BIOS/firmware update provided by your device OEM that enables hardware support for the branch target injecti
on mitigation.
* Install the latest available updates for Windows with support for speculation control mitigations.
* Follow the guidance for enabling Windows Client support for speculation control mitigations described in [Only registered and activated users can see links. Click Here To Register...]
port.microsoft.com/help/4073119
BTIHardwarePresent : False
BTIWindowsSupportPresent : False
BTIWindowsSupportEnabled : False
BTIDisabledBySystemPolicy : False
BTIDisabledByNoHardwareSupport : False
KVAShadowRequired : True
KVAShadowWindowsSupportPresent : False
KVAShadowWindowsSupportEnabled : False
KVAShadowPcidEnabled : False
MEin Laptop ist ein HP2170p, neustes Bios ist drauf, ob HP nochwas rausgibt, weis ich nicht. Das lezte Update von Microsoft vom 3.1.2018 hatte ich versucht zu instalieren, ergab aus bislang ungeklärten gründen eine n bluscrenn, per windows update wurde mir noch nix angeboten.
Das updatepack von winfuture hatte ich verwendet, bis auf KB4056897 konnte ich alle instalieren.
Diese update verursachte bei mir reproduzierbar einen bluescreen.
Leider wei ich nicht, was ich noch machen kann un d ob meine cpu betroffen ist, ich vermute, das die betroffen ist.
Weis jemand genaueres oder hätte inweise am lager?
Besten Dank im voraus.
Gruß
Verleihnix