Spectre and Meltdown mitigation detection tool v0.42

Checking for vulnerabilities on current system
Kernel is Linux 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1+deb9u2 (2019-05-13) x86_64
CPU is Intel(R) Core(TM)2 CPU P8600 @ 2.40GHz

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
    • Speculative Store Bypass Disable (SSBD)
      • CPU indicates SSBD capability: NO
    • L1 data cache invalidation
      • FLUSH_CMD MSR is available: NO
      • CPU indicates L1D flush capability: NO
    • Microarchitecture Data Sampling
      • VERW instruction is available: 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/L1TF (RDCL_NO): NO
    • CPU explicitly indicates not being vulnerable to Variant 4 (SSB_NO): NO
    • CPU/Hypervisor indicates L1D flushing is not necessary on this system: NO
    • Hypervisor indicates host CPU might be vulnerable to RSB underflow (RSBA): NO
    • CPU explicitly indicates not being vulnerable to Microarchitectural Data Sampling (MDS_NO): NO
    • CPU supports Software Guard Extensions (SGX): NO
    • CPU microcode is known to cause stability problems: NO (model 0x17 family 0x6 stepping 0xa ucode 0x0 cpuid 0x1067a)
    • CPU microcode is the latest known available version: NO (latest version is 0xa0e dated 2015/07/29 according to builtin MCExtractor DB v112 - 2019/05/22)
  • CPU vulnerability to the speculative execution attack variants
    • Vulnerable to CVE-2017-5753 (Spectre Variant 1, bounds check bypass): YES
    • Vulnerable to CVE-2017-5715 (Spectre Variant 2, branch target injection): YES
    • Vulnerable to CVE-2017-5754 (Variant 3, Meltdown, rogue data cache load): YES
    • Vulnerable to CVE-2018-3640 (Variant 3a, rogue system register read): YES
    • Vulnerable to CVE-2018-3639 (Variant 4, speculative store bypass): YES
    • Vulnerable to CVE-2018-3615 (Foreshadow (SGX), L1 terminal fault): NO
    • Vulnerable to CVE-2018-3620 (Foreshadow-NG (OS), L1 terminal fault): YES
    • Vulnerable to CVE-2018-3646 (Foreshadow-NG (VMM), L1 terminal fault): YES
    • Vulnerable to CVE-2018-12126 (Fallout, microarchitectural store buffer data sampling (MSBDS)): YES
    • Vulnerable to CVE-2018-12130 (ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)): YES
    • Vulnerable to CVE-2018-12127 (RIDL, microarchitectural load port data sampling (MLPDS)): YES
    • Vulnerable to CVE-2019-11091 (RIDL, microarchitectural data sampling uncacheable memory (MDSUM)): YES

CVE-2017-5753 aka 'Spectre Variant 1, bounds check bypass'

  • Mitigated according to the /sys interface: YES (Mitigation: __user pointer sanitization)
  • Kernel has array_index_mask_nospec: YES (1 occurrence(s) found of x86 64 bits array_index_mask_nospec())
  • Kernel has the Red Hat/Ubuntu patch: NO
  • Kernel has mask_nospec64 (arm64): NO

    STATUS: NOT VULNERABLE (Mitigation: __user pointer sanitization)

CVE-2017-5715 aka 'Spectre Variant 2, branch target injection'

  • Mitigated according to the /sys interface: YES (Mitigation: Full generic retpoline, STIBP: disabled, RSB filling)
  • Mitigation 1
    • Kernel is compiled with IBRS support: YES
      • IBRS enabled and active: NO
    • Kernel is compiled with IBPB support: YES
      • IBPB enabled and active: NO
  • Mitigation 2
    • Kernel has branch predictor hardening (arm): NO
    • Kernel compiled with retpoline option: YES
      • Kernel compiled with a retpoline-aware compiler: YES (kernel reports full retpoline compilation)

    STATUS: NOT VULNERABLE (Full retpoline is mitigating the vulnerability)

CVE-2017-5754 aka 'Variant 3, Meltdown, rogue data cache load'

  • Mitigated according to the /sys interface: YES (Mitigation: PTI)
  • Kernel supports Page Table Isolation (PTI): YES
    • PTI enabled and active: YES
    • Reduced performance impact of PTI: NO (PCID/INVPCID not supported, performance impact of PTI will be significant)
  • Running as a Xen PV DomU: NO

    STATUS: NOT VULNERABLE (Mitigation: PTI)

CVE-2018-3640 aka 'Variant 3a, rogue system register read'

  • CPU microcode mitigates the vulnerability: NO

    STATUS: VULNERABLE (an up-to-date CPU microcode is needed to mitigate this vulnerability)

CVE-2018-3639 aka 'Variant 4, speculative store bypass'

  • Mitigated according to the /sys interface: NO (Vulnerable)
  • Kernel supports disabling speculative store bypass (SSB): YES (found in /proc/self/status)
  • SSB mitigation is enabled and active: NO

    STATUS: VULNERABLE (Your CPU doesn't support SSBD)

CVE-2018-3615 aka 'Foreshadow (SGX), L1 terminal fault'

  • CPU microcode mitigates the vulnerability: N/A

    STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)

CVE-2018-3620 aka 'Foreshadow-NG (OS), L1 terminal fault'

  • Mitigated according to the /sys interface: YES (Mitigation: PTE Inversion; VMX: EPT disabled)
  • Kernel supports PTE inversion: YES (found in kernel image)
  • PTE inversion enabled and active: YES

    STATUS: NOT VULNERABLE (Mitigation: PTE Inversion; VMX: EPT disabled)

CVE-2018-3646 aka 'Foreshadow-NG (VMM), L1 terminal fault'

  • Information from the /sys interface: Mitigation: PTE Inversion; VMX: EPT disabled
  • This system is a host running a hypervisor: NO
  • Mitigation 1 (KVM)
    • EPT is disabled: YES
  • Mitigation 2
    • L1D flush is supported by kernel: YES (found flush_l1d in kernel image)
    • L1D flush enabled: NO
    • Hardware-backed L1D flush supported: NO (flush will be done in software, this is slower)
    • Hyper-Threading (SMT) is enabled: NO

    STATUS: NOT VULNERABLE (this system is not running a hypervisor)

CVE-2018-12126 aka 'Fallout, microarchitectural store buffer data sampling (MSBDS)'

  • Mitigated according to the /sys interface: NO (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)
  • Kernel supports using MD_CLEAR mitigation: YES (found md_clear implementation evidence in kernel image)
  • Kernel mitigation is enabled and active: NO
  • SMT is either mitigated or disabled: YES

    STATUS: VULNERABLE (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)

CVE-2018-12130 aka 'ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)'

  • Mitigated according to the /sys interface: NO (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)
  • Kernel supports using MD_CLEAR mitigation: YES (found md_clear implementation evidence in kernel image)
  • Kernel mitigation is enabled and active: NO
  • SMT is either mitigated or disabled: YES

    STATUS: VULNERABLE (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)

CVE-2018-12127 aka 'RIDL, microarchitectural load port data sampling (MLPDS)'

  • Mitigated according to the /sys interface: NO (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)
  • Kernel supports using MD_CLEAR mitigation: YES (found md_clear implementation evidence in kernel image)
  • Kernel mitigation is enabled and active: NO
  • SMT is either mitigated or disabled: YES

    STATUS: VULNERABLE (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)

CVE-2019-11091 aka 'RIDL, microarchitectural data sampling uncacheable memory (MDSUM)'

  • Mitigated according to the /sys interface: NO (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)
  • Kernel supports using MD_CLEAR mitigation: YES (found md_clear implementation evidence in kernel image)
  • Kernel mitigation is enabled and active: NO
  • SMT is either mitigated or disabled: YES

    STATUS: VULNERABLE (Vulnerable: Clear CPU buffers attempted, no microcode; SMT disabled)

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:OK CVE-2018-3646:OK CVE-2018-12126:KO CVE-2018-12130:KO CVE-2018-12127:KO CVE-2019-11091:KO

Edit
Pub: 18 Jun 2019 23:13 UTC
Views: 279