{"action":"opened","issue":{"url":"https://api.github.com/repos/linuxchixin/talks/issues/37","repository_url":"https://api.github.com/repos/linuxchixin/talks","labels_url":"https://api.github.com/repos/linuxchixin/talks/issues/37/labels{/name}","comments_url":"https://api.github.com/repos/linuxchixin/talks/issues/37/comments","events_url":"https://api.github.com/repos/linuxchixin/talks/issues/37/events","html_url":"https://github.com/linuxchixin/talks/issues/37","id":308325097,"number":37,"title":"Exploring the Heap","user":{"login":"jaiverma","id":8081757,"avatar_url":"https://avatars1.githubusercontent.com/u/8081757?v=4","gravatar_id":"","url":"https://api.github.com/users/jaiverma","html_url":"https://github.com/jaiverma","followers_url":"https://api.github.com/users/jaiverma/followers","following_url":"https://api.github.com/users/jaiverma/following{/other_user}","gists_url":"https://api.github.com/users/jaiverma/gists{/gist_id}","starred_url":"https://api.github.com/users/jaiverma/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jaiverma/subscriptions","organizations_url":"https://api.github.com/users/jaiverma/orgs","repos_url":"https://api.github.com/users/jaiverma/repos","events_url":"https://api.github.com/users/jaiverma/events{/privacy}","received_events_url":"https://api.github.com/users/jaiverma/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-03-25T06:02:49Z","updated_at":"2018-03-25T06:02:49Z","closed_at":null,"author_association":"NONE","body":"**Abstract**\r\n\r\nAn examination of the glibc heap memory manager.\r\n\r\n**About**\r\n\r\nA behind the scenes look at how dynamic memory management works on Linux and what happens when you call `malloc` or `free` in a program.\r\n\r\nAn examination of common programmer mistakes in memory management which could lead to security vulnerabilities and methods on exploiting them. This includes a look at vulnerabilities like Use-After-Free and Heap Overflow and how to achieve arbitrary code execution.\r\n\r\n**Pre-requisites**\r\n\r\n- Usage of `malloc` and `free`\r\n- Basic understanding of C programming\r\n\r\n- A laptop running Ubuntu 16.04 or below with `gdb` installed. (Ubuntu 17 won't work because the memory allocation algorithm has changed in the latest release)\r\n\r\n**Expected duration**\r\n\r\n1 hour\r\n\r\n**Level**\r\n\r\nIntermediate\r\n\r\n**Resources**\r\n\r\n- [https://code.woboq.org/userspace/glibc/malloc/malloc.c.html](link)\r\n- [https://sploitfun.wordpress.com/2015/02/10/understanding-glibc-malloc](link)\r\n\r\n**Speaker Bio**\r\n\r\nIndependent infosec researcher and freelancer. CTF player with ByteBandits team.\r\n\r\n\r\n###### - Can be done after the talk/workshop -\r\n\r\n[Include link to slides here](link)\r\n\r\n[Include link to video here](link)\r\n"}}
{"actor":{"display_login":"jaiverma"}}