mirror of
https://github.com/speed47/spectre-meltdown-checker.git
synced 2025-07-15 07:11:22 +02:00
Compare commits
69 Commits
Author | SHA1 | Date | |
---|---|---|---|
bd18323d79 | |||
b89d67dd15 | |||
704e54019a | |||
d96093171a | |||
dcc4488340 | |||
32e3fe6c07 | |||
f488947d43 | |||
71213c11b3 | |||
2964c4ab44 | |||
749f432d32 | |||
a422b53d7c | |||
c483a2cf60 | |||
dead0054a4 | |||
8ed7d465aa | |||
e5e4851d72 | |||
7f92717a2c | |||
b47d505689 | |||
4a2d051285 | |||
f3551b9734 | |||
45b98e125f | |||
dce917bfbb | |||
8f18f53aba | |||
d3f102b3b3 | |||
8bd093173d | |||
bfe5a3b840 | |||
6a0242eea3 | |||
bc4e39038a | |||
62f8ed6f61 | |||
56b67f8082 | |||
52a8f78885 | |||
a09a5ba38f | |||
5a7d8d7edf | |||
49fdc6c449 | |||
af3de2a862 | |||
c6e1b0ac8a | |||
b913dacc1b | |||
eb0ebef5a8 | |||
e0254025e8 | |||
bd010340e6 | |||
a658de2f01 | |||
4aed5589fe | |||
8ed1f5e3af | |||
ffc542eb82 | |||
74bc7ba637 | |||
5389ac6844 | |||
36fb83215a | |||
59fe8c2ad8 | |||
b8d28e7f61 | |||
7c11d07865 | |||
7c5cfbb8c3 | |||
381038eceb | |||
d6e4aa43f0 | |||
e5e09384f0 | |||
7222367f04 | |||
ab512687cf | |||
a5aaa790a0 | |||
335439dee0 | |||
45297b6f7d | |||
a7b14306d5 | |||
608952ff71 | |||
1c3d349667 | |||
b93b13263d | |||
ad342cab06 | |||
5fd85e288b | |||
322f4efc8f | |||
b6bfcdbd45 | |||
19b01078c2 | |||
68961f98c2 | |||
f0f2ea9b11 |
75
README.md
75
README.md
@ -1,13 +1,17 @@
|
|||||||
Spectre & Meltdown Checker
|
Spectre & Meltdown Checker
|
||||||
==========================
|
==========================
|
||||||
|
|
||||||
A simple shell script to tell if your Linux installation is vulnerable against the 3 "speculative execution" CVEs.
|
A simple shell script to tell if your Linux installation is vulnerable against the 3 "speculative execution" CVEs that were made public early 2018.
|
||||||
|
|
||||||
Without options, it'll inspect you currently running kernel.
|
Without options, it'll inspect your currently running kernel.
|
||||||
You can also specify a kernel image on the command line, if you'd like to inspect a kernel you're not running.
|
You can also specify a kernel image on the command line, if you'd like to inspect a kernel you're not running.
|
||||||
|
|
||||||
The script will do its best to detect mitigations, including backported non-vanilla patches, regardless of the advertised kernel version number.
|
The script will do its best to detect mitigations, including backported non-vanilla patches, regardless of the advertised kernel version number.
|
||||||
|
|
||||||
|
## Example of script output
|
||||||
|
|
||||||
|

|
||||||
|
|
||||||
## Quick summary of the CVEs
|
## Quick summary of the CVEs
|
||||||
|
|
||||||
**CVE-2017-5753** bounds check bypass (Spectre Variant 1)
|
**CVE-2017-5753** bounds check bypass (Spectre Variant 1)
|
||||||
@ -29,68 +33,13 @@ The script will do its best to detect mitigations, including backported non-vani
|
|||||||
- Mitigation: updated kernel (with PTI/KPTI patches), updating the kernel is enough
|
- Mitigation: updated kernel (with PTI/KPTI patches), updating the kernel is enough
|
||||||
- Performance impact of the mitigation: low to medium
|
- Performance impact of the mitigation: low to medium
|
||||||
|
|
||||||
## Example of script output
|
## Disclaimer
|
||||||
|
|
||||||
### Ubuntu LTS (before official patches)
|
This tool does its best to determine whether your system is immune (or has proper mitigations in place) for the collectively named "speculative execution" vulnerabilities. It doesn't attempt to run any kind of exploit, and can't guarantee that your system is secure, but rather helps you verifying whether your system has the known correct mitigations in place.
|
||||||
|
However, some mitigations could also exist in your kernel that this script doesn't know (yet) how to detect, or it might falsely detect mitigations that in the end don't work as expected (for example, on backported or modified kernels).
|
||||||
|
|
||||||
```
|
Your system exposure also depends on your CPU. As of now, AMD and ARM processors are marked as immune to some or all of these vulnerabilities (except some specific ARM models). All Intel processors manufactured since circa 1995 are thought to be vulnerable. Whatever processor one uses, one might seek more information from the manufacturer of that processor and/or of the device in which it runs.
|
||||||
$ sudo ./spectre-and-meltdown.sh
|
|
||||||
Spectre and Meltdown mitigation detection tool v0.16
|
|
||||||
|
|
||||||
Checking for vulnerabilities against live running kernel Linux 4.4.0-104-generic #127-Ubuntu SMP Mon Dec 11 12:16:42 UTC 2017 x86_64
|
The nature of the discovered vulnerabilities being quite new, the landscape of vulnerable processors can be expected to change over time, which is why this script makes the assumption that all CPUs are vulnerable, except if the manufacturer explicitly stated otherwise in a verifiable public announcement.
|
||||||
Will use vmlinux image /boot/vmlinuz-4.4.0-104-generic
|
|
||||||
Will use kconfig /boot/config-4.4.0-104-generic
|
|
||||||
Will use System.map file /boot/System.map-4.4.0-104-generic
|
|
||||||
|
|
||||||
CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
|
This tool has been released in the hope that it'll be useful, but don't use it to jump to conclusions about your security.
|
||||||
* Kernel compiled with LFENCE opcode inserted at the proper places: NO (only 38 opcodes found, should be >= 70)
|
|
||||||
> STATUS: VULNERABLE
|
|
||||||
|
|
||||||
CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
|
|
||||||
* Mitigation 1
|
|
||||||
* Hardware (CPU microcode) support for mitigation: NO
|
|
||||||
* Kernel support for IBRS: NO
|
|
||||||
* IBRS enabled for Kernel space: NO
|
|
||||||
* IBRS enabled for User space: NO
|
|
||||||
* Mitigation 2
|
|
||||||
* Kernel compiled with retpoline option: NO
|
|
||||||
* Kernel compiled with a retpoline-aware compiler: NO
|
|
||||||
> STATUS: VULNERABLE (IBRS hardware + kernel support OR kernel with retpoline are needed to mitigate the vulnerability)
|
|
||||||
|
|
||||||
CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
|
|
||||||
* Kernel supports Page Table Isolation (PTI): NO
|
|
||||||
* PTI enabled and active: NO
|
|
||||||
> STATUS: VULNERABLE (PTI is needed to mitigate the vulnerability)
|
|
||||||
```
|
|
||||||
|
|
||||||
### First patched kernel of RHEL6
|
|
||||||
|
|
||||||
```
|
|
||||||
$ sudo ./spectre-meltdown-checker.sh --kernel /tmp/vmlinuz-2.6.32-696.18.7.el6.x86_64 --config /tmp/config-2.6.32-696.18.7.el6.x86_64 --map /tmp/System.map-2.6.32-696.18.7.el6.x86_64
|
|
||||||
Spectre and Meltdown mitigation detection tool v0.16
|
|
||||||
|
|
||||||
Checking for vulnerabilities against specified kernel
|
|
||||||
Will use vmlinux image /tmp/vmlinuz-2.6.32-696.18.7.el6.x86_64
|
|
||||||
Will use kconfig /tmp/config-2.6.32-696.18.7.el6.x86_64
|
|
||||||
Will use System.map file /tmp/System.map-2.6.32-696.18.7.el6.x86_64
|
|
||||||
|
|
||||||
CVE-2017-5753 [bounds check bypass] aka 'Spectre Variant 1'
|
|
||||||
* Kernel compiled with LFENCE opcode inserted at the proper places: YES (84 opcodes found, which is >= 70)
|
|
||||||
> STATUS: NOT VULNERABLE
|
|
||||||
|
|
||||||
CVE-2017-5715 [branch target injection] aka 'Spectre Variant 2'
|
|
||||||
* Mitigation 1
|
|
||||||
* Hardware (CPU microcode) support for mitigation: NO
|
|
||||||
* Kernel support for IBRS: YES
|
|
||||||
* IBRS enabled for Kernel space: N/A (not testable in offline mode)
|
|
||||||
* IBRS enabled for User space: N/A (not testable in offline mode)
|
|
||||||
* Mitigation 2
|
|
||||||
* Kernel compiled with retpoline option: NO
|
|
||||||
* Kernel compiled with a retpoline-aware compiler: NO
|
|
||||||
> STATUS: NOT VULNERABLE (offline mode: IBRS will mitigate the vulnerability if enabled at runtime)
|
|
||||||
|
|
||||||
CVE-2017-5754 [rogue data cache load] aka 'Meltdown' aka 'Variant 3'
|
|
||||||
* Kernel supports Page Table Isolation (PTI): YES
|
|
||||||
* PTI enabled and active: N/A (can't verify if PTI is enabled in offline mode)
|
|
||||||
> STATUS: NOT VULNERABLE (offline mode: PTI will mitigate the vulnerability if enabled at runtime)
|
|
||||||
```
|
|
||||||
|
File diff suppressed because it is too large
Load Diff
Reference in New Issue
Block a user