1 SPECTRE - MELTDOWN Checks - Skylake
2 -----------------------------------
4 Following section displays the output of a running shell script to tell if
5 system is vulnerable against the several "speculative execution" CVEs that were
6 made public in 2018. Script is available on `Spectre & Meltdown Checker Github
7 <https://github.com/speed47/spectre-meltdown-checker>`_.
9 - CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
10 - CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
11 - CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
12 - CVE-2018-3640 [rogue system register read] aka 'Variant 3a'
13 - CVE-2018-3639 [speculative store bypass] aka 'Variant 4'
14 - CVE-2018-3615 [L1 terminal fault] aka 'Foreshadow (SGX)'
15 - CVE-2018-3620 [L1 terminal fault] aka 'Foreshadow-NG (OS)'
16 - CVE-2018-3646 [L1 terminal fault] aka 'Foreshadow-NG (VMM)'
19 $ sudo ./spectre-meltdown-checker.sh --no-color
21 Spectre and Meltdown mitigation detection tool v0.40
23 Checking for vulnerabilities on current system
24 Kernel is Linux 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 18:02:16 UTC 2018 x86_64
25 CPU is Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
28 * Hardware support (CPU microcode) for mitigation techniques
29 * Indirect Branch Restricted Speculation (IBRS)
30 * SPEC_CTRL MSR is available: YES
31 * CPU indicates IBRS capability: YES (SPEC_CTRL feature bit)
32 * Indirect Branch Prediction Barrier (IBPB)
33 * PRED_CMD MSR is available: YES
34 * CPU indicates IBPB capability: YES (SPEC_CTRL feature bit)
35 * Single Thread Indirect Branch Predictors (STIBP)
36 * SPEC_CTRL MSR is available: YES
37 * CPU indicates STIBP capability: YES (Intel STIBP feature bit)
38 * Speculative Store Bypass Disable (SSBD)
39 * CPU indicates SSBD capability: NO
40 * L1 data cache invalidation
41 * FLUSH_CMD MSR is available: NO
42 * CPU indicates L1D flush capability: NO
43 * Enhanced IBRS (IBRS_ALL)
44 * CPU indicates ARCH_CAPABILITIES MSR availability: NO
45 * ARCH_CAPABILITIES MSR advertises IBRS_ALL capability: NO
46 * CPU explicitly indicates not being vulnerable to Meltdown (RDCL_NO): NO
47 * CPU explicitly indicates not being vulnerable to Variant 4 (SSB_NO): NO
48 * CPU/Hypervisor indicates L1D flushing is not necessary on this system: NO
49 * Hypervisor indicates host CPU might be vulnerable to RSB underflow (RSBA): NO
50 * CPU supports Software Guard Extensions (SGX): NO
51 * CPU microcode is known to cause stability problems: NO (model 0x55 family 0x6 stepping 0x4 ucode 0x2000043 cpuid 0x50654)
52 * CPU microcode is the latest known available version: NO (latest version is 0x200004d dated 2018/05/15 according to builtin MCExtractor DB v84 - 2018/09/27)
53 * CPU vulnerability to the speculative execution attack variants
54 * Vulnerable to CVE-2017-5753 (Spectre Variant 1, bounds check bypass): YES
55 * Vulnerable to CVE-2017-5715 (Spectre Variant 2, branch target injection): YES
56 * Vulnerable to CVE-2017-5754 (Variant 3, Meltdown, rogue data cache load): YES
57 * Vulnerable to CVE-2018-3640 (Variant 3a, rogue system register read): YES
58 * Vulnerable to CVE-2018-3639 (Variant 4, speculative store bypass): YES
59 * Vulnerable to CVE-2018-3615 (Foreshadow (SGX), L1 terminal fault): NO
60 * Vulnerable to CVE-2018-3620 (Foreshadow-NG (OS), L1 terminal fault): YES
61 * Vulnerable to CVE-2018-3646 (Foreshadow-NG (VMM), L1 terminal fault): YES
63 CVE-2017-5753 aka 'Spectre Variant 1, bounds check bypass'
64 * Mitigated according to the /sys interface: YES (Mitigation: __user pointer sanitization)
65 * Kernel has array_index_mask_nospec: YES (1 occurrence(s) found of x86 64 bits array_index_mask_nospec())
66 * Kernel has the Red Hat/Ubuntu patch: NO
67 * Kernel has mask_nospec64 (arm64): NO
68 > STATUS: NOT VULNERABLE (Mitigation: __user pointer sanitization)
70 CVE-2017-5715 aka 'Spectre Variant 2, branch target injection'
71 * Mitigated according to the /sys interface: YES (Mitigation: Full generic retpoline, IBPB, IBRS_FW)
73 * Kernel is compiled with IBRS support: YES
74 * IBRS enabled and active: YES (for kernel and firmware code)
75 * Kernel is compiled with IBPB support: YES
76 * IBPB enabled and active: YES
78 * Kernel has branch predictor hardening (arm): NO
79 * Kernel compiled with retpoline option: YES
80 * Kernel compiled with a retpoline-aware compiler: YES (kernel reports full retpoline compilation)
81 * Kernel supports RSB filling: YES
82 > STATUS: NOT VULNERABLE (Full retpoline + IBPB are mitigating the vulnerability)
84 CVE-2017-5754 aka 'Variant 3, Meltdown, rogue data cache load'
85 * Mitigated according to the /sys interface: YES (Mitigation: PTI)
86 * Kernel supports Page Table Isolation (PTI): YES
87 * PTI enabled and active: YES
88 * Reduced performance impact of PTI: YES (CPU supports INVPCID, performance impact of PTI will be greatly reduced)
89 * Running as a Xen PV DomU: NO
90 > STATUS: NOT VULNERABLE (Mitigation: PTI)
92 CVE-2018-3640 aka 'Variant 3a, rogue system register read'
93 * CPU microcode mitigates the vulnerability: NO
94 > STATUS: VULNERABLE (an up-to-date CPU microcode is needed to mitigate this vulnerability)
96 CVE-2018-3639 aka 'Variant 4, speculative store bypass'
97 * Mitigated according to the /sys interface: NO (Vulnerable)
98 * Kernel supports speculation store bypass: YES (found in /proc/self/status)
99 > STATUS: VULNERABLE (Your CPU doesn't support SSBD)
101 CVE-2018-3615 aka 'Foreshadow (SGX), L1 terminal fault'
102 * CPU microcode mitigates the vulnerability: N/A
103 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
105 CVE-2018-3620 aka 'Foreshadow-NG (OS), L1 terminal fault'
106 * Kernel supports PTE inversion: NO
107 * PTE inversion enabled and active: UNKNOWN (sysfs interface not available)
108 > STATUS: VULNERABLE (Your kernel doesn't support PTE inversion, update it)
110 CVE-2018-3646 aka 'Foreshadow-NG (VMM), L1 terminal fault'
111 * This system is a host running an hypervisor: NO
113 * EPT is disabled: NO
115 * L1D flush is supported by kernel: NO
116 * L1D flush enabled: UNKNOWN (can't find or read /sys/devices/system/cpu/vulnerabilities/l1tf)
117 * Hardware-backed L1D flush supported: NO (flush will be done in software, this is slower)
118 * Hyper-Threading (SMT) is enabled: YES
119 > STATUS: NOT VULNERABLE (this system is not running an hypervisor)
121 > SUMMARY: CVE-2017-5753:OK CVE-2017-5715:OK CVE-2017-5754:OK CVE-2018-3640:KO CVE-2018-3639:KO CVE-2018-3615:OK CVE-2018-3620:KO CVE-2018-3646:OK
123 Need more detailed information about mitigation options? Use --explain
124 A false sense of security is worse than no security at all, see --disclaimer