Welcome!

Please read this important information about Spectre and Meltdown vulnerabilities.
Please read this important information about MX sources lists.
News
  • MX Linux on social media: here
  • Mepis support still here
Current releases
  • MX-17 Final release info here
  • MX-16.1 release info here
  • antiX-17 release info here
    New users
    • Please read this first, and don't forget to add system and hardware information to posts!
    • Read Forum Rules

Script to check for Meltdown and/or Spectre vulnerability

Message
Author
calinb
Forum Novice
Forum  Novice
Posts: 70
Joined: Tue Jun 27, 2017 1:57 am

Architecture FYI, in case anyone's interested.

#31 Postby calinb » Sun Jan 14, 2018 3:27 pm

Raspberry Pi Founder's brief introduction to the CPU concepts and architectures that make Meltdown and Spectre possible:

https://www.raspberrypi.org/blog/why-raspberry-pi-isnt-vulnerable-to-spectre-or-meltdown/

User avatar
Richard
Posts: 1433
Age: 72
Joined: Fri Dec 12, 2008 10:31 am

Re: Script to check for Meltdown and/or Spectre vulnerability

#32 Postby Richard » Sun Jan 14, 2018 3:47 pm

Off-topic:
CP/M 2.2 was great and fast.
Not so pretty but efficient
MX17: T430-2017, 8 GB RAM, 4.14.0-3-amd64, SSD
MX161: .........AA1, 1 GB RAM, 3.16.0-4-686-pae, HDD
DC9, LO544, Dbox, Chrome, Laz, CherryT, Vbox

stsoh
Forum Regular
Forum Regular
Posts: 207
Joined: Sun Aug 20, 2017 10:11 am

Re: Script to check for Meltdown and/or Spectre vulnerability

#33 Postby stsoh » Wed Jan 24, 2018 9:34 am

halfway there........ mitigation 2 of variant 2 + variant 3 not vulnerable.

Code: Select all

Spectre and Meltdown mitigation detection tool v0.32

Checking for vulnerabilities on current system
Kernel is Linux 4.14.15 #1 SMP PREEMPT Wed Jan 24 18:30:48 +08 2018 x86_64
CPU is Pentium(R) Dual-Core  CPU      E5400  @ 2.70GHz

CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
* Mitigated according to the /sys interface:  NO  (kernel confirms your system is vulnerable)
> STATUS:  VULNERABLE  (Vulnerable)

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
  * Hardware support (CPU microcode)
    * 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
  * 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:  NOT VULNERABLE  (your CPU vendor reported your CPU model as not vulnerable)

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 under Xen PV (64 bits):  UNKNOWN  (dmesg truncated, please reboot and relaunch this script)
> STATUS:  NOT VULNERABLE  (your CPU vendor reported your CPU model as not vulnerable)

A false sense of security is worse than no security at all, see --disclaimer
MX-17_x64 Horizon, Intel Dual core E5400, 3145MHz, 8GB RAM, Mesa DRI Intel G41, RTL8169 PCI Gigabit, Intel NM10/ICH7HD Audio
a linux newbie start with googling, finds all answers and solve all problems.

User avatar
timkb4cq
Forum Veteran
Forum Veteran
Posts: 4021
Joined: Wed Jul 12, 2006 4:05 pm

Re: Script to check for Meltdown and/or Spectre vulnerability

#34 Postby timkb4cq » Wed Jan 24, 2018 12:07 pm

Richard wrote:Off-topic:
CP/M 2.2 was great and fast.
Not so pretty but efficient

For it's day, perhaps. But what I remember was Put in Wordstar disk, start the program, go to the kitchen & get a drink while it loaded up. Work efficiently once it was loaded.
MSI 970A-G43 MB, AMD FX-6300 (six core), 16GB RAM, GeForce 730, Samsung 850 EVO 250GB SSD, Seagate Barracuda XT 3TB

User avatar
Richard
Posts: 1433
Age: 72
Joined: Fri Dec 12, 2008 10:31 am

Re: Script to check for Meltdown and/or Spectre vulnerability

#35 Postby Richard » Wed Jan 24, 2018 2:38 pm

yes the floppy was slow
but my Kaypro with 10 MB hard drive
seemed instantaneous. :)
MX17: T430-2017, 8 GB RAM, 4.14.0-3-amd64, SSD
MX161: .........AA1, 1 GB RAM, 3.16.0-4-686-pae, HDD
DC9, LO544, Dbox, Chrome, Laz, CherryT, Vbox

stsoh
Forum Regular
Forum Regular
Posts: 207
Joined: Sun Aug 20, 2017 10:11 am

Re: Script to check for Meltdown and/or Spectre vulnerability

#36 Postby stsoh » Fri Jan 26, 2018 4:09 pm

Code: Select all

Spectre and Meltdown mitigation detection tool v0.33

Checking for vulnerabilities on current system
Kernel is Linux 4.14.15 #1 SMP PREEMPT Wed Jan 24 18:30:48 +08 2018 x86_64
CPU is Pentium(R) Dual-Core  CPU      E5400  @ 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:  NO
  * Vulnerable to Variant 3:  NO

CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
* Mitigated according to the /sys interface:  NO  (kernel confirms your system is vulnerable)
> STATUS:  VULNERABLE  (Vulnerable)

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:  NOT VULNERABLE  (your CPU vendor reported your CPU model as not vulnerable)

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  (your CPU vendor reported your CPU model as not vulnerable)

A false sense of security is worse than no security at all, see --disclaimer
MX-17_x64 Horizon, Intel Dual core E5400, 3145MHz, 8GB RAM, Mesa DRI Intel G41, RTL8169 PCI Gigabit, Intel NM10/ICH7HD Audio
a linux newbie start with googling, finds all answers and solve all problems.


Return to “General”

Who is online

Users browsing this forum: No registered users and 6 guests