WEBVTT

00:00:00.000 --> 00:00:10.140 align:middle line:90%


00:00:10.140 --> 00:00:13.980 align:middle line:84%
We've seen some websites that
have SQL databases connected

00:00:13.980 --> 00:00:14.670 align:middle line:90%
to them.

00:00:14.670 --> 00:00:17.250 align:middle line:84%
We're going to now
investigate how

00:00:17.250 --> 00:00:20.280 align:middle line:84%
we can interact with those
databases on a website.

00:00:20.280 --> 00:00:24.780 align:middle line:84%
This is separate from when we
saw SQL or MySQL databases that

00:00:24.780 --> 00:00:26.590 align:middle line:90%
were just part of a server.

00:00:26.590 --> 00:00:28.290 align:middle line:90%
Similar interaction.

00:00:28.290 --> 00:00:31.560 align:middle line:84%
But this, we can all do
through the web application

00:00:31.560 --> 00:00:35.910 align:middle line:84%
itself, our command line
not necessarily targeting

00:00:35.910 --> 00:00:36.700 align:middle line:90%
the server.

00:00:36.700 --> 00:00:40.305 align:middle line:84%
It is going to target the
server but in a less direct way.

00:00:40.305 --> 00:00:44.020 align:middle line:84%
And again, this is tied to
the web app portion of this.

00:00:44.020 --> 00:00:47.100 align:middle line:84%
So let's get into the
lab and take a look.

00:00:47.100 --> 00:00:52.680 align:middle line:90%


00:00:52.680 --> 00:00:56.240 align:middle line:84%
First, let's pull
up our IP address.

00:00:56.240 --> 00:00:59.930 align:middle line:84%
I do this because it changes
with each lab iteration.

00:00:59.930 --> 00:01:05.630 align:middle line:90%


00:01:05.630 --> 00:01:08.300 align:middle line:84%
With this lab
environment, every time

00:01:08.300 --> 00:01:13.100 align:middle line:84%
you create a new lab
environment, this,

00:01:13.100 --> 00:01:15.800 align:middle line:84%
your network is actually
going to change,

00:01:15.800 --> 00:01:18.770 align:middle line:90%
your network in subnet.

00:01:18.770 --> 00:01:20.480 align:middle line:84%
But it's always
going to be a .2.

00:01:20.480 --> 00:01:22.240 align:middle line:90%
That's you.

00:01:22.240 --> 00:01:24.320 align:middle line:90%
And the .3, that's the target.

00:01:24.320 --> 00:01:31.720 align:middle line:90%
And .1 going to be the router.

00:01:31.720 --> 00:01:37.570 align:middle line:84%
So you see, it's got port
80 open and 3306 for mysql.

00:01:37.570 --> 00:01:40.338 align:middle line:90%
We could dive deeper into that.

00:01:40.338 --> 00:01:41.380 align:middle line:90%
I don't think it's MySQL.

00:01:41.380 --> 00:01:44.300 align:middle line:90%
I think it's SQL on Ubuntu.

00:01:44.300 --> 00:01:44.800 align:middle line:90%
It's fine.

00:01:44.800 --> 00:01:51.860 align:middle line:90%


00:01:51.860 --> 00:01:54.140 align:middle line:90%
And we've got bWAPP up again.

00:01:54.140 --> 00:01:56.120 align:middle line:90%
bWAPP is great.

00:01:56.120 --> 00:01:59.510 align:middle line:84%
We're going to do a
combination of things.

00:01:59.510 --> 00:02:04.030 align:middle line:90%
We're going to use the terminal.

00:02:04.030 --> 00:02:06.840 align:middle line:90%
We're going to use Burp Suite.

00:02:06.840 --> 00:02:09.000 align:middle line:90%
Turn that on and open it up.

00:02:09.000 --> 00:02:16.640 align:middle line:84%
And we will use sqlmap
in our command line.

00:02:16.640 --> 00:02:23.205 align:middle line:84%
So let's get Burp started,
B-U-R-P. Get it running.

00:02:23.205 --> 00:02:25.860 align:middle line:90%


00:02:25.860 --> 00:02:27.420 align:middle line:90%
Next, start Burp.

00:02:27.420 --> 00:02:31.380 align:middle line:90%


00:02:31.380 --> 00:02:33.600 align:middle line:90%
Hit OK.

00:02:33.600 --> 00:02:36.540 align:middle line:90%
And we're in.

00:02:36.540 --> 00:02:40.050 align:middle line:84%
I'm going to log
in with b and bug.

00:02:40.050 --> 00:02:41.115 align:middle line:90%
Intercept is on.

00:02:41.115 --> 00:02:46.110 align:middle line:90%


00:02:46.110 --> 00:02:48.410 align:middle line:84%
And the reason we're doing
this is because we're

00:02:48.410 --> 00:02:53.070 align:middle line:90%
going to get this cookie.

00:02:53.070 --> 00:02:55.260 align:middle line:90%
We want this cookie.

00:02:55.260 --> 00:02:56.190 align:middle line:90%
We're going to log in.

