security - Buffer size and chance of ASLR brute force -


how increasing buffer size increase chances of aslr brute force succeeding?

this related project did. had exploit_1.c program had buffer/character array (originally of size 517). buffer set nops memset. place shellcode , return address buffer, written file called badfile. program took 1 argument return address. had stack.c program which, in function called bof, copied contents of badfile buffer of size 12.

i had read 1 method put jump @ end of nop sled , have redirect shellcode. however, shellcode 24 bytes, , @ maximum had 16 bytes before return address. did put shellcode @ end of buffer.

the 3rd task given pick return addresses such exploit program (modified buffer size of course) had higher average chance of succeeding buffer sizes 1000, 10000, , 100000. used bash while loop counter count how many tries aslr brute force took.

so thinking more memory nop sled longer. there's got more that.

the addresses picked were: 0xbf87f030 0xbf82e3d0 0xbfe0fb60


Comments

Popular posts from this blog

ios - iPhone/iPad different view orientations in different views , and apple approval process -

php - HTTP_REFERER woes: How can I allow access to a specific page, only when a visitor has visited another specific page beforehand? -

java Extracting Zip file -