Timeline for ret2libc - why need 4 bytes of garbage
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 10, 2019 at 8:35 | answer | added | akshayknows | timeline score: 0 | |
| Dec 8, 2019 at 5:29 | vote | accept | DaniDin | ||
| S Dec 6, 2019 at 8:46 | history | suggested | guntbert | CC BY-SA 4.0 |
spelling, grammar, formatting, even some wording
|
| Dec 6, 2019 at 7:20 | answer | added | Kamil Solecki | timeline score: 1 | |
| Dec 5, 2019 at 23:20 | review | Suggested edits | |||
| S Dec 6, 2019 at 8:46 | |||||
| Dec 5, 2019 at 20:45 | answer | added | wireghoul | timeline score: 0 | |
| Dec 5, 2019 at 20:37 | comment | added | DaniDin | i read the article in this site: 0x00sec.org/t/exploiting-techniques-000-ret2libc/1833. | |
| Dec 5, 2019 at 20:25 | comment | added | ExecutionByFork | ROP attacks rely on proper alignment of the injected addresses (pointing to libc gadgets) in the stack. These 4 bytes are probably just buffer bytes used to align the address correctly, but this can change depending on the system architecture and even how the stack is laid out (where the return address you are trying to overwrite lies). It's hard to say when your question does not contain any links to whatever article you were reading, or any example of how the target program is set up. Can you clarify on these points? Where did you read about ret2libc? | |
| Dec 5, 2019 at 19:55 | review | First posts | |||
| Dec 5, 2019 at 23:20 | |||||
| Dec 5, 2019 at 19:54 | history | asked | DaniDin | CC BY-SA 4.0 |