00:02:56.190 --> 00:02:59.160 align:middle line:84%
And our interaction
is going to be

00:02:59.160 --> 00:03:01.005 align:middle line:90%
all based off of this cookie.

00:03:01.005 --> 00:03:07.820 align:middle line:90%


00:03:07.820 --> 00:03:09.930 align:middle line:90%
So we'll pass it through.

00:03:09.930 --> 00:03:10.850 align:middle line:90%
Will this one go?

00:03:10.850 --> 00:03:13.220 align:middle line:84%
Actually, I'll turn off
intercept for a second.

00:03:13.220 --> 00:03:14.390 align:middle line:90%
We are in.

00:03:14.390 --> 00:03:19.130 align:middle line:84%
We want to go to
the SQL Injection.

00:03:19.130 --> 00:03:21.770 align:middle line:90%


00:03:21.770 --> 00:03:24.680 align:middle line:90%
GET/Search.

00:03:24.680 --> 00:03:25.220 align:middle line:90%
Hit Hack.

00:03:25.220 --> 00:03:28.061 align:middle line:90%
It brings us to that page.

00:03:28.061 --> 00:03:30.470 align:middle line:90%
And I'll turn Intercept on.

00:03:30.470 --> 00:03:31.830 align:middle line:90%
Refresh this page.

00:03:31.830 --> 00:03:34.070 align:middle line:90%
And now we catch it.

00:03:34.070 --> 00:03:36.170 align:middle line:90%
So we have a PHPSESSID.

00:03:36.170 --> 00:03:39.950 align:middle line:84%
That is based off
of being logged in.

00:03:39.950 --> 00:03:43.670 align:middle line:90%
We logged in as b.

00:03:43.670 --> 00:03:45.410 align:middle line:84%
That's why we have
access to everything.

00:03:45.410 --> 00:03:47.900 align:middle line:84%
And as an authenticated
user, now we're

00:03:47.900 --> 00:03:51.770 align:middle line:84%
going to have access to the
SQL database through this page

00:03:51.770 --> 00:03:54.660 align:middle line:90%
right here.

00:03:54.660 --> 00:03:56.450 align:middle line:84%
So we could type
anything in here.

00:03:56.450 --> 00:04:01.610 align:middle line:84%
I'm going to type in joe
because I know it's on the list

00:04:01.610 --> 00:04:03.380 align:middle line:90%
from playing around in here.

00:04:03.380 --> 00:04:04.520 align:middle line:90%
We caught it.

00:04:04.520 --> 00:04:10.570 align:middle line:84%
We asked for-- or rather,
I'll send that through.

00:04:10.570 --> 00:04:16.070 align:middle line:90%


00:04:16.070 --> 00:04:17.089 align:middle line:90%
Joe.

00:04:17.089 --> 00:04:18.980 align:middle line:90%
That was caught.

00:04:18.980 --> 00:04:25.010 align:middle line:84%
The way it sends it, it's
got variables in the URL.

00:04:25.010 --> 00:04:27.440 align:middle line:84%
And we can see that
up here, title=joe.

00:04:27.440 --> 00:04:29.540 align:middle line:90%
action=search.

00:04:29.540 --> 00:04:35.570 align:middle line:84%
These variables are what
drives the SQL database.

00:04:35.570 --> 00:04:38.353 align:middle line:84%
And that is what
we will mess with.

00:04:38.353 --> 00:04:39.395 align:middle line:90%
We'll mess with that URL.

00:04:39.395 --> 00:04:43.430 align:middle line:90%


00:04:43.430 --> 00:04:47.270 align:middle line:84%
So knowing that we have it all
set up and that it captured,

00:04:47.270 --> 00:04:55.490 align:middle line:84%
we're going to take
this all over to sqlmap.

00:04:55.490 --> 00:04:58.040 align:middle line:90%
Or sqlmap.

00:04:58.040 --> 00:04:59.780 align:middle line:90%
Potato, potato.

00:04:59.780 --> 00:05:02.820 align:middle line:84%
Either way, someone's going to
be upset with how I said it.

00:05:02.820 --> 00:05:05.300 align:middle line:90%
sqlmap is a neat tool.

00:05:05.300 --> 00:05:06.620 align:middle line:90%
It's easier to say sqlmap.

00:05:06.620 --> 00:05:09.170 align:middle line:90%
So I'll just say it that way.

00:05:09.170 --> 00:05:10.910 align:middle line:90%
We need to give it a URL.

00:05:10.910 --> 00:05:15.635 align:middle line:90%
So http://.

00:05:15.635 --> 00:05:20.690 align:middle line:90%
And .3/.

00:05:20.690 --> 00:05:37.960 align:middle line:84%
And we will just pass, oops,
all of that into there.

00:05:37.960 --> 00:05:42.424 align:middle line:90%


00:05:42.424 --> 00:05:45.220 align:middle line:84%
title equals hello,
or joe in this case.

00:05:45.220 --> 00:05:47.290 align:middle line:90%
And action=search.

