Databases
StackOverflow2013
Postsdbo
POWhat are some advanced and modern resources on exploit writing?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat are some advanced and modern resources on exploit writing?
    primarykey
    data
    text
    <p>I've read and finished both <a href="http://rads.stackoverflow.com/amzn/click/0764574817" rel="noreferrer">Reversing: Secrets of Reverse Engineering</a> and <a href="http://rads.stackoverflow.com/amzn/click/1593271441" rel="noreferrer">Hacking: The Art of Exploitation</a>. They both were illuminating in their own way but I still feel like a lot of the techniques and information presented within them is outdated to some degree.</p> <p>When the infamous Phrack Article, <a href="http://insecure.org/stf/smashstack.html" rel="noreferrer">Smashing the Stack for Fun and Profit</a>, was written 1996 it was just before what I sort of consider the Computer Security "golden age".</p> <p>Writing exploits in the years that followed was relatively easy. Some basic knowledge in C and Assembly was all that was required to perform buffer overflows and execute some arbitrary shell code on a victims machine.</p> <p>To put it lightly, things have gotten <em>a lot</em> more complicated. Now security engineers have to contend with things like <a href="http://en.wikipedia.org/wiki/Address_space_layout_randomization" rel="noreferrer">Address Space Layout Randomization (ASLR)</a>, <a href="http://en.wikipedia.org/wiki/Data_Execution_Prevention" rel="noreferrer">Data Execution Prevention (DEP)</a>, <a href="http://en.wikipedia.org/wiki/Buffer_overflow_protection" rel="noreferrer">Stack Cookies</a>, Heap Cookies, and much more. The complexity of writing exploits went up at least an order of magnitude.</p> <p>You can't event <em>run</em> most of the buffer overrun exploits in the tutorials you'll find today without compiling with a bunch of flags to turn off modern protections.</p> <p>Now if you want to write an exploit you have to devise ways to turn off DEP, spray the heap with your shell-code hundreds of times and attempt to guess a random memory location near your shellcode. Not to mention the pervasiveness of managed languages in use today that are much more secure when it comes to these vulnerabilities.</p> <p>I'm looking to extend my security knowledge beyond writing toy-exploits for a decade old system. I'm having trouble locating resources that help address the issues of writing exploits in the face of all the protections I outlined above.</p> <p>What are the more advanced and prevalent papers, books or other resources devoted to contending with the challenges of writing exploits for modern systems?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USmmcdole
    1. USmmcdole
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhat are some advanced and modern resources on exploit writing?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhat are some advanced and modern resources on exploit writing?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhat are some advanced and modern resources on exploit writing?
      1. USVinko Vrsalovic
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload