Explore >> Select a destination
|
You are here 
|
blog.bricked.tech | ||
| | | | |
blog.xyz.is
|
|
| | | | | ||
| | | | |
tcode2k16.github.io
|
|
| | | | | a random blog about cybersecurity and programming | |
| | | | |
wachter-space.de
|
|
| | | | | This is a writeup of an easy/medium pwn challenge called "Profile" featuring a type confusion, some GOT overwriting, and a funny but unnecessary one gadget exploit for the fun of it. We are given the following files: main.c profile (binary) Dockerfile docker-compose.yml Let's look at main.c and see if we can spot a vulnerability from the provided source code. #include #include #include #include struct person_t { int id; int age; char *name; }; void get_value(const char *msg, void *pval) { printf("%s", ms... | |
| | | | |
blog.trailofbits.com
|
|
| | | By Alan Cao If you love exploit mitigations, you may have heard of a new system call named mseal landing into the Linux kernel's 6.10 release, providing a protection called "memory sealing." Beyond notes from the authors, very little information about this mitigation exists. In this blog post, we'll explain what this syscall is, including... | ||
