WEBVTT

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


00:00:09.710 --> 00:00:12.530 align:middle line:84%
In this lesson, we're going
to dig in a little more.

00:00:12.530 --> 00:00:14.270 align:middle line:84%
We looked at a few
different tools

00:00:14.270 --> 00:00:16.190 align:middle line:90%
for enumerating a website.

00:00:16.190 --> 00:00:17.800 align:middle line:90%
Websites are really important.

00:00:17.800 --> 00:00:20.390 align:middle line:84%
You're going to see them,
again, internally or external

00:00:20.390 --> 00:00:22.295 align:middle line:90%
to a network.

00:00:22.295 --> 00:00:28.430 align:middle line:90%


00:00:28.430 --> 00:00:30.140 align:middle line:84%
And we're going to
utilize some Nmap

00:00:30.140 --> 00:00:32.600 align:middle line:90%
scripts to enumerate even more.

00:00:32.600 --> 00:00:36.755 align:middle line:84%
And you've been
given our IP address.

00:00:36.755 --> 00:00:41.430 align:middle line:90%


00:00:41.430 --> 00:00:44.790 align:middle line:84%
I always see the same
results, as in the past.

00:00:44.790 --> 00:00:49.440 align:middle line:84%
But port 80 is open
with HTTP, and that's

00:00:49.440 --> 00:00:54.010 align:middle line:84%
what we care about
most right now.

00:00:54.010 --> 00:00:57.540 align:middle line:90%
I'll run a service scan.

00:00:57.540 --> 00:01:11.630 align:middle line:84%
HTTP is open, so open Firefox,
navigate to the website,

00:01:11.630 --> 00:01:15.310 align:middle line:84%
and we get webgoat.net
on the default, dot aspx.

00:01:15.310 --> 00:01:18.870 align:middle line:90%


00:01:18.870 --> 00:01:25.080 align:middle line:84%
And we're running
Microsoft HTTPAPI httpd

00:01:25.080 --> 00:01:31.170 align:middle line:90%
2.0, which is rather useful.

00:01:31.170 --> 00:01:37.180 align:middle line:84%
But we could run some
further enumeration.

00:01:37.180 --> 00:01:40.720 align:middle line:84%
Let's look at just
port 80, and we'll

00:01:40.720 --> 00:01:44.395 align:middle line:90%
run a script with http-enum.

00:01:44.395 --> 00:01:51.710 align:middle line:90%


00:01:51.710 --> 00:01:55.130 align:middle line:84%
The script is going to
return not just what service

00:01:55.130 --> 00:01:58.940 align:middle line:84%
is running, but also maybe
some directories that

00:01:58.940 --> 00:02:03.170 align:middle line:84%
are very common, similar
to running [INAUDIBLE],,

00:02:03.170 --> 00:02:04.865 align:middle line:90%
but with a very select list.

00:02:04.865 --> 00:02:10.350 align:middle line:90%


00:02:10.350 --> 00:02:12.990 align:middle line:84%
We got our results
back, and you see

00:02:12.990 --> 00:02:15.540 align:middle line:84%
there is a content directory,
a downloads directory,

00:02:15.540 --> 00:02:25.240 align:middle line:84%
and a webdav, all marked
as potentially interesting

00:02:25.240 --> 00:02:25.740 align:middle line:90%
folders.

00:02:25.740 --> 00:02:31.210 align:middle line:90%


00:02:31.210 --> 00:02:33.370 align:middle line:84%
We could navigate
and try to connect

00:02:33.370 --> 00:02:37.300 align:middle line:84%
to them through a browser,
but there's another script

00:02:37.300 --> 00:02:38.260 align:middle line:90%
that we can run.

00:02:38.260 --> 00:02:42.025 align:middle line:84%
This one is going to be
web, or HTTP, headers.

00:02:42.025 --> 00:02:46.410 align:middle line:90%


00:02:46.410 --> 00:02:48.810 align:middle line:84%
We'll let that script
on, along with the skin.

00:02:48.810 --> 00:02:55.590 align:middle line:90%


00:02:55.590 --> 00:03:02.000 align:middle line:84%
And this owner turned
in more information--

00:03:02.000 --> 00:03:07.440 align:middle line:84%
the straightforward
HTTP header information,

