Difference between revisions of "SVG:Meltdown and Spectre Vulnerabilities"
(→Intel) |
|||
Line 28: | Line 28: | ||
As of Feb 2nd 2018, RedHat has [https://access.redhat.com/security/vulnerabilities/speculativeexecution offered new kernel updates that can mitigate Meltdown (CVE-2017-5754), Spectre Variant 1 (CVE-2017-5753) and Spectre Variant 2 (CVE-2017-5715)]. | As of Feb 2nd 2018, RedHat has [https://access.redhat.com/security/vulnerabilities/speculativeexecution offered new kernel updates that can mitigate Meltdown (CVE-2017-5754), Spectre Variant 1 (CVE-2017-5753) and Spectre Variant 2 (CVE-2017-5715)]. | ||
However, due to instability issues, it has [https://access.redhat.com/errata/RHSA-2018:0093 removed the microcode updates required for Spectre Variant 2 (CVE-2017-5715)] | However, due to instability issues, it has [https://access.redhat.com/errata/RHSA-2018:0093 removed the microcode updates required for Spectre Variant 2 (CVE-2017-5715)]. Until Intel releases stable microcode or RedHat switches to 'retpoline', no mitigation for Spectre Variant 2 (CVE-2017-5715) is safely usable. | ||
It is currently possible to mitigate Meltdown (CVE-2017-5754) and Spectre Variant 1 (CVE-2017-5753) by: | It is currently possible to mitigate Meltdown (CVE-2017-5754) and Spectre Variant 1 (CVE-2017-5753) by: | ||
Line 34: | Line 34: | ||
* On RHEL6: Updating the kernel to 2.6.32-696.18.7.el6, see [https://access.redhat.com/errata/RHSA-2018:0008 RHSA-2018:0008] | * On RHEL6: Updating the kernel to 2.6.32-696.18.7.el6, see [https://access.redhat.com/errata/RHSA-2018:0008 RHSA-2018:0008] | ||
=== Centos === | |||
Centos is following RedHat (see above). | |||
It is currently possible to mitigate Meltdown (CVE-2017-5754) and Spectre Variant 1 (CVE-2017-5753) by: | |||
* On Centos 7: Updating the kernel to 3.10.0-693.11.6.el7, see [https://lists.centos.org/pipermail/centos-announce/2018-January/022696.html CESA-2018:0007] | |||
* On Centos 6: Updating the kernel to 2.6.32-696.18.7.el6, see [https://lists.centos.org/pipermail/centos-announce/2018-January/022701.html CESA-2018:0008] | |||
== More Information == | == More Information == |
Revision as of 10:17, 2 February 2018
Main page | Software Security Checklist | Issue Handling | Advisories | Notes On Risk | Advisory Template | More |
Meltdown and Spectre Vulnerabilities
Purpose of this page
To provide more detailed information about the Meltdown and Spectre vulnerabilities, to complement the advisory, SVG:Advisory-SVG-CVE-2017-5753.
We are continuing to add new information when we become aware of it, and the situation continues to change (02nd February 2018).
What are they?
These are vulnerabilities in the design of the chip hardware, and cannot be fully resolved by patching operating systems. However patches are available which mitigate these problems.
- Meltdown (CVE-2017-5754) affects most Intel chips.
- Spectre (CVE-2017-5753 and CVE-2017-5715) affects a wide range of chips.
For more details, see https://meltdownattack.com/ , https://spectreattack.com/ and https://googleprojectzero.blogspot.dk/2018/01/reading-privileged-memory-with-side.html
How to mitigate these vulnerabilities
Each CVE can be mitigated via different ways:
- Meltdown (CVE-2017-5754) can be mitigated via Kernel Page Table Isolation, which is enabled by default in latest linux kernels
- Spectre Variant 1 (CVE-2017-5753) has to be mitigated in each software which can be vulnerable. The latest linux kernel contains fixes to protect itself (does not protect other software).
- Spectre Variant 2 (CVE-2017-5715) can be (at least partially) mitigated via at least two different approach:
- Using new Intel-specific MSR, added via a microcode update, to control indirect branch restricted speculation (IBRS): Both a kernel and a microcode update are required. In addition, in case of virtualization, an update of the virtualization software (e.g. qemu & virt) is required to expose the new MSR to the VM.
- Using "retpoline", a new software construct that can mitigate, on most CPUs, the vulnerability
RedHat
As of Feb 2nd 2018, RedHat has offered new kernel updates that can mitigate Meltdown (CVE-2017-5754), Spectre Variant 1 (CVE-2017-5753) and Spectre Variant 2 (CVE-2017-5715).
However, due to instability issues, it has removed the microcode updates required for Spectre Variant 2 (CVE-2017-5715). Until Intel releases stable microcode or RedHat switches to 'retpoline', no mitigation for Spectre Variant 2 (CVE-2017-5715) is safely usable.
It is currently possible to mitigate Meltdown (CVE-2017-5754) and Spectre Variant 1 (CVE-2017-5753) by:
- On RHEL7: Updating the kernel to 3.10.0-693.11.6.el7, see RHSA-2018:0007
- On RHEL6: Updating the kernel to 2.6.32-696.18.7.el6, see RHSA-2018:0008
Centos
Centos is following RedHat (see above).
It is currently possible to mitigate Meltdown (CVE-2017-5754) and Spectre Variant 1 (CVE-2017-5753) by:
- On Centos 7: Updating the kernel to 3.10.0-693.11.6.el7, see CESA-2018:0007
- On Centos 6: Updating the kernel to 2.6.32-696.18.7.el6, see CESA-2018:0008
More Information
CERN
CERN has compiled information which is useful for many EGI sites:
https://security.web.cern.ch/security/advisories/spectre-meltdown/spectre-meltdown.shtml
Intel
Intel has initially, on January 8th, released new microcodes to complement the IBRS kernel patchset. However, these new microcodes are in fact unstable and Intel has since then recommended to stop deploying them.
Intel latest recommendation can be found in their advisory, INTEL-SA-00088
More updates and information:
- Jan 3rd: Initial response
- Jan 4th
- Jan 9th: Microcode released
- Jan 10th: performance impact analysis
- Jan 11th: Microcode unstability reported
- Jan 17th
- Jan 22th: Instabilities causes found for 2 Intel series
RedHat
Important! [as of 17th January]
RedHat has issued new microcode_ctl packages to rollback the latest updates, see RHSA-2018:0093.
RedHat description:
- https://access.redhat.com/security/vulnerabilities/speculativeexecution
- https://access.redhat.com/articles/3307751 (subscription required)
- https://access.redhat.com/solutions/3315431 (subscription required)
RedHat CVE info:
CentOS
Important! [as of 17th January]
Centos seems to be following Redhat in the revert of the microcode_ctl package, see the disclaimer in the sources of the last package:
This update supersedes microcode provided by Red Hat with the CVE-2017-5715 (“Spectre”) CPU branch injection vulnerability mitigation. (HIstorically, Red Hat has provided updated microcode, developed by our microprocessor partners, as a customer convenience.) Further testing has uncovered problems with the microcode provided along with the “Spectre” mitigation that could lead to system instabilities. As a result, Red Hat is providing an microcode update that reverts to the last known good microcode version dated before 03 January 2018. Red Hat strongly recommends that customers contact their hardware provider for the latest microcode updates. IMPORTANT: Customers using Intel Skylake-, Broadwell-, and Haswell-based platforms must obtain and install updated microcode from their hardware vendor immediately. The "Spectre" mitigation requires both an updated kernel from Red Hat and updated microcode from your hardware vendor.
CentOS 7:
- kernel Security Update: CESA-2018:0007
- microcode_ctl Security Update: CESA-2018:0012
also needs dracut BugFix Update for AMD: CEBA-2018:0042 - linux-firmware Security Update: CESA-2018:0014
- qemu-kvm Security Update: CESA-2018:0023
- libvirt Security Update: CESA-2018:0029
CentOS 6:
- kernel Security Update: CESA-2018:0008
- microcode_ctl Security Update: CESA-2018:0013
- qemu-kvm Security Update: CESA-2018:0024
- libvirt Security Update: CESA-2018:0030
See further in the centos-announce Security mails for January https://lists.centos.org/pipermail/centos-announce/2018-January/date.html
Scientific Linux
Important! [as of 18th January]
Scientific Linux is following RedHat in the revert of the microcode_ctl package, see https://www.scientificlinux.org/category/sl-errata/slsa-20180093-1/:
This update supersedes the previous microcode update provided with the CVE-2017-5715 (Spectre) CPU branch injection vulnerability mitigation. Further testing has uncovered problems with the microcode provided along with the Spectre mitigation that could lead to system instabilities. As a result, this microcode update reverts to the last known good microcode version dated before 03 January 2018. You should contact your hardware provider for the latest microcode updates. IMPORTANT: If you are using Intel Skylake-, Broadwell-, and Haswell-based platforms, obtain and install updated microcode from your hardware vendor immediately. The "Spectre" mitigation requires both an updated kernel and updated microcode from your hardware vendor.
SL6:
https://www.scientificlinux.org/category/sl-errata/slsa-20180008-1/
SL7:
https://www.scientificlinux.org/category/sl-errata/slsa-20180007-1/
qemu-kvn:
SL6:
qemu-kvm: http://scientificlinux.org/category/sl-errata/slsa-20180024-1/
libvirt: http://scientificlinux.org/category/sl-errata/slsa-20180030-1/
SL7:
qemu-kvm: http://scientificlinux.org/category/sl-errata/slsa-20180023-1/
libvirt: http://scientificlinux.org/category/sl-errata/slsa-20180029-1/
Ubuntu
https://wiki.ubuntu.com/SecurityTeam/KnowledgeBase/SpectreAndMeltdown
Supermicro
https://www.supermicro.com/support/security_Intel-SA-00088.cfm
Dell
Important! [as of 23rd January]
Dell is advising that all customers and partners should not deploy the BIOS update for the Spectre vulnerability at this time due to Intel’s advisory acknowledging reboot issues and unpredictable system behaviour.
Note this is changing rather frequently
HPE
[as of January 23]
HPE has updated their advisory to note that "Marked impacted products with TBD for System ROM updates per Intel's guidance on microcode issues" - so following suit with DELL.
Lenovo
[as of January 23]
Lenovo security advisory
https://support.lenovo.com/gb/en/solutions/len-18282
Xen
- https://xenbits.xen.org/xsa/advisory-254.html
- https://blog.xenproject.org/2018/01/04/xen-project-spectremeltdown-faq/
- https://wiki.xenproject.org/wiki/Xen_Project_Meltdown_and_Spectre_Technical_FAQ
- https://wiki.xenproject.org/wiki/Respond_to_Meltdown_and_Spectre
QEMU-KVM
In order to protect hypervisors from malicious VMs, the kernel, microcode and QEMU must be updated: