Author Topic: Post Meltdown, Spectre and other Intel issues  (Read 11006 times)

Offline pin

  • Veteran
  • ****
  • Posts: 1838
  • Karma: 280
    • View Profile
Re: Post Meltdown, Spectre and other Intel issues
« Reply #60 on: January 30, 2018, 12:32:20 pm »

Online VinDSL

  • Administrator
  • Hero
  • *****
  • Posts: 5863
  • Karma: 1137
  • Team Peppermint
    • View Profile
  • Peppermint version(s): Developmental Builds
Re: Post Meltdown, Spectre and other Intel issues
« Reply #61 on: January 30, 2018, 12:36:41 pm »
Then, install it manually using GDebi ...  ;)

Offline pin

  • Veteran
  • ****
  • Posts: 1838
  • Karma: 280
    • View Profile
Re: Post Meltdown, Spectre and other Intel issues
« Reply #62 on: January 30, 2018, 12:40:19 pm »
Thx VinDSL, forgot about that detail  ;)

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26452
  • Karma: 65531
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Post Meltdown, Spectre and other Intel issues
« Reply #63 on: January 30, 2018, 12:49:44 pm »
Better method would be to download the later 0.33 script from the github page (the .deb from the Debian repo contains the older 0.32 script) and run it:
Code: [Select]
cd ~/Desktop
wget https://github.com/speed47/spectre-meltdown-checker/raw/master/spectre-meltdown-checker.sh
chmod +x ~/Desktop/spectre-meltdown-checker.sh
sudo /home/$USER//Desktop/spectre-meltdown-checker.sh
so on my system with the default 4.13.0-32 kernel:-
Code: [Select]
mark@Dell-E6530 ~ $ sudo /home/$USER/Desktop/spectre-meltdown-checker.sh
[sudo] password for mark:
Spectre and Meltdown mitigation detection tool v0.33+

Checking for vulnerabilities on current system
Kernel is Linux 4.13.0-32-generic #35~16.04.1-Ubuntu SMP Thu Jan 25 10:13:43 UTC 2018 x86_64
CPU is Intel(R) Core(TM) i7-3740QM CPU @ 2.70GHz

Hardware check
* Hardware support (CPU microcode) for mitigation techniques
  * Indirect Branch Restricted Speculation (IBRS)
    * SPEC_CTRL MSR is available:  NO
    * CPU indicates IBRS capability:  NO
  * Indirect Branch Prediction Barrier (IBPB)
    * PRED_CMD MSR is available:  NO
    * CPU indicates IBPB capability:  NO
  * Single Thread Indirect Branch Predictors (STIBP)
    * SPEC_CTRL MSR is available:  NO
    * CPU indicates STIBP capability:  NO
  * Enhanced IBRS (IBRS_ALL)
    * CPU indicates ARCH_CAPABILITIES MSR availability:  NO
    * ARCH_CAPABILITIES MSR advertises IBRS_ALL capability:  NO
  * CPU explicitly indicates not being vulnerable to Meltdown (RDCL_NO):  NO
  * CPU microcode is known to cause stability problems:  NO
* CPU vulnerability to the three speculative execution attacks variants
  * Vulnerable to Variant 1:  YES
  * Vulnerable to Variant 2:  YES
  * Vulnerable to Variant 3:  YES

CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
* Kernel has array_index_mask_nospec:  NO
* Checking count of LFENCE opcodes in kernel:  YES  (114 opcodes found, which is >= 70, heuristic to be improved when official patches become available)
> STATUS:  NOT VULNERABLE  (Kernel source has PROBABLY been patched to mitigate the vulnerability (LFENCE opcodes heuristic))

CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
* Mitigation 1
  * Kernel is compiled with IBRS/IBPB support:  YES
  * Currently enabled features
    * IBRS enabled for Kernel space:  NO
    * IBRS enabled for User space:  NO
    * IBPB enabled:  NO
* Mitigation 2
  * Kernel compiled with retpoline option:  NO
  * Kernel compiled with a retpoline-aware compiler:  NO
  * Retpoline enabled:  NO
> STATUS:  VULNERABLE  (IBRS hardware + kernel support OR kernel with retpoline are needed to mitigate the vulnerability)

CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
* Kernel supports Page Table Isolation (PTI):  YES
* PTI enabled and active:  YES
* Running as a Xen PV DomU:  NO
> STATUS:  NOT VULNERABLE  (PTI mitigates the vulnerability)

A false sense of security is worse than no security at all, see --disclaimer
so apparently with the default kernel I'm only vulnerable to one of the three vulnerabilities (Spectre variant 2) .. where your 4.15 kernel appears to be vulnerable to BOTH Spectre variants.



spectre-meltdown-checker on github:
https://github.com/speed47/spectre-meltdown-checker
« Last Edit: January 30, 2018, 01:45:35 pm by PCNetSpec »
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline pin

  • Veteran
  • ****
  • Posts: 1838
  • Karma: 280
    • View Profile
