Skip to main content
Information Security

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

2
  • Writing a more elaborate answer would be helpful for other readers. So that you know, this happens because gdb alter the process env, which is at the top of the stack, shifting everything down. You can see this with a trivial assembly program that prints rsp (possibly even just return the low byte of rsp). With ASRL disabled, it will print the same value at every run but when run in gdb it will have a different value. That's why we use nop sleds. You can also simply write your exploit using a different offset for gdb (to debug it) and for the terminal. Commented Jul 19 at 11:15
  • @MargaretBloom Hey! you are absolutely right, its kinda selfish of me just to move forward after i figured out the solution without disclosing the method, i have replicated what you have written and soon I'm going to update the comment with possible changes. Thank you so much for direction though i appreciate it a lot! Commented Jul 21 at 14:01