00:03:07.440 --> 00:03:14.250 align:middle line:84%
which is where we find out
that it's Microsoft IIS 10.0.

00:03:14.250 --> 00:03:18.150 align:middle line:84%
We can also dig in, and it
shows that cross-site scripting

00:03:18.150 --> 00:03:19.080 align:middle line:90%
protection is off.

00:03:19.080 --> 00:03:24.300 align:middle line:90%


00:03:24.300 --> 00:03:25.670 align:middle line:90%
X-Powered by ASP.NET.

00:03:25.670 --> 00:03:29.440 align:middle line:90%


00:03:29.440 --> 00:03:32.310 align:middle line:84%
So it's potentially
useful for us.

00:03:32.310 --> 00:03:35.203 align:middle line:84%
All of this, we would
want to save in our notes

00:03:35.203 --> 00:03:36.120 align:middle line:90%
to come back to later.

00:03:36.120 --> 00:03:41.860 align:middle line:90%


00:03:41.860 --> 00:03:48.300 align:middle line:84%
Another thing that's useful
to look at is methods,

00:03:48.300 --> 00:03:52.740 align:middle line:90%
and we'll pass arguments--

00:03:52.740 --> 00:03:56.230 align:middle line:90%


00:03:56.230 --> 00:03:57.480 align:middle line:90%
http-methods.url.

00:03:57.480 --> 00:04:04.780 align:middle line:90%


00:04:04.780 --> 00:04:09.490 align:middle line:84%
We're going to dig
into this web.dev

00:04:09.490 --> 00:04:12.160 align:middle line:84%
and see if there's anything
we can do in there.

00:04:12.160 --> 00:04:25.955 align:middle line:90%


00:04:25.955 --> 00:04:29.230 align:middle line:84%
And we find out the
supported methods,

00:04:29.230 --> 00:04:32.185 align:middle line:84%
options trace, get,
get being very common,

00:04:32.185 --> 00:04:35.200 align:middle line:84%
it's what we're most
used to, or post.

00:04:35.200 --> 00:04:45.730 align:middle line:84%
But websites are just APIs, and
you've got all these methods.

00:04:45.730 --> 00:04:49.540 align:middle line:84%
Some of these could
be quite useful,

00:04:49.540 --> 00:04:52.610 align:middle line:84%
but we won't dig
into why just yet.

00:04:52.610 --> 00:04:55.660 align:middle line:84%
We'll save that for
an HTTP section.

00:04:55.660 --> 00:04:57.580 align:middle line:84%
Right now, we're
just enumerating.

00:04:57.580 --> 00:05:00.970 align:middle line:84%
So we tested web.dav, came up
with these potentially risky

00:05:00.970 --> 00:05:01.900 align:middle line:90%
ones.

00:05:01.900 --> 00:05:04.180 align:middle line:84%
We would want to write
that down in our notes,

00:05:04.180 --> 00:05:08.470 align:middle line:84%
maybe check the other
directories that we found.

00:05:08.470 --> 00:05:12.330 align:middle line:90%


00:05:12.330 --> 00:05:16.810 align:middle line:84%
What's really helpful--
we found a webdav.

00:05:16.810 --> 00:05:25.990 align:middle line:84%
Well, there's an
HTTP webdav scan,

00:05:25.990 --> 00:05:37.140 align:middle line:84%
and we'll pass the
same URL, and this

00:05:37.140 --> 00:05:45.390 align:middle line:84%
will help identify webdav
installations utilizing options

00:05:45.390 --> 00:05:46.395 align:middle line:90%
and prop find methods.

00:05:46.395 --> 00:05:53.710 align:middle line:90%


00:05:53.710 --> 00:05:58.610 align:middle line:84%
So just more useful
information that we will

00:05:58.610 --> 00:06:03.125 align:middle line:84%
want to write down in store
for the auditing phase.

00:06:03.125 --> 00:06:08.970 align:middle line:90%


00:06:08.970 --> 00:06:12.930 align:middle line:84%
Now, that's two Windows
servers that we've looked at.

00:06:12.930 --> 00:06:16.350 align:middle line:84%
But what's really most
common out there in the wild

00:06:16.350 --> 00:06:20.390 align:middle line:84%
is Linux servers, so we'll
take a look at that next.

00:06:20.390 --> 00:06:21.000 align:middle line:90%