Re: Post Meltdown, Spectre and other Intel issues
« Reply #64 on: January 30, 2018, 01:03:44 pm »
I knew I had linked that github page sometime ago, https://forum.peppermintos.com/index.php/topic,6415.msg65084.html#msg65084
But, maybe it easier with a .deb file for most of the users.
 :)

Anyway, on Void I get a slightly different response. Vulnerable to V1, but not V2 :o... or maybe I should run this as root...
Code: [Select]
CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
* Mitigated according to the /sys interface:  NO  (kernel confirms your system is vulnerable)
* Kernel has array_index_mask_nospec:  UNKNOWN  (couldn't check (missing 'readelf' tool, please install it, usually it's in the 'binutils' package))
* Checking count of LFENCE opcodes in kernel:  UNKNOWN  (couldn't check (missing 'readelf' tool, please install it, usually it's in the 'binutils' package))
> STATUS:  VULNERABLE  (Kernel source needs to be patched to mitigate the vulnerability)

CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
* Mitigated according to the /sys interface:  YES  (kernel confirms that the mitigation is active)
* Mitigation 1
  * Kernel is compiled with IBRS/IBPB support:  NO
  * Currently enabled features
    * IBRS enabled for Kernel space:  NO
    * IBRS enabled for User space:  NO
    * IBPB enabled:  NO
* Mitigation 2
  * Kernel compiled with retpoline option:  YES
  * Kernel compiled with a retpoline-aware compiler:  YES  (kernel reports full retpoline compilation)
  * Retpoline enabled:  YES
> STATUS:  NOT VULNERABLE  (Mitigation: Full generic retpoline)

CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
* Mitigated according to the /sys interface:  YES  (kernel confirms that the mitigation is active)
* Kernel supports Page Table Isolation (PTI):  YES
* PTI enabled and active:  YES
* Running as a Xen PV DomU:  NO
> STATUS:  NOT VULNERABLE  (Mitigation: PTI)

A false sense of security is worse than no security at all, see --disclaimer

EDIT: Same output as root  :o
« Last Edit: January 30, 2018, 01:27:43 pm by pin »

Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26452
  • Karma: 65531
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Post Meltdown, Spectre and other Intel issues
« Reply #65 on: January 30, 2018, 01:11:24 pm »
Dunno why .. it's a command line tool either way.
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec

Offline DAMIEN1307

  • Member
  • ***
  • Posts: 154
  • Karma: 11
  • non illigitamus carborundum est
    • View Profile
  • Peppermint version(s): Peppermint 8.5 (Respin) 64 bit
Re: Post Meltdown, Spectre and other Intel issues
« Reply #66 on: January 30, 2018, 01:33:24 pm »
as per the 4.15 series pin is using...

PCNetSpec wrote "so apparently with the default kernel I'm only vulnerable to one of the three vulnerabilities (Spectre variant 2) .. where your 4.15 kernel appears to be vulnerable to BOTH Spectre variants."

this is what i was trying to refer to...(probably quite badly i might add) when i wrote

" would think then that until the kerfuffle dies down from intel etc that the CPU coupled with usage of 4.15 kernel is probably not enabled/disabled as designed when in use but probably not enabled at all until all patches possible could be applied which would mean its not as readily exploitable but not fixed either...DAMIEN

that was my 2 cents worth...pockets empty now...lol...DAMIEN



ORDO AB CHAO

Offline pin

  • Veteran
  • ****
  • Posts: 1838
  • Karma: 280
    • View Profile
Re: Post Meltdown, Spectre and other Intel issues
« Reply #67 on: January 30, 2018, 01:35:55 pm »
I'm not on the 4.15 series in any of my machines!
PM7 is on 4.4 series and Void is on the 4.14....
VinDSL is on 4.15!

Online VinDSL

  • Administrator
  • Hero
  • *****
  • Posts: 5863
  • Karma: 1137
  • Team Peppermint
    • View Profile
  • Peppermint version(s): Developmental Builds
Re: Post Meltdown, Spectre and other Intel issues
« Reply #68 on: January 30, 2018, 01:36:54 pm »
Think I'll install a Liquorix kernel, for shiggles, and see how it scores  ;D

Offline pin

  • Veteran
  • ****
  • Posts: 1838
  • Karma: 280
    • View Profile
Re: Post Meltdown, Spectre and other Intel issues
« Reply #69 on: January 30, 2018, 01:37:34 pm »
Say that again... a what?

Online VinDSL

  • Administrator
  • Hero
  • *****
  • Posts: 5863
  • Karma: 1137
  • Team Peppermint
    • View Profile
  • Peppermint version(s): Developmental Builds
Re: Post Meltdown, Spectre and other Intel issues
« Reply #70 on: January 30, 2018, 01:44:16 pm »
Say that again... a what?

https://goo.gl/WXjo1U

Used to run it all the time, but not recently ...

Offline pin

  • Veteran
  • ****
  • Posts: 1838
  • Karma: 280
    • View Profile
Re: Post Meltdown, Spectre and other Intel issues
« Reply #71 on: January 30, 2018, 01:50:28 pm »
Cheers! Thx for the link!

