spectre-meltdown-checker/FAQ.md

Questions

• What to expect from this tool?
• Why was this script written in the first place?
• Why are those vulnerabilities so different than regular CVEs?
• What do “affected”, “vulnerable” and “mitigated” mean exactly?
• What are the main design decisions regarding this script?
• Everything is indicated in sysfs now, is this script still useful?
• How does this script work?
• Which BSD OSes are supported?
• Why is my OS not supported?
• The tool says there is an updated microcode for my CPU, but I don’t have it!
• The tool says that I need a more up-to-date microcode, but I have the more recent version!
• Which rules are governing the support of a CVE in this tool?

Answers

What to expect from this tool?

This tool does its best to determine where your system stands on each of the collectively named transient execution vulnerabilities (also sometimes called “speculative execution” vulnerabilities) that were made public since early 2018. It doesn’t attempt to run any kind of exploit, and can’t guarantee that your system is secure, but rather helps you verifying if your system is affected, and if it is, checks whether it has the known mitigations in place to avoid being vulnerable. 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).

Please also note that for Spectre vulnerabilities, all software can possibly be exploited, this tool only verifies that the kernel (which is the core of the system) you’re using has the proper protections in place. Verifying all the other software is out of the scope of this tool. As a general measure, ensure you always have the most up to date stable versions of all the software you use, especially for those who are exposed to the world, such as network daemons and browsers.

This tool has been released in the hope that it’ll be useful, but don’t use it to jump to definitive conclusions about your security: hardware vulnerabilities are complex beasts, and collective understanding of each vulnerability is evolving with time.

Why was this script written in the first place?

The first commit of this script is dated 2018-01-07, only 4 days after the world first heard about the Meltdown and the Spectre attacks. With those attacks disclosure, a whole new range of vulnerabilities that were previously thought to be mostly theoretical and only possible in very controlled environments (labs) - hence of little interest for most except researchers - suddenly became completely mainstream and apparently trivial to conduct on an immensely large number of systems.

On the few hours and days after that date, the whole industry went crazy. Proper, verified information about these vulnerabilities was incredibly hard to find, because before this, even the CPU vendors never had to deal with managing security vulnerabilities at scale, as software vendors do since decades. There were a lot of FUD, and the apparent silence of the vendors was enough for most to fear the worst. The whole industry had everything to learn about this new type of vulnerabilities. However, most systems administrators had a few simple questions:

• Am I vulnerable? And if yes,
• What do I have to do to mitigate these vulnerabilities on my system?

Unfortunately, answering those questions was very difficult (and still is to some extent), even if the safe answer to the first question was “you probably are”. This script was written to try to give simple answers to those simple questions, and was made to evolve as the information about these vulnerabilities became available. On the first few days, there was several new versions published per day.

Why are those vulnerabilities so different than regular CVEs?

Those are hardware vulnerabilities, while most of the CVEs we see everyday are software vulnerabilities. A quick comparison would be:

Software vulnerability: - Can be fixed? Yes. - How to fix? Update the software (or uninstall it!)

Hardware vulnerability: - Can be fixed? No, only mitigated (or buy new hardware!) - How to fix mitigate? In the worst case scenario, 5 “layers” need to be updated: the microcode/firmware, the host OS kernel, the hypervisor, the VM OS kernel, and possibly all the software running on the VM.

A more detailed video explanation is available here: https://youtu.be/2gB9U1EcCss?t=85

What do “affected”, “vulnerable” and “mitigated” mean exactly?

• Affected means that your CPU’s hardware, as it went out of the factory, is known to be concerned by a specific vulnerability, i.e. the vulnerability applies to your hardware model. Note that it says nothing about whether a given vulnerability can actually be used to exploit your system. However, an unaffected CPU will never be vulnerable, and doesn’t need to have mitigations in place.
• Vulnerable implies that you’re using an affected CPU, and means that a given vulnerability can be exploited on your system, because no (or insufficient) mitigations are in place.
• Mitigated implies that a previously vulnerable system has followed all the steps (updated all the required layers) to ensure a given vulnerability cannot be exploited. About what “layers” mean, see the previous question.

What are the main design decisions regarding this script?

There are a few rules that govern how this tool is written.

