Microarchitectural Data Sampling: Difference between revisions

Revision as of 18:23, 7 September 2020

Latest revision as of 09:03, 13 June 2025

(9 intermediate revisions by 8 users not shown)

Line 1:

{{short description|CPU vulnerabilities}}

{{See also|Transient execution CPU vulnerability}}

{{Use dmy dates|date=May 2019|cs1-dates=y}}

{{Infobox bug

Line 6 ⟶ 7:

| alt =

| caption = Logo designed for the vulnerabilities, featuring a wounded hand holding a broken microprocessor.

| screenshot =

| screenshot_size =

| screenshot_alt =

| screenshot_caption =

| CVE = {{CVE|2018-12126}} (Fallout),<br />{{CVE|2018-12127|link=no}} (RIDL),<br />{{CVE|2019-11091|link=no}} (RIDL, ZombieLoad),<br />{{CVE|2018-12130|link=no}} (RIDL, ZombieLoad),<br />{{CVE|2019-11135|link=no}} (ZombieLoad v2)

| discovered = 2018<ref name="Greenberg"/>

| patched = 14 May 2019

Line 20 ⟶ 21:

| website = {{URL|https://mdsattacks.com|mdsattacks.com}} {{URL|https://zombieloadattack.com|ZombieLoadAttack.com}}

}}

The '''Microarchitectural Data Sampling''' ('''MDS''') [[vulnerability (computing)|vulnerabilities]] are a set of weaknesses in [[Intel CPUs|Intel x86 microprocessors]] that use [[hyper-threading]], and leak data across protection boundaries that are architecturally supposed to be secure. The attacks exploiting the vulnerabilities have been labeled '''Fallout''', '''RIDL''' (''Rogue In-Flight Data Load''), '''ZombieLoad'''.,<ref name="new"/><ref>[https://www.heise.de/security/meldung/Spectre-NG-Luecken-OpenBSD-schaltet-Hyper-Threading-ab-4087035.html Spectre-NG-Lücken: OpenBSD schaltet Hyper-Threading ab], heise.de, 2018-06, accessed 2019-09-29</ref><ref>[https://www.youtube.com/watch?v=sDrRvrh16ws&t=75 Let's Talk To Linux Kernel Developer Greg Kroah-Hartman | Open Source Summit, 2019], TFIR, 2019-09-03</ref> and '''ZombieLoad 2'''.<ref>{{Cite web|url=https://www.forbes.com/sites/daveywinder/2019/11/13/zombie-inside-intel-confirms-zombieload-2-security-threat/|title=Intel Confirms ‘ZombieLoad'ZombieLoad 2’2' Security Threat|last=Winder|first=Davey|date=2019-11-13|website=[[Forbes]]|language=en|url-status=live|archive-url=https://archive.today/20200114182955/https://www.forbes.com/sites/kateoflahertyuk/2020/01/14/new-citrix-security-alert-us-government-issues-test-tool-for-serious-flaw/%2352628b892865|archive-date=14 January 2020|access-date=2020-01-14}}</ref>

==Description==

Line 30 ⟶ 31:

*Transactional Asynchronous Abort (TAA), [https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-11135 CVE-2019-11135]

Not all processors are affected by all variants of MDS.<ref name="linux-mds">{{cite web |title=Microarchitectural Data Sampling |url=https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html |date=2019-05-14 |work=The Linux kernel user’suser's and administrator’sadministrator's guide}}</ref>

==History==

Line 40 ⟶ 41:

==Impact==

According to varying reports, Intel processors dating back to 2011<ref>{{cite news |url=httphttps://social.techcrunch.com/2019/05/14/zombieload-flaw-intel-processors/ |title=New secret-spilling flaw affects almost every Intel chip since 2011 |author-first=Zach |author-last=Whittaker |work=TechCrunch |date=14 May 2019 |access-date=14 May 2019}}</ref> or 2008<ref name="Greenberg"/> are affected, and the fixes may be associated with a [[computer performance|performance]] drop.<ref name="BBC-20190515">{{cite news |author=<!-- Staff --> |title=Intel Zombieload bug fix to slow data centre computers |url=https://www.bbc.com/news/technology-48278400 |date=15 May 2019 |work=[[BBC News]] |access-date=15 May 2019}}</ref><ref name="PH-20190524">{{cite news |author-last=Larabel |author-first=Michael |title=Benchmarking AMD FX vs. Intel Sandy/Ivy Bridge CPUs Following Spectre, Meltdown, L1TF, Zombieload |url=https://www.phoronix.com/scan.php?page=article&item=sandy-fx-zombieload&num=1 |date=24 May 2019 |work=[[Phoronix]] |access-date=25 May 2019}}</ref> Intel reported that processors manufactured in the month before the disclosure have mitigations against the attacks.<ref name="Greenberg">{{cite news |author-first1=Andy |author-last1=Greenberg |url=https://www.wired.com/story/intel-mds-attack-speculative-execution-buffer/ |title=Meltdown Redux: Intel Flaw Lets Hackers Siphon Secrets from Millions of PCs |newspaper=[[WIRED]] |date=14 May 2019 |access-date=14 May 2019}}</ref>

Intel characterized the vulnerabilities as "low-to-medium" impact, disagreeing with the security researchers who characterized them as major, and disagreeing with their recommendation that operating system software manufacturers should completely disable [[hyperthreading]].<ref name="Greenberg"/><ref name="PCW-20190515">{{cite news |author-last=Mah Ung |author-first=Gordan |title=Intel: You don't need to disable Hyper-Threading to protect against the ZombieLoad CPU exploit - "ZombieLoad" exploit seems to put Intel's Hyper-Threading at risk of being put down |url=https://www.pcworld.com/article/3395439/intel-hyper-threading-zombieload-cpu-exploit.html |date=15 May 2019 |work=[[PC World]] |access-date=15 May 2019}}</ref> Nevertheless, the ZombieLoad vulnerability can be used by hackers exploiting the vulnerability to steal information recently accessed by the affected microprocessor.<ref name="steal data">{{cite web |url=https://www.theverge.com/2019/5/14/18623708/zombieload-attack-intel-processors-speculative-execution |title=ZombieLoad attack lets hackers steal data from Intel chips |author-first=Jacob |author-last=Kastrenakes |website=[[The Verge]] |date=14 May 2019 |access-date=15 May 2019}}</ref>

Line 49 ⟶ 50:

*Intel incorporated fixes in its processors starting shortly before the public announcement of the vulnerabilities.<ref name="Greenberg"/>

*On 14 May 2019, a mitigation was released for the [[Linux kernel]],<ref>{{Cite web |url=https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.1.2 |title=ChangeLog-5.1.2 |date=14 May 2019 |website=The Linux Kernel Archives |archive-url=https://web.archive.org/web/20190515071751/https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.1.2 |archive-date=15 May 2019 |url-status=live |access-date=15 May 2019}}</ref> and [[Apple Inc.|Apple]], [[Google]], [[Microsoft]], and [[Amazon (company)|Amazon]] released emergency patches for their products to mitigate ZombieLoad.<ref>{{cite news |url=httphttps://social.techcrunch.com/2019/05/14/intel-chip-flaws-patches-released/ |title=Apple, Amazon, Google, Microsoft and Mozilla release patches for ZombieLoad chip flaws |author-first=Zach |author-last=Whittaker |work=TechCrunch |access-date=14 May 2019}}</ref>

*On 14 May 2019, [[Intel]] published a security advisory on its website detailing its plans to mitigate ZombieLoad.<ref name="sa-00233">{{cite web |url=https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00233.html |title=INTEL-SA-00233 |website=Intel |access-date=14 May 2019}}</ref>

== See also ==

* [[Hardware security bug]]

* [[Transient execution CPU vulnerabilities]]

* [[Hardware security bug]]

== References ==

Line 61 ⟶ 62:

== Further reading ==

=== Original papers by the researchers ===

* {{cite paperweb |title=ZombieLoad: Cross-Privilege-Boundary Data Sampling |author-first1=Michael |author-last1=Schwarz |author-first2=Moritz |author-last2=Lipp |author-first3=Daniel |author-last3=Moghimi |author-first4=Jo |author-last4=Van Bulck |author-first5=Julian |author-last5=Stecklina |author-first6=Thomas |author-last6=Prescher |author-first7=Daniel |author-last7=Gruss |format=[[PDF]] |url=https://zombieloadattack.com/zombieload.pdf |date=2019-05-14}}

* {{cite paperweb |title=RIDL: Rogue In-Flight Data Load |author-first1=Stephan |author-last1=van Schaik |author-first2=Alyssa |author-last2=Milburn |author-first3=Sebastian |author-last3=Österlund |author-first4=Pietro |author-last4=Frigo |author-first5=Giorgi |author-last5=Maisuradze |author-first6=Kaveh |author-last6=Razavi |author-first7=Herbert |author-last7=Bos |author-first8=Cristiano |author-last8=Giuffrida |format=[[PDF]] |url=https://mdsattacks.com/files/ridl.pdf |date=2019-05-14}}

* {{cite paperweb |title=Fallout: Reading Kernel Writes From User Space |author-first1=Marina |author-last1=Minkin |author-first2=Daniel |author-last2=Moghimi |author-first3=Moritz |author-last3=Lipp |author-first4=Michael |author-last4=Schwarz |author-first5=Jo |author-last5=Van Bulck |author-first6=Daniel |author-last6=Genkin |author-first7=Daniel |author-last7=Gruss |author-first8=Frank |author-last8=Piessens |author-first9=Berk |author-last9=Sunar |author-first10=Yuval |author-last10=Yarom |format=[[PDF]] |url=https://mdsattacks.com/files/fallout.pdf |date=2019-05-14}}

* {{cite paperweb |title=ZombieLoad: Cross Privilege-Boundary Data Leakage |author-first1=Jacek |author-last1=Galowicz |author-first2=Thomas |author-last2=Prescher |author-first3=Julian |author-last3=Stecklina |url=https://www.cyberus-technology.de/posts/2019-05-14-zombieload.html |publisher=Cyberus Technology GmbH |date=2019-05-14}}

* {{cite web |url=https://cpu.fail/ |title=cpu.fail |date=2019-05-14 |publisher=[[Graz University of Technology]]}}

Line 79 ⟶ 80:

{{Portal bar|Business and economics}}

[[Category:SpeculativeTransient execution securityCPU vulnerabilities]]

[[Category:Computer security exploits]]

[[Category:Hardware bugs]]

[[Category:Intel x86 microprocessors]]

[[Category:Side-channel attacks]]

[[Category:2019 in computing]]

[[Category:X86 architecture]]

[[Category:X86 memory management]]