1 Spectre and Meltdown Checks
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>`_.
11 Spectre and Meltdown mitigation detection tool v0.44+
13 Checking for vulnerabilities on current system
14 Kernel is Linux 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 x86_64
15 CPU is Intel(R) Xeon(R) Platinum 8180 CPU @ 2.50GHz
18 * Hardware support (CPU microcode) for mitigation techniques
19 * Indirect Branch Restricted Speculation (IBRS)
20 * SPEC_CTRL MSR is available: YES
21 * CPU indicates IBRS capability: YES (SPEC_CTRL feature bit)
22 * Indirect Branch Prediction Barrier (IBPB)
23 * PRED_CMD MSR is available: YES
24 * CPU indicates IBPB capability: YES (SPEC_CTRL feature bit)
25 * Single Thread Indirect Branch Predictors (STIBP)
26 * SPEC_CTRL MSR is available: YES
27 * CPU indicates STIBP capability: YES (Intel STIBP feature bit)
28 * Speculative Store Bypass Disable (SSBD)
29 * CPU indicates SSBD capability: YES (Intel SSBD)
30 * L1 data cache invalidation
31 * FLUSH_CMD MSR is available: YES
32 * CPU indicates L1D flush capability: YES (L1D flush feature bit)
33 * Microarchitectural Data Sampling
34 * VERW instruction is available: YES (MD_CLEAR feature bit)
35 * Enhanced IBRS (IBRS_ALL)
36 * CPU indicates ARCH_CAPABILITIES MSR availability: NO
37 * ARCH_CAPABILITIES MSR advertises IBRS_ALL capability: NO
38 * CPU explicitly indicates not being vulnerable to Meltdown/L1TF (RDCL_NO): NO
39 * CPU explicitly indicates not being vulnerable to Variant 4 (SSB_NO): NO
40 * CPU/Hypervisor indicates L1D flushing is not necessary on this system: NO
41 * Hypervisor indicates host CPU might be vulnerable to RSB underflow (RSBA): NO
42 * CPU explicitly indicates not being vulnerable to Microarchitectural Data Sampling (MDS_NO): NO
43 * CPU explicitly indicates not being vulnerable to TSX Asynchronous Abort (TAA_NO): NO
44 * CPU explicitly indicates not being vulnerable to iTLB Multihit (PSCHANGE_MSC_NO): NO
45 * CPU explicitly indicates having MSR for TSX control (TSX_CTRL_MSR): NO
46 * CPU supports Transactional Synchronization Extensions (TSX): YES (RTM feature bit)
47 * CPU supports Software Guard Extensions (SGX): NO
48 * CPU supports Special Register Buffer Data Sampling (SRBDS): NO
49 * CPU microcode is known to cause stability problems: NO (family 0x6 model 0x55 stepping 0x4 ucode 0x2000065 cpuid 0x50654)
50 * CPU microcode is the latest known available version: NO (latest version is 0x2006b06 dated 2021/03/08 according to builtin firmwares DB v191+i20210217)
51 * CPU vulnerability to the speculative execution attack variants
52 * Affected by CVE-2017-5753 (Spectre Variant 1, bounds check bypass): YES
53 * Affected by CVE-2017-5715 (Spectre Variant 2, branch target injection): YES
54 * Affected by CVE-2017-5754 (Variant 3, Meltdown, rogue data cache load): YES
55 * Affected by CVE-2018-3640 (Variant 3a, rogue system register read): YES
56 * Affected by CVE-2018-3639 (Variant 4, speculative store bypass): YES
57 * Affected by CVE-2018-3615 (Foreshadow (SGX), L1 terminal fault): NO
58 * Affected by CVE-2018-3620 (Foreshadow-NG (OS), L1 terminal fault): YES
59 * Affected by CVE-2018-3646 (Foreshadow-NG (VMM), L1 terminal fault): YES
60 * Affected by CVE-2018-12126 (Fallout, microarchitectural store buffer data sampling (MSBDS)): YES
61 * Affected by CVE-2018-12130 (ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)): YES
62 * Affected by CVE-2018-12127 (RIDL, microarchitectural load port data sampling (MLPDS)): YES
63 * Affected by CVE-2019-11091 (RIDL, microarchitectural data sampling uncacheable memory (MDSUM)): YES
64 * Affected by CVE-2019-11135 (ZombieLoad V2, TSX Asynchronous Abort (TAA)): YES
65 * Affected by CVE-2018-12207 (No eXcuses, iTLB Multihit, machine check exception on page size changes (MCEPSC)): YES
66 * Affected by CVE-2020-0543 (Special Register Buffer Data Sampling (SRBDS)): NO
68 CVE-2017-5753 aka Spectre Variant 1, bounds check bypass
69 * Mitigated according to the /sys interface: YES (Mitigation: usercopy/swapgs barriers and __user pointer sanitization)
70 * Kernel has array_index_mask_nospec: YES (1 occurrence(s) found of x86 64 bits array_index_mask_nospec())
71 * Kernel has the Red Hat/Ubuntu patch: NO
72 * Kernel has mask_nospec64 (arm64): NO
73 * Kernel has array_index_nospec (arm64): NO
74 > STATUS: NOT VULNERABLE (Mitigation: usercopy/swapgs barriers and __user pointer sanitization)
76 CVE-2017-5715 aka Spectre Variant 2, branch target injection
77 * Mitigated according to the /sys interface: YES (Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: conditional, RSB filling)
79 * Kernel is compiled with IBRS support: YES
80 * IBRS enabled and active: YES (for firmware code only)
81 * Kernel is compiled with IBPB support: YES
82 * IBPB enabled and active: YES
84 * Kernel has branch predictor hardening (arm): NO
85 * Kernel compiled with retpoline option: YES
86 * Kernel compiled with a retpoline-aware compiler: YES (kernel reports full retpoline compilation)
87 * Kernel supports RSB filling: YES
88 > STATUS: NOT VULNERABLE (Full retpoline + IBPB are mitigating the vulnerability)
90 CVE-2017-5754 aka Variant 3, Meltdown, rogue data cache load
91 * Mitigated according to the /sys interface: YES (Mitigation: PTI)
92 * Kernel supports Page Table Isolation (PTI): YES
93 * PTI enabled and active: YES
94 * Reduced performance impact of PTI: YES (CPU supports INVPCID, performance impact of PTI will be greatly reduced)
95 * Running as a Xen PV DomU: NO
96 > STATUS: NOT VULNERABLE (Mitigation: PTI)
98 CVE-2018-3640 aka Variant 3a, rogue system register read
99 * CPU microcode mitigates the vulnerability: YES
100 > STATUS: NOT VULNERABLE (your CPU microcode mitigates the vulnerability)
102 CVE-2018-3639 aka Variant 4, speculative store bypass
103 * Mitigated according to the /sys interface: YES (Mitigation: Speculative Store Bypass disabled via prctl and seccomp)
104 * Kernel supports disabling speculative store bypass (SSB): YES (found in /proc/self/status)
105 * SSB mitigation is enabled and active: YES (per-thread through prctl)
106 * SSB mitigation currently active for selected processes: YES (boltd fwupd irqbalance systemd-journald systemd-logind systemd-networkd systemd-resolved systemd-timesyncd systemd-udevd)
107 > STATUS: NOT VULNERABLE (Mitigation: Speculative Store Bypass disabled via prctl and seccomp)
109 CVE-2018-3615 aka Foreshadow (SGX), L1 terminal fault
110 * CPU microcode mitigates the vulnerability: N/A
111 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
113 CVE-2018-3620 aka Foreshadow-NG (OS), L1 terminal fault
114 * Mitigated according to the /sys interface: YES (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable)
115 * Kernel supports PTE inversion: YES (found in kernel image)
116 * PTE inversion enabled and active: YES
117 > STATUS: NOT VULNERABLE (Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable)
119 CVE-2018-3646 aka Foreshadow-NG (VMM), L1 terminal fault
120 * Information from the /sys interface: Mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
121 * This system is a host running a hypervisor: NO
123 * EPT is disabled: NO
125 * L1D flush is supported by kernel: YES (found flush_l1d in /proc/cpuinfo)
126 * L1D flush enabled: YES (conditional flushes)
127 * Hardware-backed L1D flush supported: YES (performance impact of the mitigation will be greatly reduced)
128 * Hyper-Threading (SMT) is enabled: YES
129 > STATUS: NOT VULNERABLE (this system is not running a hypervisor)
131 CVE-2018-12126 aka Fallout, microarchitectural store buffer data sampling (MSBDS)
132 * Mitigated according to the /sys interface: YES (Mitigation: Clear CPU buffers; SMT vulnerable)
133 * Kernel supports using MD_CLEAR mitigation: YES (md_clear found in /proc/cpuinfo)
134 * Kernel mitigation is enabled and active: YES
135 * SMT is either mitigated or disabled: NO
136 > STATUS: NOT VULNERABLE (Your microcode and kernel are both up to date for this mitigation, and mitigation is enabled)
138 CVE-2018-12130 aka ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)
139 * Mitigated according to the /sys interface: YES (Mitigation: Clear CPU buffers; SMT vulnerable)
140 * Kernel supports using MD_CLEAR mitigation: YES (md_clear found in /proc/cpuinfo)
141 * Kernel mitigation is enabled and active: YES
142 * SMT is either mitigated or disabled: NO
143 > STATUS: NOT VULNERABLE (Your microcode and kernel are both up to date for this mitigation, and mitigation is enabled)
145 CVE-2018-12127 aka RIDL, microarchitectural load port data sampling (MLPDS)
146 * Mitigated according to the /sys interface: YES (Mitigation: Clear CPU buffers; SMT vulnerable)
147 * Kernel supports using MD_CLEAR mitigation: YES (md_clear found in /proc/cpuinfo)
148 * Kernel mitigation is enabled and active: YES
149 * SMT is either mitigated or disabled: NO
150 > STATUS: NOT VULNERABLE (Your microcode and kernel are both up to date for this mitigation, and mitigation is enabled)
152 CVE-2019-11091 aka RIDL, microarchitectural data sampling uncacheable memory (MDSUM)
153 * Mitigated according to the /sys interface: YES (Mitigation: Clear CPU buffers; SMT vulnerable)
154 * Kernel supports using MD_CLEAR mitigation: YES (md_clear found in /proc/cpuinfo)
155 * Kernel mitigation is enabled and active: YES
156 * SMT is either mitigated or disabled: NO
157 > STATUS: NOT VULNERABLE (Your microcode and kernel are both up to date for this mitigation, and mitigation is enabled)
159 CVE-2019-11135 aka ZombieLoad V2, TSX Asynchronous Abort (TAA)
160 * Mitigated according to the /sys interface: YES (Mitigation: Clear CPU buffers; SMT vulnerable)
161 * TAA mitigation is supported by kernel: YES (found tsx_async_abort in kernel image)
162 * TAA mitigation enabled and active: YES (Mitigation: Clear CPU buffers; SMT vulnerable)
163 > STATUS: NOT VULNERABLE (Mitigation: Clear CPU buffers; SMT vulnerable)
165 CVE-2018-12207 aka No eXcuses, iTLB Multihit, machine check exception on page size changes (MCEPSC)
166 * Mitigated according to the /sys interface: YES (KVM: Mitigation: Split huge pages)
167 * This system is a host running a hypervisor: NO
168 * iTLB Multihit mitigation is supported by kernel: YES (found itlb_multihit in kernel image)
169 * iTLB Multihit mitigation enabled and active: YES (KVM: Mitigation: Split huge pages)
170 > STATUS: NOT VULNERABLE (this system is not running a hypervisor)
172 CVE-2020-0543 aka Special Register Buffer Data Sampling (SRBDS)
173 * Mitigated according to the /sys interface: YES (Not affected)
174 * SRBDS mitigation control is supported by the kernel: YES (found SRBDS implementation evidence in kernel image. Your kernel is up to date for SRBDS mitigation)
175 * SRBDS mitigation control is enabled and active: NO
176 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
178 > 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 CVE-2019-11135:OK CVE-2018-12207:OK CVE-2020-0543:OK
182 Spectre and Meltdown mitigation detection tool v0.44+
184 Checking for vulnerabilities on current system
185 Kernel is Linux 5.4.0-65-generic #73-Ubuntu SMP Mon Jan 18 17:25:17 UTC 2021 x86_64
186 CPU is Intel(R) Atom(TM) CPU C3858 @ 2.00GHz
189 * Hardware support (CPU microcode) for mitigation techniques
190 * Indirect Branch Restricted Speculation (IBRS)
191 * SPEC_CTRL MSR is available: YES
192 * CPU indicates IBRS capability: YES (SPEC_CTRL feature bit)
193 * Indirect Branch Prediction Barrier (IBPB)
194 * PRED_CMD MSR is available: YES
195 * CPU indicates IBPB capability: YES (SPEC_CTRL feature bit)
196 * Single Thread Indirect Branch Predictors (STIBP)
197 * SPEC_CTRL MSR is available: YES
198 * CPU indicates STIBP capability: YES (Intel STIBP feature bit)
199 * Speculative Store Bypass Disable (SSBD)
200 * CPU indicates SSBD capability: NO
201 * L1 data cache invalidation
202 * FLUSH_CMD MSR is available: NO
203 * CPU indicates L1D flush capability: NO
204 * Microarchitectural Data Sampling
205 * VERW instruction is available: NO
206 * Enhanced IBRS (IBRS_ALL)
207 * CPU indicates ARCH_CAPABILITIES MSR availability: YES
208 * ARCH_CAPABILITIES MSR advertises IBRS_ALL capability: NO
209 * CPU explicitly indicates not being vulnerable to Meltdown/L1TF (RDCL_NO): YES
210 * CPU explicitly indicates not being vulnerable to Variant 4 (SSB_NO): NO
211 * CPU/Hypervisor indicates L1D flushing is not necessary on this system: NO
212 * Hypervisor indicates host CPU might be vulnerable to RSB underflow (RSBA): NO
213 * CPU explicitly indicates not being vulnerable to Microarchitectural Data Sampling (MDS_NO): NO
214 * CPU explicitly indicates not being vulnerable to TSX Asynchronous Abort (TAA_NO): NO
215 * CPU explicitly indicates not being vulnerable to iTLB Multihit (PSCHANGE_MSC_NO): NO
216 * CPU explicitly indicates having MSR for TSX control (TSX_CTRL_MSR): NO
217 * CPU supports Transactional Synchronization Extensions (TSX): NO
218 * CPU supports Software Guard Extensions (SGX): NO
219 * CPU supports Special Register Buffer Data Sampling (SRBDS): NO
220 * CPU microcode is known to cause stability problems: NO (family 0x6 model 0x5f stepping 0x1 ucode 0x20 cpuid 0x506f1)
221 * CPU microcode is the latest known available version: NO (latest version is 0x34 dated 2020/10/23 according to builtin firmwares DB v191+i20210217)
222 * CPU vulnerability to the speculative execution attack variants
223 * Affected by CVE-2017-5753 (Spectre Variant 1, bounds check bypass): YES
224 * Affected by CVE-2017-5715 (Spectre Variant 2, branch target injection): YES
225 * Affected by CVE-2017-5754 (Variant 3, Meltdown, rogue data cache load): NO
226 * Affected by CVE-2018-3640 (Variant 3a, rogue system register read): YES
227 * Affected by CVE-2018-3639 (Variant 4, speculative store bypass): YES
228 * Affected by CVE-2018-3615 (Foreshadow (SGX), L1 terminal fault): NO
229 * Affected by CVE-2018-3620 (Foreshadow-NG (OS), L1 terminal fault): NO
230 * Affected by CVE-2018-3646 (Foreshadow-NG (VMM), L1 terminal fault): NO
231 * Affected by CVE-2018-12126 (Fallout, microarchitectural store buffer data sampling (MSBDS)): NO
232 * Affected by CVE-2018-12130 (ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)): NO
233 * Affected by CVE-2018-12127 (RIDL, microarchitectural load port data sampling (MLPDS)): NO
234 * Affected by CVE-2019-11091 (RIDL, microarchitectural data sampling uncacheable memory (MDSUM)): NO
235 * Affected by CVE-2019-11135 (ZombieLoad V2, TSX Asynchronous Abort (TAA)): NO
236 * Affected by CVE-2018-12207 (No eXcuses, iTLB Multihit, machine check exception on page size changes (MCEPSC)): NO
237 * Affected by CVE-2020-0543 (Special Register Buffer Data Sampling (SRBDS)): NO
239 CVE-2017-5753 aka Spectre Variant 1, bounds check bypass
240 * Mitigated according to the /sys interface: YES (Mitigation: usercopy/swapgs barriers and __user pointer sanitization)
241 * Kernel has array_index_mask_nospec: YES (1 occurrence(s) found of x86 64 bits array_index_mask_nospec())
242 * Kernel has the Red Hat/Ubuntu patch: NO
243 * Kernel has mask_nospec64 (arm64): NO
244 * Kernel has array_index_nospec (arm64): NO
245 > STATUS: NOT VULNERABLE (Mitigation: usercopy/swapgs barriers and __user pointer sanitization)
247 CVE-2017-5715 aka Spectre Variant 2, branch target injection
248 * Mitigated according to the /sys interface: YES (Mitigation: Full generic retpoline, IBPB: conditional, IBRS_FW, STIBP: disabled, RSB filling)
250 * Kernel is compiled with IBRS support: YES
251 * IBRS enabled and active: YES (for firmware code only)
252 * Kernel is compiled with IBPB support: YES
253 * IBPB enabled and active: YES
255 * Kernel has branch predictor hardening (arm): NO
256 * Kernel compiled with retpoline option: YES
257 * Kernel compiled with a retpoline-aware compiler: YES (kernel reports full retpoline compilation)
258 > STATUS: NOT VULNERABLE (Full retpoline + IBPB are mitigating the vulnerability)
260 CVE-2017-5754 aka Variant 3, Meltdown, rogue data cache load
261 * Mitigated according to the /sys interface: YES (Not affected)
262 * Kernel supports Page Table Isolation (PTI): YES
263 * PTI enabled and active: NO
264 * Reduced performance impact of PTI: NO (PCID/INVPCID not supported, performance impact of PTI will be significant)
265 * Running as a Xen PV DomU: NO
266 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
268 CVE-2018-3640 aka Variant 3a, rogue system register read
269 * CPU microcode mitigates the vulnerability: NO
270 > STATUS: VULNERABLE (an up-to-date CPU microcode is needed to mitigate this vulnerability)
272 CVE-2018-3639 aka Variant 4, speculative store bypass
273 * Mitigated according to the /sys interface: NO (Vulnerable)
274 * Kernel supports disabling speculative store bypass (SSB): YES (found in /proc/self/status)
275 * SSB mitigation is enabled and active: NO
276 > STATUS: VULNERABLE (Your CPU doesnt support SSBD)
278 CVE-2018-3615 aka Foreshadow (SGX), L1 terminal fault
279 * CPU microcode mitigates the vulnerability: N/A
280 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
282 CVE-2018-3620 aka Foreshadow-NG (OS), L1 terminal fault
283 * Mitigated according to the /sys interface: YES (Not affected)
284 * Kernel supports PTE inversion: YES (found in kernel image)
285 * PTE inversion enabled and active: NO
286 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
288 CVE-2018-3646 aka Foreshadow-NG (VMM), L1 terminal fault
289 * Information from the /sys interface: Not affected
290 * This system is a host running a hypervisor: NO
292 * EPT is disabled: NO
294 * L1D flush is supported by kernel: YES (found flush_l1d in kernel image)
295 * L1D flush enabled: NO
296 * Hardware-backed L1D flush supported: NO (flush will be done in software, this is slower)
297 * Hyper-Threading (SMT) is enabled: NO
298 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
300 CVE-2018-12126 aka Fallout, microarchitectural store buffer data sampling (MSBDS)
301 * Mitigated according to the /sys interface: YES (Not affected)
302 * Kernel supports using MD_CLEAR mitigation: YES (found md_clear implementation evidence in kernel image)
303 * Kernel mitigation is enabled and active: NO
304 * SMT is either mitigated or disabled: NO
305 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
307 CVE-2018-12130 aka ZombieLoad, microarchitectural fill buffer data sampling (MFBDS)
308 * Mitigated according to the /sys interface: YES (Not affected)
309 * Kernel supports using MD_CLEAR mitigation: YES (found md_clear implementation evidence in kernel image)
310 * Kernel mitigation is enabled and active: NO
311 * SMT is either mitigated or disabled: NO
312 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
314 CVE-2018-12127 aka RIDL, microarchitectural load port data sampling (MLPDS)
315 * Mitigated according to the /sys interface: YES (Not affected)
316 * Kernel supports using MD_CLEAR mitigation: YES (found md_clear implementation evidence in kernel image)
317 * Kernel mitigation is enabled and active: NO
318 * SMT is either mitigated or disabled: NO
319 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
321 CVE-2019-11091 aka RIDL, microarchitectural data sampling uncacheable memory (MDSUM)
322 * Mitigated according to the /sys interface: YES (Not affected)
323 * Kernel supports using MD_CLEAR mitigation: YES (found md_clear implementation evidence in kernel image)
324 * Kernel mitigation is enabled and active: NO
325 * SMT is either mitigated or disabled: NO
326 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
328 CVE-2019-11135 aka ZombieLoad V2, TSX Asynchronous Abort (TAA)
329 * Mitigated according to the /sys interface: YES (Not affected)
330 * TAA mitigation is supported by kernel: YES (found tsx_async_abort in kernel image)
331 * TAA mitigation enabled and active: NO
332 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
334 CVE-2018-12207 aka No eXcuses, iTLB Multihit, machine check exception on page size changes (MCEPSC)
335 * Mitigated according to the /sys interface: YES (Not affected)
336 * This system is a host running a hypervisor: NO
337 * iTLB Multihit mitigation is supported by kernel: YES (found itlb_multihit in kernel image)
338 * iTLB Multihit mitigation enabled and active: NO
339 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
341 CVE-2020-0543 aka Special Register Buffer Data Sampling (SRBDS)
342 * Mitigated according to the /sys interface: YES (Not affected)
343 * SRBDS mitigation control is supported by the kernel: YES (found SRBDS implementation evidence in kernel image. Your kernel is up to date for SRBDS mitigation)
344 * SRBDS mitigation control is enabled and active: NO
345 > STATUS: NOT VULNERABLE (your CPU vendor reported your CPU model as not vulnerable)
347 > 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:OK CVE-2018-12130:OK CVE-2018-12127:OK CVE-2019-11091:OK CVE-2019-11135:OK CVE-2018-12207:OK CVE-2020-0543:OK