1. It should be okay to run this script in a production environment. This implies, but is not limited to:

   • 1a. Never modify the system it’s running on, and if it needs to e.g. load a kernel module it requires, that wasn’t loaded before it was launched, it’ll take care to unload it on exit
   • 1b. Never attempt to “fix” or “mitigate” any vulnerability, or modify any configuration. It just reports what it thinks is the status of your system. It leaves all decisions to the sysadmin.
   • 1c. Never attempt to run any kind of exploit to tell whether a vulnerability is mitigated, because it would violate 1a), could lead to unpredictable system behavior, and might even lead to wrong conclusions, as some PoC must be compiled with specific options and prerequisites, otherwise giving wrong information (especially for Spectre). If you want to run PoCs, do it yourself, but please read carefully about the PoC and the vulnerability. PoCs about a hardware vulnerability are way more complicated and prone to false conclusions than PoCs for software vulnerabilities.

2. Never look at the kernel version to tell whether it supports mitigation for a given vulnerability. This implies never hardcoding version numbers in the script. This would defeat the purpose: this script should be able to detect mitigations in unknown kernels, with possibly backported or forward-ported patches. Also, don’t believe what sysfs says, when possible. See the next question about this.

3. Never look at the microcode version to tell whether it has the proper mechanisms in place to support mitigation for a given vulnerability. This implies never hardcoding version numbers in the script. Instead, look for said mechanisms, as the kernel would do.

4. When a CPU is not known to be explicitly unaffected by a vulnerability, make the assumption that it is. This strong design choice has it roots in the early speculative execution vulnerability days (see this answer), and is still a good approach as of today.

Everything is indicated in sysfs now, is this script still useful?

A lot as changed since 2018. Nowadays, the industry adapted and this range of vulnerabilities is almost “business as usual”, as software vulnerabilities are. However, due to their complexity, it’s still not as easy as just checking a version number to ensure a vulnerability is closed.

Granted, we now have a standard way under Linux to check whether our system is affected, vulnerable, mitigated against most of these vulnerabilities. By having a look at the sysfs hierarchy, and more precisely the /sys/devices/system/cpu/vulnerabilities/ folder, one can have a pretty good insight about its system state for each of the listed vulnerabilities. Note that the output can be a little different with some vendors (e.g. Red Hat has some slightly different output than the vanilla kernel for some vulnerabilities), but it’s still a gigantic leap forward, given where we were in 2018 when this script was started, and it’s very good news. The kernel is the proper place to have this because the kernel knows everything about itself (the mitigations it might have), and the CPU (its model, and microcode features that are exposed).

However I see a few reasons why this script might still be useful to you, and that’s why its development has not halted when the sysfs hierarchy came out:

• A given version of the kernel doesn’t have knowledge about the future. To put it in another way: a given version of the kernel only has the understanding of a vulnerability available at the time it was compiled. Let me explain this: when a new vulnerability comes out, new versions of the microcode and kernels are released, with mitigations in place. With such a kernel, a new sysfs entry will appear. However, after a few weeks or months, corner cases can be discovered, previously-thought unaffected CPUs can turn out to be affected in the end, and sometimes mitigations can end up being insufficient. Of course, if you’re always running the latest kernel version from kernel.org, this issue might be limited for you. The spectre-meltdown-checker script doesn’t depend on a kernel’s knowledge and understanding of a vulnerability to compute its output. That is, unless you tell it to (using the --sysfs-only option).

• Mitigating a vulnerability completely can sometimes be tricky, and have a lot of complicated prerequisites, depending on your kernel version, CPU vendor, model and even sometimes stepping, CPU microcode, hypervisor support, etc. The script gives a very detailed insight about each of the prerequisites of mitigation for every vulnerability, step by step, hence pointing out what is missing on your system as a whole to completely mitigate an issue.

• The script can be pointed at a kernel image, and will deep dive into it, telling you if this kernel will mitigate vulnerabilities that might be present on your system. This is a good way to verify before booting a new kernel, that it’ll mitigate the vulnerabilities you expect it to, especially if you modified a few config options around these topics.

• The script will also work regardless of the custom patches that might be integrated in the kernel you’re running (or you’re pointing it to, in offline mode), and completely ignores the advertised kernel version, to tell whether a given kernel mitigates vulnerabilities. This is especially useful for non-vanilla kernel, where patches might be backported, sometimes silently (this has already happened, too).

• Educational purposes: the script gives interesting insights about a vulnerability, and how the different parts of the system work together to mitigate it.

There are probably other reasons, but that are the main ones that come to mind. In the end, of course, only you can tell whether it’s useful for your use case ;)

How does this script work?

On one hand, the script gathers information about your CPU, and the features exposed by its microcode. To do this, it uses the low-level CPUID instruction (through the cpuid kernel module under Linux, and the cpucontrol tool under BSD), and queries to the MSR registers of your CPU (through the msr kernel module under Linux, and the cpucontrol tool under BSD).

