API tools faq
paste
Guest User

CoffeLake Specre/Meltdown status

a guest
Jun 11th, 2019
505
0
Never
Add comment
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 8.67 KB | None | 0 0
raw download clone embed print report
  1. Spectre and Meltdown mitigation detection tool v0.42
  2.  
  3. Checking for vulnerabilities on current system
  4. Kernel is Linux 4.18.0-21-generic #22~18.04.1-Ubuntu SMP Thu May 16 15:07:19 UTC 2019 x86_64
  5. CPU is Intel(R) Core(TM) i7-8550U CPU @ 1.80GHz
  6.  
  7. Hardware check
  8. * Hardware support (CPU microcode) for mitigation techniques
  9. * Indirect Branch Restricted Speculation (IBRS)
  10. * SPEC_CTRL MSR is available: YES
  11. * CPU indicates IBRS capability: YES (SPEC_CTRL feature bit)
  12. * Indirect Branch Prediction Barrier (IBPB)
  13. * PRED_CMD MSR is available: YES
  14. * CPU indicates IBPB capability: YES (SPEC_CTRL feature bit)
  15. * Single Thread Indirect Branch Predictors (STIBP)
  16. * SPEC_CTRL MSR is available: YES
  17. * CPU indicates STIBP capability: YES (Intel STIBP feature bit)
  18. * Speculative Store Bypass Disable (SSBD)
  19. * CPU indicates SSBD capability: YES (Intel SSBD)
  20. * L1 data cache invalidation
  21. * FLUSH_CMD MSR is available: YES
  22. * CPU indicates L1D flush capability: YES (L1D flush feature bit)
  23. * Microarchitecture Data Sampling
  24. * VERW instruction is available: YES (MD_CLEAR feature bit)
  25. * Enhanced IBRS (IBRS_ALL)
  26. * CPU indicates ARCH_CAPABILITIES MSR availability: NO
  27. * ARCH_CAPABILITIES MSR advertises IBRS_ALL capability: NO
  28. * CPU explicitly indicates not being vulnerable to Meltdown/L1TF (RDCL_NO): NO
  29. * CPU explicitly indicates not being vulnerable to Variant 4 (SSB_NO): NO
  30. * CPU/Hypervisor indicates L1D flushing is not necessary on this system: NO
  31. * Hypervisor indicates host CPU might be vulnerable to RSB underflow (RSBA): NO
  32. * CPU explicitly indicates not being vulnerable to Microarchitectural Data Sampling (MDS_NO): NO
  33. * CPU supports Software Guard Extensions (SGX): YES
  34. * CPU microcode is known to cause stability problems: NO (model 0x8e family 0x6 stepping 0xa ucode 0xb4 cpuid 0x806ea)
  35. * CPU microcode is the latest known available version: YES (latest version is 0xb4 dated 2019/04/01 according to builtin MCExtractor DB v112 - 2019/05/22)
  36. * CPU vulnerability to the speculative execution attack variants
  37. * Vulnerable to CVE-2017-5753 (Spectre Variant 1, bounds check bypass): YES
  38. * Vulnerable to CVE-2017-5715 (Spectre Variant 2, branch target injection): YES
  39. * Vulnerable to CVE-2017-5754 (Variant 3, Meltdown, rogue data cache load): YES
  40. * Vulnerable to CVE-2018-3640 (Variant 3a, rogue system register read): YES
  41. * Vulnerable to CVE-2018-3639 (Variant 4, speculative store bypass): YES
  42. * Vulnerable to CVE-2018-3615 (Foreshadow (SGX), L1 terminal fault): YES
  43. * Vulnerable to CVE-2018-3620 (Foreshadow-NG (OS), L1 terminal fault): YES
  44. * Vulnerable to CVE-2018-3646 (Foreshadow-NG (VMM), L1 terminal fault): YES
  45. * Vulnerable to CVE-2018-12126 (Fallout, microarchitectural store buffer data sampling (MSBDS)): YES
  46. * Vulnerable to CVE-2018-12130 (ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)): YES
  47. * Vulnerable to CVE-2018-12127 (RIDL, microarchitectural load port data sampling (MLPDS)): YES
  48. * Vulnerable to CVE-2019-11091 (RIDL, microarchitectural data sampling uncacheable memory (MDSUM)): YES
  49.  
  50. CVE-2017-5753 aka 'Spectre Variant 1, bounds check bypass'
  51. * Mitigated according to the /sys interface: YES (Mitigation: __user pointer sanitization)
  52. * Kernel has array_index_mask_nospec: YES (1 occurrence(s) found of x86 64 bits array_index_mask_nospec())
  53. * Kernel has the Red Hat/Ubuntu patch: NO
  54. * Kernel has mask_nospec64 (arm64): NO
  55. > STATUS: NOT VULNERABLE (Mitigation: __user pointer sanitization)
  56.  
  57. CVE-2017-5715 aka 'Spectre Variant 2, branch target injection'
  58. * Mitigated according to the /sys interface: YES (Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling)
  59. * Mitigation 1
  60. * Kernel is compiled with IBRS support: YES
  61. * IBRS enabled and active: YES (for firmware code only)
  62. * Kernel is compiled with IBPB support: YES
  63. * IBPB enabled and active: YES
  64. * Mitigation 2
  65. * Kernel has branch predictor hardening (arm): NO
  66. * Kernel compiled with retpoline option: YES
  67. * Kernel compiled with a retpoline-aware compiler: YES (kernel reports full retpoline compilation)
  68. * Kernel supports RSB filling: YES
  69. > STATUS: NOT VULNERABLE (Full retpoline + IBPB are mitigating the vulnerability)
  70.  
  71. CVE-2017-5754 aka 'Variant 3, Meltdown, rogue data cache load'
  72. * Mitigated according to the /sys interface: YES (Mitigation: PTI)
  73. * Kernel supports Page Table Isolation (PTI): YES
  74. * PTI enabled and active: YES
  75. * Reduced performance impact of PTI: YES (CPU supports INVPCID, performance impact of PTI will be greatly reduced)
  76. * Running as a Xen PV DomU: NO
  77. > STATUS: NOT VULNERABLE (Mitigation: PTI)
  78.  
  79. CVE-2018-3640 aka 'Variant 3a, rogue system register read'
  80. * CPU microcode mitigates the vulnerability: YES
  81. > STATUS: NOT VULNERABLE (your CPU microcode mitigates the vulnerability)
  82.  
  83. CVE-2018-3639 aka 'Variant 4, speculative store bypass'
  84. * Mitigated according to the /sys interface: YES (Mitigation: Speculative Store Bypass disabled via prctl and seccomp)
  85. * Kernel supports disabling speculative store bypass (SSB): YES (found in /proc/self/status)
  86. * SSB mitigation is enabled and active: YES (per-thread through prctl)
  87. * SSB mitigation currently active for selected processes: YES (ModemManager mpd systemd-journald systemd-logind systemd-resolved systemd-timesyncd systemd-udevd vivaldi-bin)
  88. > STATUS: NOT VULNERABLE (Mitigation: Speculative Store Bypass disabled via prctl and seccomp)
  89.  
  90. CVE-2018-3615 aka 'Foreshadow (SGX), L1 terminal fault'
  91. * CPU microcode mitigates the vulnerability: YES
  92. > STATUS: NOT VULNERABLE (your CPU microcode mitigates the vulnerability)
  93.  
  94. CVE-2018-3620 aka 'Foreshadow-NG (OS), L1 terminal fault'
  95. * Mitigated according to the /sys interface: YES (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable)
  96. * Kernel supports PTE inversion: YES (found in kernel image)
  97. * PTE inversion enabled and active: YES
  98. > STATUS: NOT VULNERABLE (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable)
  99.  
  100. CVE-2018-3646 aka 'Foreshadow-NG (VMM), L1 terminal fault'
  101. * Information from the /sys interface: Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
  102. * This system is a host running a hypervisor: NO
  103. * Mitigation 1 (KVM)
  104. * EPT is disabled: NO
  105. * Mitigation 2
  106. * L1D flush is supported by kernel: YES (found flush_l1d in /proc/cpuinfo)
  107. * L1D flush enabled: YES (conditional flushes)
  108. * Hardware-backed L1D flush supported: YES (performance impact of the mitigation will be greatly reduced)
  109. * Hyper-Threading (SMT) is enabled: YES
  110. > STATUS: NOT VULNERABLE (this system is not running a hypervisor)
  111.  
  112. CVE-2018-12126 aka 'Fallout, microarchitectural store buffer data sampling (MSBDS)'
  113. * Mitigated according to the /sys interface: YES (Mitigation: Clear CPU buffers; SMT vulnerable)
  114. * Kernel supports using MD_CLEAR mitigation: YES (md_clear found in /proc/cpuinfo)
  115. * Kernel mitigation is enabled and active: YES
  116. * SMT is either mitigated or disabled: NO
  117. > STATUS: NOT VULNERABLE (Mitigation: Clear CPU buffers; SMT vulnerable)
  118.  
  119. CVE-2018-12130 aka 'ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)'
  120. * Mitigated according to the /sys interface: YES (Mitigation: Clear CPU buffers; SMT vulnerable)
  121. * Kernel supports using MD_CLEAR mitigation: YES (md_clear found in /proc/cpuinfo)
  122. * Kernel mitigation is enabled and active: YES
  123. * SMT is either mitigated or disabled: NO
  124. > STATUS: NOT VULNERABLE (Mitigation: Clear CPU buffers; SMT vulnerable)
  125.  
  126. CVE-2018-12127 aka 'RIDL, microarchitectural load port data sampling (MLPDS)'
  127. * Mitigated according to the /sys interface: YES (Mitigation: Clear CPU buffers; SMT vulnerable)
  128. * Kernel supports using MD_CLEAR mitigation: YES (md_clear found in /proc/cpuinfo)
  129. * Kernel mitigation is enabled and active: YES
  130. * SMT is either mitigated or disabled: NO
  131. > STATUS: NOT VULNERABLE (Mitigation: Clear CPU buffers; SMT vulnerable)
  132.  
  133. CVE-2019-11091 aka 'RIDL, microarchitectural data sampling uncacheable memory (MDSUM)'
  134. * Mitigated according to the /sys interface: YES (Mitigation: Clear CPU buffers; SMT vulnerable)
  135. * Kernel supports using MD_CLEAR mitigation: YES (md_clear found in /proc/cpuinfo)
  136. * Kernel mitigation is enabled and active: YES
  137. * SMT is either mitigated or disabled: NO
  138. > STATUS: NOT VULNERABLE (Mitigation: Clear CPU buffers; SMT vulnerable)
  139.  
  140. > SUMMARY: CVE-2017-5753:OK CVE-2017-5715:OK CVE-2017-5754:OK CVE-2018-3640:OK CVE-2018-3639:OK CVE-2018-3615:OK CVE-2018-3620:OK CVE-2018-3646:OK CVE-2018-12126:OK CVE-2018-12130:OK CVE-2018-12127:OK CVE-2019-11091:OK
  141.  
  142. Need more detailed information about mitigation options? Use --explain
  143. A false sense of security is worse than no security at all, see --disclaimer
Advertisement
Add Comment
Please, Sign In to add comment
Public Pastes
We use cookies for various purposes including analytics. By continuing to use Pastebin, you agree to our use of cookies as described in the Cookies Policy.  OK, I Understand
Not a member of Pastebin yet?
Sign Up, it unlocks many cool features!