# Big Geeks Only: Buffer Overflows: Anatomy of an Exploit

**URL:** <https://forums.speedlife.net/t/big-geeks-only-buffer-overflows-anatomy-of-an-exploit/219667>\
**Category:** NYSpeed Off Topic\
**Created:** [January 10, 2012, 12:56pm UTC](https://forums.speedlife.net/t/big-geeks-only-buffer-overflows-anatomy-of-an-exploit/219667 "2012-01-10T12:56:15Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![boxxa](https://yyz2.discourse-cdn.com/flex034/user_avatar/forums.speedlife.net/boxxa/32/5045_2.png) [@boxxa](https://forums.speedlife.net/u/boxxa)\
**Post date:** [January 10, 2012, 12:56pm UTC](https://forums.speedlife.net/t/big-geeks-only-buffer-overflows-anatomy-of-an-exploit/219667/1 "2012-01-10T12:56:15Z")

</div>

Really awesome read about buffer overflows. My only interest a few people but was a nice 25 page article.

[http://bit.ly/x8lpVF](http://t.co/Ovth0pk4) [PDF]

> Buffer Overflows: Anatomy of an Exploit  
> A Look at How Systems are Exploited, and Why These Exploits Exist

> This paper will look at how buffer overflows occur on the stack. It will outline  
> how the stack should be visualised when software engineers code in languages that  
> requires manual memory management(assembly, c, c++, etc) and the importance of  
> the ‘null terminating character’ in possible vulnerabilities.  
> Before considering the exploitation of systems and the methods that should be  
> employed to remove them, some time will be spent explaining the stack in the x86  
> architecture, the flat memory model employed by modern operating systems how  
> payloads are written and delivered to exploited programs.

---

<div class="post-metadata">

**Author:** ![ProgRocker](https://yyz2.discourse-cdn.com/flex034/user_avatar/forums.speedlife.net/progrocker/32/5434_2.png) [@ProgRocker](https://forums.speedlife.net/u/ProgRocker)\
**Post date:** [January 10, 2012, 12:58pm UTC](https://forums.speedlife.net/t/big-geeks-only-buffer-overflows-anatomy-of-an-exploit/219667/2 "2012-01-10T12:58:30Z")

</div>

:shrug:

---

<div class="post-metadata">

**Author:** ![Gus](https://yyz2.discourse-cdn.com/flex034/user_avatar/forums.speedlife.net/gus/32/5112_2.png) [@Gus](https://forums.speedlife.net/u/Gus)\
**Post date:** [January 10, 2012, 1:08pm UTC](https://forums.speedlife.net/t/big-geeks-only-buffer-overflows-anatomy-of-an-exploit/219667/3 "2012-01-10T13:08:22Z")

</div>

I didn’t get much from this, but my buddy that writes scripts for everything here found it amusing.

---

<div class="post-metadata">

**Author:** ![LZ1](https://avatars.discourse-cdn.com/v4/letter/l/7ab992/32.png) [@LZ1](https://forums.speedlife.net/u/LZ1)\
**Post date:** [January 10, 2012, 2:17pm UTC](https://forums.speedlife.net/t/big-geeks-only-buffer-overflows-anatomy-of-an-exploit/219667/4 "2012-01-10T14:17:27Z")

</div>

And it’s on PDF how cute lol

---

<div class="post-metadata">

**Author:** ![LZ1](https://avatars.discourse-cdn.com/v4/letter/l/7ab992/32.png) [@LZ1](https://forums.speedlife.net/u/LZ1)\
**Post date:** [January 10, 2012, 4:46pm UTC](https://forums.speedlife.net/t/big-geeks-only-buffer-overflows-anatomy-of-an-exploit/219667/5 "2012-01-10T16:46:13Z")

</div>

To bad it’s not that easy anymore with DEP, SEH, ASLR…

Now you need to do this…

> **[Exploit writing tutorial part 11 : Heap Spraying Demystified](https://www.corelan.be/index.php/2011/12/31/exploit-writing-tutorial-part-11-heap-spraying-demystified/)**
>
> A lot has been said and written already about heap spraying, but most of the existing documentation and whitepapers focus on IE7 or older versions.
> Although there are a number of public exploits a…