Hello and welcome to the cyber. Very secure coding course. My name is Sonny Wear, and this is AWAS top 10 for 2013 a two broken authentication and session management lab in solution.
The lab is Web goat authentication flaws.
Multi level. Log in to
now in this lab, you will see me use a Firefox plugin called tamper data.
You are free to also use tamper data if you like, or you can use birth. Sweet as we've been using in other labs, either too will accomplish the same tasks.
This is the video solution for multi level. Log in to
it says you are an attacker called Chou. You have a valid account by web coat financial.
You're goes toe log in as Jane.
Now your user name is Joe in Your password is banana.
And these are your tans.
there's a couple of flaws here.
Um, the first is, of course, the fact that programmers assume that
one stage happens before the next stage can happen. And I'm gonna show you how that is flawed. So
go ahead and properly log in as Joe
and then next Joe would be assigned this transaction authorization number. At least that's what the programmers assume in their code.
I'm gonna go ahead and
and all I'm gonna do is change this hidden field here that has User Joe.
I'm just going to change that to Jane,
and then I am able to successfully log in his Jane. So unfortunately, there was a combination of problems.
One is, of course, having weak form of identification, just being hidden field
on the form itself, which can easily be
manipulated and spoofed since it's located on the quiet side.
And there wasn't any kind of validation occurring on the service side, obviously.
And then secondly, of course, this whole idea that programmers assume that
Stage one is always going to happen before Stage two can happen. There's no kind of validation check. And so he's easily able to