Explore >> Select a destination
|
You are here 
|
satharus.me | ||
| | | | |
manybutfinite.com
|
|
| | | | | Last week we looked at how the stack works and how stack frames are built during function prologues. Now it's time to look at the inverse process as stack frames are destroyed in function epilogues. | |
| | | | |
danielnouri.org
|
|
| | | | | [AI summary] The post explains how to debug memory access violations and segmentation faults in C and C++ programs using AddressSanitizer and the GNU Debugger. | |
| | | | |
mouha.be
|
|
| | | | | [AI summary] A cryptography researcher coordinates the public disclosure of a SHA-3 buffer overflow vulnerability found in the official XKCP implementation and related projects, detailing how the flaw allows for memory exhaustion and potential code execution. | |
| | | | |
blog.coffinsec.com
|
|
| | | While poking at an HTTP server I had come across I eventually discovered a buffer overflow in the code responsible for processing the URI part of an HTTP request. This post walks through the process of finding the root-cause of the bug and write a PoC exploit using return-to-libc to call exit() cleanly across all running threads and kill the server. | ||