00:05:47.290 --> 00:05:52.120 align:middle line:84%
And for the cookie,
we need that cookie.

00:05:52.120 --> 00:05:56.140 align:middle line:84%
We'll grab it right out of here,
PHPSESSID all the way through

00:05:56.140 --> 00:05:57.730 align:middle line:90%
security_level=0.

00:05:57.730 --> 00:06:01.050 align:middle line:90%


00:06:01.050 --> 00:06:04.710 align:middle line:84%
There is so much wrong
with this web app.

00:06:04.710 --> 00:06:07.600 align:middle line:90%
But that's on purpose.

00:06:07.600 --> 00:06:14.760 align:middle line:84%
And then, we're going to target
title right there, title.

00:06:14.760 --> 00:06:15.510 align:middle line:90%
Boom.

00:06:15.510 --> 00:06:17.820 align:middle line:84%
So based on what
is in the title,

00:06:17.820 --> 00:06:20.295 align:middle line:84%
sqlmap is going to
do some neat stuff.

00:06:20.295 --> 00:06:21.120 align:middle line:90%
I'll have it run.

00:06:21.120 --> 00:06:26.170 align:middle line:90%


00:06:26.170 --> 00:06:29.710 align:middle line:84%
It made a connection doing
heuristic based off of title.

00:06:29.710 --> 00:06:31.690 align:middle line:90%
It might be injectable.

00:06:31.690 --> 00:06:34.840 align:middle line:84%
Possible database
management system is MySQL.

00:06:34.840 --> 00:06:39.451 align:middle line:90%


00:06:39.451 --> 00:06:41.620 align:middle line:90%
It sounds about right.

00:06:41.620 --> 00:06:43.600 align:middle line:84%
So it's testing
for SQL injection

00:06:43.600 --> 00:06:45.850 align:middle line:90%
on the GET parameter title.

00:06:45.850 --> 00:06:49.450 align:middle line:84%
And it should find it
because it's supposed to.

00:06:49.450 --> 00:06:52.120 align:middle line:90%


00:06:52.120 --> 00:06:52.620 align:middle line:90%
All right.

00:06:52.620 --> 00:06:55.750 align:middle line:90%
We have our results back.

00:06:55.750 --> 00:06:59.760 align:middle line:84%
So it looks like the
parameter title is vulnerable.

00:06:59.760 --> 00:07:02.385 align:middle line:84%
And it gave us some
things to try out.

00:07:02.385 --> 00:07:05.400 align:middle line:90%


00:07:05.400 --> 00:07:08.130 align:middle line:90%
There is these payloads here.

00:07:08.130 --> 00:07:09.580 align:middle line:90%
We do OR NOT.

00:07:09.580 --> 00:07:11.130 align:middle line:90%
And here's this code.

00:07:11.130 --> 00:07:15.660 align:middle line:84%
Or we could input
this longer one

00:07:15.660 --> 00:07:17.760 align:middle line:90%
and see if that does something.

00:07:17.760 --> 00:07:20.500 align:middle line:90%
Well, let's play around with it.

00:07:20.500 --> 00:07:22.605 align:middle line:84%
So what we'll do, I'm
going to copy this.

00:07:22.605 --> 00:07:26.570 align:middle line:90%


00:07:26.570 --> 00:07:29.780 align:middle line:84%
Go into Burp Suite, where
we've captured this.

00:07:29.780 --> 00:07:30.680 align:middle line:90%
Go to Actions.

00:07:30.680 --> 00:07:32.630 align:middle line:90%
And we'll Send it to Repeater.

00:07:32.630 --> 00:07:35.630 align:middle line:84%
Repeater is going to let
us take this GET request,

00:07:35.630 --> 00:07:38.790 align:middle line:90%
change some things on it.

00:07:38.790 --> 00:07:42.375 align:middle line:90%
And let's see what happens.

00:07:42.375 --> 00:07:44.948 align:middle line:90%


00:07:44.948 --> 00:07:45.490 align:middle line:90%
So if we do--

00:07:45.490 --> 00:07:48.880 align:middle line:90%


00:07:48.880 --> 00:07:52.710 align:middle line:84%
let's just check, make
sure that we had it right.

00:07:52.710 --> 00:07:53.590 align:middle line:90%
php?title=.

00:07:53.590 --> 00:07:57.250 align:middle line:90%


00:07:57.250 --> 00:08:08.770 align:middle line:84%
And after joe, we're going to
throw in this backtick OR NOT.

00:08:08.770 --> 00:08:13.420 align:middle line:90%
One-- 2377=2377.

00:08:13.420 --> 00:08:16.090 align:middle line:90%
And then, action=search.

00:08:16.090 --> 00:08:18.550 align:middle line:84%
So we'll throw all that in
there and see what that does.

00:08:18.550 --> 00:08:20.020 align:middle line:90%
We'll send that.

00:08:20.020 --> 00:08:32.559 align:middle line:90%
And we get back something.

00:08:32.559 --> 00:08:34.030 align:middle line:90%
Search for movie.

00:08:34.030 --> 00:08:35.919 align:middle line:90%
We should see results.

