Attacking Hypervisors via Firmware and Hardware

More documents

Recommendations

Info

Root cause? Port B2h is open to VM in I/O bitmap
Page 1 and 2: Attacking Hypervisorsvia Firmware a
Page 3 and 4: Image sourceHypervisor Based Isolat
Page 5 and 6: Hypervisor Based IsolationVirtual M
Page 7 and 8: CPU Virtualization (simplified)VM G
Page 9 and 10: Hypervisor ProtectionsSystem Firmwa
Page 11 and 12: What is firmware rootkit?Virtual Ma
Page 13 and 14: “Backdoor” for attacker’s VM1
Page 15 and 16: Using hardware SPI flash programmer
Page 17 and 18: Software access and exploiting some
Page 19 and 20: Installing rootkit in firmware from
Page 21 and 22: We flashed rootkited part of firmwa
Page 23 and 24: VMCS, MSR and I/O bitmaps..
Page 25 and 26: Image sourceAttacking Hypervisor Em
Page 27 and 28: Did you know that VMMs emulate virt
Page 29 and 30: Crashing Host or Guest from Ring3
Page 31 and 32: Pointer Vulnerabilities in SMI Hand
Page 33: DEMOAttacking Hypervisor viaPoisono
Page 37 and 38: Point SMI handler to overwrite VMM
Page 39 and 40: Sometimes attacker doesn’t need a
Page 41 and 42: NORMAL BOOTS3 RESUMEWaking the syst
Page 43 and 44: NORMAL BOOTMODIFYS3 RESUMEXen expos
Page 45 and 46: Dumping Dom0VMCS from memoryprotect
Page 47 and 48: Déjà vu?Xen 0wning Trilogy (Part
Page 49 and 50: Image sciencenews.orgTools and Miti
Page 51 and 52: Testing hypervisors…Simple hardwa
Page 53 and 54: Conclusions• Compromised firmware
Page 55: Thank You!

Attacking Hypervisors via Firmware and Hardware

Create successful ePaper yourself

Delete template?

Save as template?