On another hand, the script looks into the kernel image your system is running on, for clues about the mitigations it supports. Of course, this is very specific for each operating system, even if the implemented mitigation is functionally the same, the actual code is completely specific. As you can imagine, the Linux kernel code has a few in common with a BSD kernel code, for example. Under Linux, the script supports looking into the kernel image, and possibly the System.map and kernel config file, if these are available. Under BSD, it looks into the kernel file only.

Then, for each vulnerability it knows about, the script decides whether your system is affected, vulnerable, and mitigated against it, using the information it gathered about your hardware and your kernel.

Which BSD OSes are supported?

For the BSD range of operating systems, the script will work as long as the BSD you’re using supports cpuctl and linprocfs. This is not the case for OpenBSD for example. Known BSD flavors having proper support are: FreeBSD, NetBSD, DragonflyBSD. Derivatives of those should also work. To know why other BSDs will likely never be supported, see why is my OS not supported?.

Why is my OS not supported?

This tool only supports Linux, and some flavors of BSD. Other OSes will most likely never be supported, due to how this script works. It would require implementing these OSes specific way of querying the CPU. It would also require to get documentation (if available) about how this OS mitigates each vulnerability, down to this OS kernel code, and if documentation is not available, reverse-engineer the difference between a known old version of a kernel, and a kernel that mitigates a new vulnerability. This means that all the effort has to be duplicated times the number of supported OSes, as everything is specific, by construction. It also implies having a deep understanding of every OS, which takes years to develop. However, if/when other tools appear for other OSes, that share the same goal of this one, they might be listed here as a convenience.

The tool says there is an updated microcode for my CPU, but I don’t have it!

Even if your operating system is fully up to date, the tool might still tell you that there is a more recent microcode version for your CPU. Currently, it uses (and merges) information from two sources:

• The official Intel microcode repository
• The awesome platomav’s MCExtractor database for non-Intel CPUs

Generally, for Intel CPUs it means that Intel does have a more recent version for your CPU, and for other CPUs it means that a more recent version has already been seen in the wild. However, your OS vendor might have chosen not to ship this new version (yet), maybe because it’s currently being tested, or for other reasons. This tool can’t tell you when or if this will be the case. You should ask your vendor about it. Technically, you can still go and upgrade your microcode yourself, and use this tool to confirm whether you did it successfully. Updating the microcode for you is out of the scope of this tool, as this would violate rule 1b.

The tool says that I need a more up-to-date microcode, but I have the more recent version!

This can happen for a few reasons:

• Your CPU is no longer supported by the vendor. In that case, new versions of the microcode will never be published, and vulnerabilities requiring microcode features will never be fixed. On most of these vulnerabilities, you’ll have no way to mitigate the issue on a vulnerable system, appart from buying a more recent CPU. Sometimes, you might be able to mitigate the issue by disabling a CPU feature instead (often at the cost of speed). When this is the case, the script will list this as one of the possible mitigations for the vulnerability.

• The vulnerability is recent, and your CPU has not yet received a microcode update for the vendor. Often, these updates come in batches, and it can take several batches to cover all the supported CPUs.

In both cases, you can contact your vendor to know whether there’ll be an update or not, and if yes, when. For Intel, at the time this FAQ entry was written, such guidance was available here.

Which rules are governing the support of a CVE in this tool?

On the early days, it was easy: just Spectre and Meltdown (hence the tool name), because that’s all we had. Now that this range of vulnerability is seeing a bunch of newcomers every year, this question is legitimate.

To stick with this tool’s goal, a good indication as to why a CVE should be supported, is when mitigating it requires either kernel modifications, microcode modifications, or both.

Counter-examples include (non-exhaustive list):

• CVE-2019-14615, mitigating this issue is done by updating the Intel driver. This is out of the scope of this tool.
• CVE-2019-15902, this CVE is due to a bad backport in the stable kernel. If the faulty backport was part of the mitigation of another supported CVE, and this bad backport was detectable (without hardcoding kernel versions, see rule 2), it might have been added as a bullet point in the concerned CVE’s section in the tool. However, this wasn’t the case.
• The “Take A Way” vulnerability, AMD said that they believe this is not a new attack, hence there were no microcode and no kernel modification made. As there is nothing to look for, this is out of the scope of this tool.
• CVE-2020-0550, the vendor thinks this is hardly exploitable in the wild, and as mitigations would be too performance impacting, as a whole the industry decided to not address it. As there is nothing to check for, this is out of the scope of this tool.
• CVE-2020-0551, the industry decided to not address it, as it is believed mitigations for other CVEs render this attack practically hard to make, Intel just released an updated SDK for SGX to help mitigate the issue, but this is out of the scope of this tool.

Look for the information tag in the issues list for more examples.