00:08:35.919 --> 00:08:37.600 align:middle line:90%
There it is.

00:08:37.600 --> 00:08:40.600 align:middle line:84%
Error, you have an error
in your SQL syntax.

00:08:40.600 --> 00:08:42.610 align:middle line:84%
Check the manual
that corresponds.

00:08:42.610 --> 00:08:43.809 align:middle line:90%
Bummer.

00:08:43.809 --> 00:08:48.730 align:middle line:84%
So that, in the end, errored
out, because the way the page

00:08:48.730 --> 00:08:51.950 align:middle line:84%
works, it presents it
down here at the bottom

00:08:51.950 --> 00:08:54.340 align:middle line:90%
when it runs something.

00:08:54.340 --> 00:08:56.030 align:middle line:90%
That's what it's showing here.

00:08:56.030 --> 00:08:58.680 align:middle line:84%
So in this attempt,
it didn't work.

00:08:58.680 --> 00:09:01.570 align:middle line:90%
Well, let's try this other one.

00:09:01.570 --> 00:09:03.580 align:middle line:90%
This is really long.

00:09:03.580 --> 00:09:07.240 align:middle line:90%


00:09:07.240 --> 00:09:08.710 align:middle line:90%
Let's see if it works.

00:09:08.710 --> 00:09:10.630 align:middle line:90%
We're still in the Repeater tab.

00:09:10.630 --> 00:09:16.730 align:middle line:84%
So I can just replace
all of that title all

00:09:16.730 --> 00:09:18.890 align:middle line:90%
the way through search.

00:09:18.890 --> 00:09:23.535 align:middle line:84%
And we'll see if
that does anything.

00:09:23.535 --> 00:09:24.910 align:middle line:84%
Scroll all the
way to the bottom.

00:09:24.910 --> 00:09:27.780 align:middle line:90%
And we still get an error.

00:09:27.780 --> 00:09:32.770 align:middle line:90%
Well, let's see why these ones.

00:09:32.770 --> 00:09:34.700 align:middle line:90%
Place this one.

00:09:34.700 --> 00:09:36.520 align:middle line:90%
See if any of them work.

00:09:36.520 --> 00:09:39.130 align:middle line:84%
Just to get a sqlmap, I found
something that might work.

00:09:39.130 --> 00:09:41.500 align:middle line:90%
It doesn't mean it really will.

00:09:41.500 --> 00:09:46.330 align:middle line:90%


00:09:46.330 --> 00:09:48.070 align:middle line:90%
It is a tool.

00:09:48.070 --> 00:09:53.120 align:middle line:84%
And sometimes,
you get something.

00:09:53.120 --> 00:09:54.110 align:middle line:90%
Sometimes, you don't.

00:09:54.110 --> 00:09:58.760 align:middle line:84%
If we did have SQL injection
here, what we might see

00:09:58.760 --> 00:10:05.008 align:middle line:84%
is the whole database
spitting out.

00:10:05.008 --> 00:10:07.125 align:middle line:84%
It doesn't look like it's
going to do anything.

00:10:07.125 --> 00:10:09.735 align:middle line:90%


00:10:09.735 --> 00:10:10.735 align:middle line:90%
This one's pretty crazy.

00:10:10.735 --> 00:10:15.770 align:middle line:90%


00:10:15.770 --> 00:10:17.150 align:middle line:90%
Well, why not?

00:10:17.150 --> 00:10:19.310 align:middle line:90%
Why not try it?

00:10:19.310 --> 00:10:21.305 align:middle line:90%
Replace title through search.

00:10:21.305 --> 00:10:24.550 align:middle line:90%


00:10:24.550 --> 00:10:27.530 align:middle line:84%
And you can send any
information in this header.

00:10:27.530 --> 00:10:32.500 align:middle line:84%
Whether it works or
not really depends

00:10:32.500 --> 00:10:34.600 align:middle line:84%
on the database
on the other end.

00:10:34.600 --> 00:10:35.140 align:middle line:90%
Bummer.

00:10:35.140 --> 00:10:37.090 align:middle line:90%
Another error.

00:10:37.090 --> 00:10:37.880 align:middle line:90%
That's fine.

00:10:37.880 --> 00:10:38.650 align:middle line:90%
Let's move on.

00:10:38.650 --> 00:10:41.630 align:middle line:90%


00:10:41.630 --> 00:10:43.310 align:middle line:90%
That errored out a few times.

00:10:43.310 --> 00:10:48.353 align:middle line:84%
Let's try something
just a little different.

00:10:48.353 --> 00:10:55.410 align:middle line:90%


00:10:55.410 --> 00:10:59.550 align:middle line:84%
Now that we have access,
we know that sqlmap was

00:10:59.550 --> 00:11:00.780 align:middle line:90%
able to try these things out.

00:11:00.780 --> 00:11:09.860 align:middle line:84%
It tested out a mess of them
and came up with some feedback.

00:11:09.860 --> 00:11:13.640 align:middle line:84%
So we'll keep that,
everything the same.

