Welcome back.
Let's do the first example of ethical injection.
So in the previous video, we took a quick guide that told us how exactly we can exploit certain types
of ethical injection.
Right now, let's see how we can put that to practice with our WASP.
B.W., a machine.
So what I want you to do is I want you to go to the WASP Mutilate to.
And from here, I want you to navigate to us 2013, a one injection eskow, and we want to go with the
first example, which is user info ask you out.
Let's click on that.
And this is the application that we want to try to perform Eskil injection on.
So if we follow the same guide from the previous video, we should be able to get it to work.
Let's give it a try.
So first, let's take a look at the application itself.
It requires the name and the password in order to view account details.
Let's type anything just to see whether it will work.
Click on the account details and we get results for test zero records found authentication, error,
bad username or password.
If we remember from the previous video, in most cases, we can take a look whether there is an ESKILD
injection on a webpage, if we make the application run into an error by specifying something like a
single quote, let's give it a try.
If we tried to specify a single quote for both name and password and we click on View Account details.
We still don't get anything.
Let's also give it a try like this test single code and test single code.
Perhaps we can make it crash or perhaps we can make it give us some details that we didn't have.
And by those details, I mean something like this error message.
So we typed in test single code for the name and for the password.
And it gave us this error message.
We didn't exploit it yet, but we are aware that this does cause an error in the application.
And if we take a closer look inside this error, it does also give us the Esequiel query used to query
the database.
If we take a look where our user name is being specified, we have single, quote, creating a problem
right here and we also have a single quote, creating a problem in the password variable.
Why?
Well, because both of them have one open single quote into to close single quote resulting in this
error.
So what we can do is we can try to perform the same thing from the previous video.
Just this time.
We don't really know the correct username like we did in the previous lecture or in the previous guide.
How can we bypass that?
Well, we can type the same comment, which is, for example, test single quote or one equals one.
And we can type this for both username and password now, since our username is in the middle of the
syntax, we can't really use dash dash at the end to comment out the rest.
So what we are going to do is we're going to type it in like this test, single code or single quote.
One single quote equals single code one.
This will be our username.
Now, you could be asking, well, why didn't we specify single code at the end?
Well, that is because we already have it inside the ESKIL query.
Our input is getting stored between the single quotes by default.
So this and single code inside of the username will replace the end single quote that should belong
to this one.
No.
And then we will get the username to be equal to test or one on their single code is equal to one under
single quotes, which should be correct.
We want to specify the same thing for our password.
So pretty much you can just copy and paste it right here, and if we click on View Account details,
scroll a little bit down.
Here it is.
We successfully exploited the application.
And now since we didn't specify a unique user, now we got the entire database of users outputted right
here.
We got their usernames and passwords as well as their signature, and we got passwords for every username
inside the database.
Now you can see how dangerous this can be.
Now we can access any of these accounts that we got right here by going simply on the login screen,
which is right here, and specifying their username and password.
This was also a simple example, but nonetheless, it has a powerful result that you can really do some
damage with.
But in the next lecture, we're going to take a look at more advanced example inside of our TBWA application.
Thank you for watching.
And we'll see you in the next lecture.