Online VinDSL

  • Administrator
  • Hero
  • *****
  • Posts: 5863
  • Karma: 1137
  • Team Peppermint
    • View Profile
  • Peppermint version(s): Developmental Builds
Re: Post Meltdown, Spectre and other Intel issues
« Reply #72 on: January 30, 2018, 02:10:53 pm »
Same ...

Spoiler (click here to view / hide)
[close]

Spoiler (click here to view / hide)
[close]

Online VinDSL

  • Administrator
  • Hero
  • *****
  • Posts: 5863
  • Karma: 1137
  • Team Peppermint
    • View Profile
  • Peppermint version(s): Developmental Builds
Re: Post Meltdown, Spectre and other Intel issues
« Reply #73 on: January 30, 2018, 02:17:43 pm »
It goes without saying, but at this point, I suppose a word of warning doesn't hurt  8)



Offline PCNetSpec

  • Administrator
  • Hero
  • *****
  • Posts: 26452
  • Karma: 65531
  • "-rw-rw-rw-" .. The Number Of The Beast
    • View Profile
    • PCNetSpec
  • Peppermint version(s): Peppermint 10
Re: Post Meltdown, Spectre and other Intel issues
« Reply #74 on: January 30, 2018, 02:20:29 pm »
Yep I got the same .. the liquorix kernel is vulneable to BOTH Spectre variants
Code: [Select]
mark@Dell-E6530 ~ $ uname -a
Linux Dell-E6530 4.14.0-15.2-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.14-22ubuntu1~xenial (2018-01-30) x86_64 x86_64 x86_64 GNU/Linux
mark@Dell-E6530 ~ $ sudo /home/$USER/Desktop/spectre-meltdown-checker.sh
[sudo] password for mark:
Spectre and Meltdown mitigation detection tool v0.33+

Checking for vulnerabilities on current system
Kernel is Linux 4.14.0-15.2-liquorix-amd64 #1 ZEN SMP PREEMPT liquorix 4.14-22ubuntu1~xenial (2018-01-30) x86_64
CPU is Intel(R) Core(TM) i7-3740QM CPU @ 2.70GHz

Hardware check
* Hardware support (CPU microcode) for mitigation techniques
  * Indirect Branch Restricted Speculation (IBRS)
    * SPEC_CTRL MSR is available:  NO
    * CPU indicates IBRS capability:  NO
  * Indirect Branch Prediction Barrier (IBPB)
    * PRED_CMD MSR is available:  NO
    * CPU indicates IBPB capability:  NO
  * Single Thread Indirect Branch Predictors (STIBP)
    * SPEC_CTRL MSR is available:  NO
    * CPU indicates STIBP capability:  NO
  * Enhanced IBRS (IBRS_ALL)
    * CPU indicates ARCH_CAPABILITIES MSR availability:  NO
    * ARCH_CAPABILITIES MSR advertises IBRS_ALL capability:  NO
  * CPU explicitly indicates not being vulnerable to Meltdown (RDCL_NO):  NO
  * CPU microcode is known to cause stability problems:  NO
* CPU vulnerability to the three speculative execution attacks variants
  * Vulnerable to Variant 1:  YES
  * Vulnerable to Variant 2:  YES
  * Vulnerable to Variant 3:  YES

CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
* Mitigated according to the /sys interface:  NO  (kernel confirms your system is vulnerable)
* Kernel has array_index_mask_nospec:  UNKNOWN  (couldn't check (missing 'lzop' tool, please install it, usually it's in the 'lzop' package))
* Checking count of LFENCE opcodes in kernel:  UNKNOWN  (couldn't check (missing 'lzop' tool, please install it, usually it's in the 'lzop' package))
> STATUS:  VULNERABLE  (Kernel source needs to be patched to mitigate the vulnerability)

CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
* Mitigated according to the /sys interface:  NO  (kernel confirms your system is vulnerable)
* Mitigation 1
  * Kernel is compiled with IBRS/IBPB support:  NO
  * Currently enabled features
    * IBRS enabled for Kernel space:  NO
    * IBRS enabled for User space:  NO
    * IBPB enabled:  NO
* Mitigation 2
  * Kernel compiled with retpoline option:  YES
  * Kernel compiled with a retpoline-aware compiler:  NO  (kernel reports minimal retpoline compilation)
  * Retpoline enabled:  YES
> STATUS:  VULNERABLE  (Vulnerable: Minimal generic ASM retpoline)

CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
* Mitigated according to the /sys interface:  YES  (kernel confirms that the mitigation is active)
* Kernel supports Page Table Isolation (PTI):  YES
* PTI enabled and active:  YES
* Running as a Xen PV DomU:  NO
> STATUS:  NOT VULNERABLE  (Mitigation: PTI)

A false sense of security is worse than no security at all, see --disclaimer

Seems the default kernel is the best for now :)
WARNING: You are logged into reality as 'root' .. logging in as 'insane' is the only safe option.

Team Peppermint
PCNetSpec