00:11:13.640 --> 00:11:18.980 align:middle line:84%
Except instead of finding
payloads for title,

00:11:18.980 --> 00:11:23.630 align:middle line:84%
we want it to check
databases and/or--

00:11:23.630 --> 00:11:26.180 align:middle line:90%
yeah, databases.

00:11:26.180 --> 00:11:29.870 align:middle line:90%
So we'll do a --dbs.

00:11:29.870 --> 00:11:35.780 align:middle line:84%
And it'll try to do some SQL
injection to turn back what all

00:11:35.780 --> 00:11:40.700 align:middle line:90%
the databases are accessible.

00:11:40.700 --> 00:11:41.960 align:middle line:90%
Wow, that was fast.

00:11:41.960 --> 00:11:43.910 align:middle line:90%
We've got four databases.

00:11:43.910 --> 00:11:46.580 align:middle line:84%
There's bWAPP,
information_schema, mysql,

00:11:46.580 --> 00:11:49.970 align:middle line:90%
and performance_schema.

00:11:49.970 --> 00:11:52.260 align:middle line:84%
That was a nice
little quick thing.

00:11:52.260 --> 00:11:57.200 align:middle line:84%
Let's see what
tables are in bWAPP.

00:11:57.200 --> 00:12:01.280 align:middle line:90%
So -D. Now we'll look at bWAPP.

00:12:01.280 --> 00:12:03.170 align:middle line:90%
And tell me the tables.

00:12:03.170 --> 00:12:05.960 align:middle line:90%


00:12:05.960 --> 00:12:06.780 align:middle line:90%
Pretty quick.

00:12:06.780 --> 00:12:10.670 align:middle line:84%
We have these tables, blog,
heroes, movies, users,

00:12:10.670 --> 00:12:12.410 align:middle line:90%
visitors.

00:12:12.410 --> 00:12:15.080 align:middle line:84%
Now this is where you've got to
start understanding databases.

00:12:15.080 --> 00:12:17.480 align:middle line:84%
And we haven't taught
anything on databases.

00:12:17.480 --> 00:12:22.640 align:middle line:84%
We haven't taught anything
on SQL specific to how

00:12:22.640 --> 00:12:24.140 align:middle line:90%
the database works.

00:12:24.140 --> 00:12:26.480 align:middle line:90%
But they're very common.

00:12:26.480 --> 00:12:28.310 align:middle line:90%
Databases hold information.

00:12:28.310 --> 00:12:31.610 align:middle line:84%
Hopefully, someone's worked
with an Excel spreadsheet

00:12:31.610 --> 00:12:37.322 align:middle line:84%
or just columns of data where
you have different rows.

00:12:37.322 --> 00:12:38.780 align:middle line:84%
And each row has
different columns.

00:12:38.780 --> 00:12:42.800 align:middle line:90%


00:12:42.800 --> 00:12:48.920 align:middle line:84%
Well, those rows and columns
are stored in tables.

00:12:48.920 --> 00:12:51.530 align:middle line:84%
And the tables are
stored in databases.

00:12:51.530 --> 00:12:54.180 align:middle line:90%
Boom, there it is.

00:12:54.180 --> 00:12:57.770 align:middle line:90%
So we've got users.

00:12:57.770 --> 00:13:01.100 align:middle line:90%
Let's dive in even more.

00:13:01.100 --> 00:13:05.600 align:middle line:84%
So now that we've identified
a table, we use capital T.

00:13:05.600 --> 00:13:07.580 align:middle line:90%
And we want to look at users.

00:13:07.580 --> 00:13:09.500 align:middle line:84%
And let's see what
all the columns are.

00:13:09.500 --> 00:13:13.200 align:middle line:90%


00:13:13.200 --> 00:13:15.720 align:middle line:90%
Boom, find out all the columns.

00:13:15.720 --> 00:13:18.015 align:middle line:84%
There's an admin
column, password column.

00:13:18.015 --> 00:13:26.362 align:middle line:84%
Ooh, and you can see what type
of information they could hold.

00:13:26.362 --> 00:13:27.195 align:middle line:90%
That's quite useful.

00:13:27.195 --> 00:13:30.160 align:middle line:90%


00:13:30.160 --> 00:13:31.870 align:middle line:90%
Let's dump this whole table.

00:13:31.870 --> 00:13:32.380 align:middle line:90%
Why not?

00:13:32.380 --> 00:13:34.920 align:middle line:90%


00:13:34.920 --> 00:13:42.930 align:middle line:84%
So we know that we
have users as a table.

00:13:42.930 --> 00:13:44.790 align:middle line:90%
Capital C for columns.

00:13:44.790 --> 00:13:53.420 align:middle line:84%
We'll do admin, and
password, and email.

00:13:53.420 --> 00:13:54.950 align:middle line:90%
Let's get all those.

00:13:54.950 --> 00:13:55.765 align:middle line:90%
And then --dump.

00:13:55.765 --> 00:13:58.477 align:middle line:90%


00:13:58.477 --> 00:13:59.810 align:middle line:90%
Now it's going to read all that.

