All right.
Welcome back.
And we're going to see.
We go back to our session, remember, we were able to leak the canary from the canary.
And notice how it changes and we have to dynamically capture the canary, repair it so that way it doesn't
trigger stack smashing detected.
So we're going to do a go exploit API then edit it.
Now remember I am who am I id?
So I am basically a underprivileged user.
If I try to pseudo, let's say pseudo pseudo or s you root and then I try to enter my password player.
It's the wrong password.
See, because I can't sit out.
It's not a suitable user.
But if I ran my exploit python three exploit dot pie ID, I am now a root user.
The reason why is because I hardcoded root within this vulnerable binary.
And from this point on, you can actually just read the fly.
So I just want to admit to you that I've been having some issues with poll tools.
So if you have any issues like end of file errors and stuff like that, immediately let me know in the
QA section.
Tell me exactly what you did.
I will address these issues because this is not the first time I've seen it.
But I have restarted Docker on these exercises so many times.
There might be some sort of issue with that.
I've seen this issue happen with MacBooks and stuff.
So let me know if the stationary bypass using specifically powered tools is having issues outside of
that.
If you manage to get the fly, go submit it as your quiz answer.