back

What could possibly go wrong with <insert x86 instruction here>?

Side effects include side-channel attacks and bypassing kernel ASLR

If you suspend your transcription on amara.org, please add a timestamp below to indicate how far you progressed! This will help others to resume your work!

Please do not press “publish” on amara.org to save your progress, use “save draft” instead. Only press “publish” when you're done with quality control.

Video duration
00:55:05
Language
English
Abstract
Hardware is often considered as an abstract layer that behaves correctly, just executing instructions and outputting a result. However, the internal state of the hardware leaks information about the programs that are executing. In this talk, we focus on how to extract information from the execution of simple x86 instructions that do not require any privileges. Beyond classical cache-based side-channel attacks, we demonstrate how to perform cache attacks without a single memory access, as well as how to bypass kernel ASLR. This talk does not require any knowledge about assembly. We promise.

When hunting for bugs, the focus is mostly on the software layer. On the other hand, hardware is often considered as an abstract layer that behaves correctly, just executing instructions and outputing a result. However, the internal state of the hardware leaks information about the programs that are running. Unlike software bugs, these bugs are not easy to patch on current hardware, and manufacturers are also reluctant to fix them in future generations, as they are tightly tied with performance optimizations.

In this talk, we focus on how to extract information from the execution of simple x86 instructions that do not require any privileges. The most studied microarchitectural attacks are beyond doubt cache attacks. Indeed, the timing of a memory access depends heavily on the state of the CPU cache. But beyond memory accesses that are the base of classical cache-based side-channel attacks, other x86 instructions leak information about the internal state of the hardware, and thus about running programs. First, we present side channels caused by the "clflush" instruction, that flushes all content of the cache. We will explain how it can be used to perform side-channel attacks that are faster and stealthier than their classical counterpart, without performing so much as a single memory access [1]. Second, we present side channels caused by the prefetch instructions. We will explain how these instructions can be used to translate virtual addresses to physical addresses - without the use of the proc interface that is restricted today -, and to bypass kernel ASLR [2].

This talk does not require any knowledge about assembly. We promise.

The talk will be given as a joint presentation by Clémentine Maurice and Moritz Lipp.



[1] Daniel Gruss, Clémentine Maurice, Klaus Wagner and Stefan Mangard, "Flush+Flush: A Fast and Stealthy Cache Attack", DIMVA 2016
[2] Daniel Gruss, Clémentine Maurice, Anders Fogh, Moritz Lipp, Stefan Mangard, "Prefetch Side-Channel Attacks: Bypassing SMAP and Kernel ASLR", CCS 2016

Talk ID
8044
Event:
33c3
Day
1
Room
Saal G
Start
11:30 a.m.
Duration
01:00:00
Track
Security
Type of
lecture
Speaker
Clémentine Maurice
Moritz Lipp
Talk Slug & media link
33c3-8044-what_could_possibly_go_wrong_with_insert_x86_instruction_here

Talk & Speaker speed statistics

Very rough underestimation:
152.5 wpm
826.5 spm
100.0% Checking done100.0%
0.0% Syncing done0.0%
0.0% Transcribing done0.0%
0.0% Nothing done yet0.0%
  

Work on this video on Amara!

Talk & Speaker speed statistics with word clouds

Whole talk:
152.5 wpm
826.5 spm
cacheaddressattacksdatamemoryinstructiontimeflushattacklevelchannelthingkernelaccessbasicallyvictimaddressesprefetchphysicaltalkspaceflashinstructionsperformanceloadedcorenicecmbitcpuclflushreloaduservirtualloadaccessedattackercovertbitslevelssetsharedprogrampointsecondmicrophonefindinterestingtodayworks