00:13:59.810 --> 00:14:07.520 align:middle line:90%
And sure.

00:14:07.520 --> 00:14:13.010 align:middle line:90%


00:14:13.010 --> 00:14:13.510 align:middle line:90%
No.

00:14:13.510 --> 00:14:20.410 align:middle line:90%


00:14:20.410 --> 00:14:21.512 align:middle line:90%
[INAUDIBLE]

00:14:21.512 --> 00:14:28.730 align:middle line:90%


00:14:28.730 --> 00:14:30.870 align:middle line:90%
Hmm, I stopped it.

00:14:30.870 --> 00:14:33.960 align:middle line:90%
But it came up with some hashes.

00:14:33.960 --> 00:14:38.450 align:middle line:90%


00:14:38.450 --> 00:14:39.650 align:middle line:90%
Yeah, that works.

00:14:39.650 --> 00:14:40.370 align:middle line:90%
That's it.

00:14:40.370 --> 00:14:41.630 align:middle line:90%
That's what I had.

00:14:41.630 --> 00:14:44.540 align:middle line:84%
So it's got these
hashed passwords.

00:14:44.540 --> 00:14:46.100 align:middle line:84%
It came up with the
hashed passwords.

00:14:46.100 --> 00:14:48.200 align:middle line:84%
I didn't read what
it was asking.

00:14:48.200 --> 00:14:49.910 align:middle line:90%
It noticed that they're hashes.

00:14:49.910 --> 00:14:52.170 align:middle line:84%
And it said, hey, do you
want to crack the hashes?

00:14:52.170 --> 00:14:55.400 align:middle line:84%
And I didn't give it a
dictionary to crack with.

00:14:55.400 --> 00:14:57.320 align:middle line:84%
So it used the
default dictionary.

00:14:57.320 --> 00:14:59.810 align:middle line:90%
It went very quickly.

00:14:59.810 --> 00:15:01.275 align:middle line:90%
I had boarded it.

00:15:01.275 --> 00:15:03.650 align:middle line:84%
So it didn't actually find
the passwords from the hashes.

00:15:03.650 --> 00:15:10.310 align:middle line:84%
But you could take this
offline through John or Hashcat

00:15:10.310 --> 00:15:11.510 align:middle line:90%
and actually crack it.

00:15:11.510 --> 00:15:14.720 align:middle line:90%


00:15:14.720 --> 00:15:15.410 align:middle line:90%
All right.

00:15:15.410 --> 00:15:17.840 align:middle line:84%
Let's change it up
just a little bit.

00:15:17.840 --> 00:15:21.998 align:middle line:90%


00:15:21.998 --> 00:15:24.360 align:middle line:90%
I want intercept to work.

00:15:24.360 --> 00:15:30.555 align:middle line:84%
But we'll go to the SQL
Injection with a POST.

00:15:30.555 --> 00:15:35.200 align:middle line:90%


00:15:35.200 --> 00:15:37.810 align:middle line:84%
And let's forward it on so
we see what that looks like.

00:15:37.810 --> 00:15:43.946 align:middle line:90%


00:15:43.946 --> 00:15:47.300 align:middle line:84%
Did it not go where
I wanted it to go?

00:15:47.300 --> 00:15:48.020 align:middle line:90%
POST/Search.

00:15:48.020 --> 00:15:55.980 align:middle line:90%


00:15:55.980 --> 00:15:59.220 align:middle line:90%
Oh, I didn't hit Hack.

00:15:59.220 --> 00:15:59.760 align:middle line:90%
Hack.

00:15:59.760 --> 00:16:00.600 align:middle line:90%
There you go.

00:16:00.600 --> 00:16:03.820 align:middle line:90%
Now it's on POST/Search.

00:16:03.820 --> 00:16:04.320 align:middle line:90%
Fun.

00:16:04.320 --> 00:16:07.490 align:middle line:90%


00:16:07.490 --> 00:16:10.310 align:middle line:84%
And here, I turned intercept
back on now that I've got it.

00:16:10.310 --> 00:16:11.580 align:middle line:90%
[LAUGHTER]

00:16:11.580 --> 00:16:14.270 align:middle line:90%
Search the right place, sqli_6.

00:16:14.270 --> 00:16:18.530 align:middle line:84%
And in this one,
it looks like it's

00:16:18.530 --> 00:16:24.840 align:middle line:84%
going to send it in the
POST data, in the form data.

00:16:24.840 --> 00:16:29.030 align:middle line:90%
So let's not intercept that.

00:16:29.030 --> 00:16:32.810 align:middle line:90%
Let's intercept if I pass hello.

00:16:32.810 --> 00:16:33.800 align:middle line:90%
There it is.

00:16:33.800 --> 00:16:36.200 align:middle line:90%
It passes it in this form data.

00:16:36.200 --> 00:16:37.550 align:middle line:90%
Forget requests.

00:16:37.550 --> 00:16:42.380 align:middle line:84%
You pass variables
in the URL, usually.

