<- Back to the timetable

New memory corruption attacks: why can't we have nice things?

gannimo, npc@berkeley.edu

Memory corruption plagues systems not just since Aleph1's article on stack smashing but since the dawn of computing. With the rise of defense techniques like stack cookies, ASLR, and DEP, attacks have grown more sophisticated but control-flow hijack attacks are still prevalent. Attackers can still launch code reuse attacks, often using some form of information disclosure. Stronger defense mechanisms have been proposed but none have seen wide deployment so far due to the time it takes to deploy a security mechanism, incompatibility with specific features, and most severely due to performance overhead. Control-Flow Integrity (CFI) and Code-Pointer Integrity (CPI) are two of the hottest upcoming defense mechanisms. After quickly introducing them, we will discuss differences and advantages/disadvantages of both approaches, especially the security benefits they give under novel memory corruption attacks. CFI guarantees that the dynamic control flow follows the statically determined control-flow of the compiled program but an attacker may reuse any of the statically valid transitions at any control flow transfer. CPI on the other hand is a dynamic property that enforces memory safety guarantees like bounds checks for code pointers by separating code pointers from regular data. Data-only attacks are possible both for CFI and CPI. Counterfeit Object-Oriented Programming (COOP) and Control-Flow Bending (CFB) are two novel attack mechanisms. COOP reuses complete functions as gadgets, mitigating several defense mechanisms and CFB bends the control flow along valid but unintended paths in the control flow graph of a program. We will discuss COOP and CFB attacks, focusing on mitigating strong novel defense mechanisms.

Download Slides
PDF ZIP JSON
0:01:27 - 0:01:30
0:01:52 - 0:02:07
0:02:56 - 0:03:06
0:03:26 - 0:03:33
0:03:40 - 0:03:54
0:04:02 - 0:04:09
0:04:15 - 0:04:25
0:04:33 - 0:04:35
0:04:35 - 0:04:41
0:04:41 - 0:04:51
0:04:53 - 0:04:56
0:05:04 - 0:05:07
0:05:13 - 0:05:25
0:06:03 - 0:06:18
0:06:19 - 0:06:29
0:06:38 - 0:07:14
0:07:19 - 0:07:32
0:08:06 - 0:08:10
0:08:16 - 0:08:33
0:08:33 - 0:09:11
0:09:21 - 0:09:30
0:09:31 - 0:09:44
0:09:44 - 0:09:56
0:09:56 - 0:10:06
0:10:17 - 0:10:21
0:10:21 - 0:10:25
0:10:26 - 0:10:34
0:11:05 - 0:11:14
0:11:18 - 0:11:48
0:12:19 - 0:12:46
0:12:47 - 0:12:54
0:12:54 - 0:13:20
0:13:38 - 0:13:54
0:14:11 - 0:15:04
0:16:02 - 0:16:11
0:16:36 - 0:16:43
0:16:43 - 0:16:53
0:18:01 - 0:18:07
0:18:11 - 0:18:30
0:18:30 - 0:18:33
0:18:34 - 0:18:40
0:18:41 - 0:18:46
0:18:46 - 0:19:09
0:19:10 - 0:19:19
0:19:50 - 0:20:01
0:20:02 - 0:20:13
0:20:30 - 0:20:40
0:20:41 - 0:20:48
0:21:09 - 0:21:17
0:21:47 - 0:21:54
0:22:02 - 0:22:15
0:22:25 - 0:22:34
0:22:41 - 0:22:47
0:22:47 - 0:23:04
0:23:24 - 0:23:33
0:23:54 - 0:24:03
0:24:03 - 0:24:23
0:24:23 - 0:24:44
0:24:44 - 0:25:06
0:25:06 - 0:25:25
0:25:33 - 0:25:43
0:26:59 - 0:27:13
0:27:29 - 0:27:54
0:28:01 - 0:28:08
0:28:11 - 0:28:20
0:28:37 - 0:29:29
0:29:36 - 0:29:44
0:29:44 - 0:29:54
0:29:59 - 0:30:12
0:30:12 - 0:30:20
0:30:31 - 0:30:40
0:30:55 - 0:31:04
0:31:26 - 0:31:35
0:31:56 - 0:32:17
0:32:30 - 0:32:40
0:32:50 - 0:33:00
0:33:21 - 0:33:47
0:33:48 - 0:33:54
0:34:00 - 0:34:04
0:34:04 - 0:34:09
0:34:10 - 0:34:19
0:34:20 - 0:34:36
0:35:03 - 0:35:12
0:35:16 - 0:35:22
0:36:39 - 0:36:48
0:36:50 - 0:37:06
0:37:21 - 0:37:31
0:38:36 - 0:38:47
0:38:47 - 0:38:53
0:38:55 - 0:38:57
0:38:58 - 0:39:03
0:39:03 - 0:39:24
0:39:26 - 0:40:13
0:40:34 - 0:40:44
0:41:13 - 0:41:21
0:42:24 - 0:42:43
0:43:58 - 0:44:08
0:44:30 - 0:44:52
0:44:53 - 0:44:57
0:44:58 - 0:45:07
0:45:16 - 0:45:26
0:45:49 - 0:45:55
0:45:56 - 0:46:09
0:46:24 - 0:46:26
0:46:28 - 0:46:30
0:46:38 - 0:46:41
0:47:03 - 0:47:23
0:47:45 - 0:47:55
0:47:57 - 0:48:02
0:48:02 - 0:48:11
0:48:17 - 0:48:24
0:50:06 - 0:50:11
0:50:12 - 0:50:16
0:50:34 - 0:50:38
0:51:01 - 0:51:11
0:51:28 - 0:51:37
0:51:38 - 0:51:54