00:16:42.380 --> 00:16:44.930 align:middle line:84%
For a form or for a
POST, you're going

00:16:44.930 --> 00:16:52.440 align:middle line:84%
to pass it in the body
of your POST request.

00:16:52.440 --> 00:16:56.280 align:middle line:84%
So now, we're going to do
very much similar stuff.

00:16:56.280 --> 00:17:05.930 align:middle line:84%
What we want is to copy
all of this to a file.

00:17:05.930 --> 00:17:08.440 align:middle line:90%
So Action.

00:17:08.440 --> 00:17:13.400 align:middle line:90%
And then, Copy to File.

00:17:13.400 --> 00:17:15.109 align:middle line:90%
And in root's fine.

00:17:15.109 --> 00:17:16.969 align:middle line:84%
We'll just call
this the request.

00:17:16.969 --> 00:17:21.290 align:middle line:90%


00:17:21.290 --> 00:17:24.244 align:middle line:84%
And now, we've got that
request, the POST request.

00:17:24.244 --> 00:17:27.307 align:middle line:90%


00:17:27.307 --> 00:17:28.975 align:middle line:90%
Let's see here.

00:17:28.975 --> 00:17:29.745 align:middle line:90%
We've got request.

00:17:29.745 --> 00:17:32.810 align:middle line:90%


00:17:32.810 --> 00:17:37.300 align:middle line:84%
And it did not save everything
that it was supposed to save.

00:17:37.300 --> 00:17:39.400 align:middle line:84%
It only saved what
I highlighted.

00:17:39.400 --> 00:17:40.460 align:middle line:90%
Be careful.

00:17:40.460 --> 00:17:42.190 align:middle line:90%
That's why we check things.

00:17:42.190 --> 00:17:44.890 align:middle line:90%
Copy it all.

00:17:44.890 --> 00:17:45.610 align:middle line:90%
Save it.

00:17:45.610 --> 00:17:46.770 align:middle line:90%
Override it, Yes.

00:17:46.770 --> 00:17:51.370 align:middle line:90%


00:17:51.370 --> 00:17:52.360 align:middle line:90%
There we go.

00:17:52.360 --> 00:17:54.500 align:middle line:90%
Now it's got everything.

00:17:54.500 --> 00:18:00.640 align:middle line:84%
Request has the
full POST, including

00:18:00.640 --> 00:18:02.380 align:middle line:90%
the variables at the end.

00:18:02.380 --> 00:18:06.110 align:middle line:90%
There is no new line at the end.

00:18:06.110 --> 00:18:10.740 align:middle line:84%
So yay Linux, it didn't even
put the new line when it catted.

00:18:10.740 --> 00:18:13.155 align:middle line:90%


00:18:13.155 --> 00:18:13.780 align:middle line:90%
That will work.

00:18:13.780 --> 00:18:15.680 align:middle line:90%
We can work with that.

00:18:15.680 --> 00:18:20.080 align:middle line:84%
So it doesn't look so
freaky to you to do that.

00:18:20.080 --> 00:18:20.580 align:middle line:90%
All right.

00:18:20.580 --> 00:18:23.530 align:middle line:84%
Now we're going to
use sqlmap on this.

00:18:23.530 --> 00:18:26.880 align:middle line:90%
So sqlmap.

00:18:26.880 --> 00:18:31.470 align:middle line:90%
And we will use the request.

00:18:31.470 --> 00:18:34.530 align:middle line:84%
And we'll look at
the payload of title

00:18:34.530 --> 00:18:36.950 align:middle line:90%
because that's still there.

00:18:36.950 --> 00:18:43.230 align:middle line:90%


00:18:43.230 --> 00:18:43.980 align:middle line:90%
Go the defaults.

00:18:43.980 --> 00:18:50.780 align:middle line:90%


00:18:50.780 --> 00:18:51.380 align:middle line:90%
It's testing.

00:18:51.380 --> 00:18:55.877 align:middle line:90%


00:18:55.877 --> 00:18:56.660 align:middle line:90%
[INAUDIBLE]

00:18:56.660 --> 00:18:58.950 align:middle line:90%
We've got new payloads back.

00:18:58.950 --> 00:19:00.330 align:middle line:90%
So we could try these ones.

00:19:00.330 --> 00:19:01.670 align:middle line:90%
Let's give them a try.

00:19:01.670 --> 00:19:04.730 align:middle line:90%


00:19:04.730 --> 00:19:07.120 align:middle line:84%
Let's Send this
over to Repeater.

00:19:07.120 --> 00:19:08.350 align:middle line:90%
Go to Repeater.

00:19:08.350 --> 00:19:10.930 align:middle line:90%
What does it normally look like?

00:19:10.930 --> 00:19:16.770 align:middle line:84%
It would normally
look like all this.

00:19:16.770 --> 00:19:25.460 align:middle line:90%


00:19:25.460 --> 00:19:28.591 align:middle line:90%
So nothing terribly crazy.

00:19:28.591 --> 00:19:30.213 align:middle line:90%
Let's write hello.

00:19:30.213 --> 00:19:32.170 align:middle line:90%
Did we put it in here?

00:19:32.170 --> 00:19:37.970 align:middle line:84%
Nope, because it didn't
find anything with a hello.

00:19:37.970 --> 00:19:41.420 align:middle line:90%
Let's look at our payloads.

00:19:41.420 --> 00:19:51.760 align:middle line:84%
If we replace our variables
with these payloads

00:19:51.760 --> 00:19:53.680 align:middle line:84%
and then send that,
what do we get?

00:19:53.680 --> 00:20:23.380 align:middle line:90%


00:20:23.380 --> 00:20:32.400 align:middle line:84%
It looks like-- yeah, it
just stops right in here.

00:20:32.400 --> 00:20:36.680 align:middle line:90%
It looks like we got an error.

00:20:36.680 --> 00:20:38.450 align:middle line:84%
That's where it
should have shown up.

00:20:38.450 --> 00:20:44.030 align:middle line:90%


00:20:44.030 --> 00:20:46.690 align:middle line:90%
But it didn't.

00:20:46.690 --> 00:20:49.510 align:middle line:84%
And so we've got
this gobbledygook.

00:20:49.510 --> 00:20:50.710 align:middle line:90%
Well, let's try another one.

00:20:50.710 --> 00:21:10.450 align:middle line:90%


00:21:10.450 --> 00:21:12.010 align:middle line:90%
Ooh, maybe this one hit.

00:21:12.010 --> 00:21:15.030 align:middle line:90%


00:21:15.030 --> 00:21:16.440 align:middle line:90%
No movies were found.

00:21:16.440 --> 00:21:18.950 align:middle line:90%
Bummer.

00:21:18.950 --> 00:21:19.450 align:middle line:90%
All right.

00:21:19.450 --> 00:21:22.360 align:middle line:90%
So that one didn't work either.

00:21:22.360 --> 00:21:27.290 align:middle line:84%
sqlmap is useful, but
also not always useful.

00:21:27.290 --> 00:21:32.560 align:middle line:90%


00:21:32.560 --> 00:21:42.110 align:middle line:84%
How about-- this
first one did work.

00:21:42.110 --> 00:21:47.930 align:middle line:90%


00:21:47.930 --> 00:21:54.300 align:middle line:84%
What it did is it threw
in this hash information.

00:21:54.300 --> 00:22:03.800 align:middle line:90%


00:22:03.800 --> 00:22:15.800 align:middle line:84%
So let's use that
again just to show.

00:22:15.800 --> 00:22:23.650 align:middle line:90%


00:22:23.650 --> 00:22:25.585 align:middle line:84%
BIGINT value is
out of the range.

00:22:25.585 --> 00:22:30.720 align:middle line:90%


00:22:30.720 --> 00:22:39.085 align:middle line:84%
So how about instead of
this, we send version?

00:22:39.085 --> 00:22:48.180 align:middle line:90%


00:22:48.180 --> 00:22:51.800 align:middle line:84%
Oh, it didn't like
that one either.

00:22:51.800 --> 00:22:52.640 align:middle line:90%
Well, how annoying.

00:22:52.640 --> 00:23:08.830 align:middle line:90%


00:23:08.830 --> 00:23:09.580 align:middle line:90%
Oh, no.

00:23:09.580 --> 00:23:11.050 align:middle line:90%
It is in there.

00:23:11.050 --> 00:23:13.690 align:middle line:90%
It found the version.

00:23:13.690 --> 00:23:15.830 align:middle line:90%
It's right here.

00:23:15.830 --> 00:23:19.610 align:middle line:90%
It's 5.5.47 on ubuntu.

00:23:19.610 --> 00:23:21.110 align:middle line:90%
Ta da.

00:23:21.110 --> 00:23:24.320 align:middle line:84%
I just wasn't
reading it properly.

00:23:24.320 --> 00:23:27.110 align:middle line:90%
Well, sqlmap can get confusing.

00:23:27.110 --> 00:23:31.880 align:middle line:84%
But with understanding the
tools in sqlmap, and Burp Suite,

00:23:31.880 --> 00:23:34.430 align:middle line:84%
and some of the
others, you can really

00:23:34.430 --> 00:23:38.030 align:middle line:84%
take advantage of
the vulnerabilities

00:23:38.030 --> 00:23:43.280 align:middle line:84%
and some of the access available
to you as a penetration tester.

00:23:43.280 --> 00:23:44.360 align:middle line:90%
There's more tools.

00:23:44.360 --> 00:23:46.470 align:middle line:84%
There's some neat
stuff that can happen.

00:23:46.470 --> 00:23:49.520 align:middle line:84%
This is just starting it
off, showing you a little bit

00:23:49.520 --> 00:23:50.510 align:middle line:90%
of what you can do.

00:23:50.510 --> 00:23:54.480 align:middle line:84%
And we'll dig into more in the
following lessons and labs.

00:23:54.480 --> 00:23:57.500 align:middle line:90%
So hang on for this.

00:23:57.500 --> 00:23:58.000 align:middle line:90%