WEBVTT

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


00:00:10.020 --> 00:00:12.030 align:middle line:90%
Port scanning and enumeration.

00:00:12.030 --> 00:00:15.960 align:middle line:84%
Welcome to the first video
within the Linux Exploitations

00:00:15.960 --> 00:00:18.070 align:middle line:90%
section of this course.

00:00:18.070 --> 00:00:20.340 align:middle line:84%
So again, we're going to
be performing a black box

00:00:20.340 --> 00:00:22.770 align:middle line:84%
penetration test on
the Linux target,

00:00:22.770 --> 00:00:24.870 align:middle line:84%
as we did with the
Windows target.

00:00:24.870 --> 00:00:26.470 align:middle line:84%
And the first step
will, of course,

00:00:26.470 --> 00:00:28.980 align:middle line:84%
involve performing
port scanning in order

00:00:28.980 --> 00:00:31.020 align:middle line:84%
to identify open
ports on the target,

00:00:31.020 --> 00:00:34.860 align:middle line:84%
as well as the services that
are running on those open ports.

00:00:34.860 --> 00:00:38.010 align:middle line:84%
And we can then start performing
some basic enumeration

00:00:38.010 --> 00:00:41.250 align:middle line:84%
to learn as much information
as we can about these services

00:00:41.250 --> 00:00:44.010 align:middle line:84%
and what they are
used for in the case

00:00:44.010 --> 00:00:45.750 align:middle line:84%
or in the context
of services that

00:00:45.750 --> 00:00:50.350 align:middle line:84%
might be slightly ambiguous in
regards to the actual function.

00:00:50.350 --> 00:00:52.530 align:middle line:84%
So again, I just want
to reiterate something

00:00:52.530 --> 00:00:57.120 align:middle line:84%
that, again, if you are going
to be utilizing the same lab

00:00:57.120 --> 00:00:59.910 align:middle line:84%
environment for
this entire section,

00:00:59.910 --> 00:01:01.740 align:middle line:84%
you have the ability
to go through the pen

00:01:01.740 --> 00:01:05.580 align:middle line:84%
test in one sitting or
in one go and then refer

00:01:05.580 --> 00:01:07.330 align:middle line:90%
to these videos as a reference.

00:01:07.330 --> 00:01:09.780 align:middle line:84%
Now, do note that, once you
terminate the lab environment,

00:01:09.780 --> 00:01:12.030 align:middle line:84%
any data that's stored
on that lab environment

00:01:12.030 --> 00:01:15.510 align:middle line:84%
will be wiped, so keep all
your documented notes offline

00:01:15.510 --> 00:01:19.260 align:middle line:84%
or within a note a note-taking
application or note-keeping

00:01:19.260 --> 00:01:20.430 align:middle line:90%
application.

00:01:20.430 --> 00:01:22.530 align:middle line:84%
And of course, after
every termination

00:01:22.530 --> 00:01:25.410 align:middle line:84%
or after every restart,
the target IP address

00:01:25.410 --> 00:01:27.940 align:middle line:84%
within the lab
environment will change.

00:01:27.940 --> 00:01:30.200 align:middle line:84%
So do take that
into consideration.

00:01:30.200 --> 00:01:30.700 align:middle line:90%
All right.

00:01:30.700 --> 00:01:32.910 align:middle line:84%
So again, all you need
to do to get started

00:01:32.910 --> 00:01:34.590 align:middle line:84%
is just fire up the
lab environment.

00:01:34.590 --> 00:01:37.380 align:middle line:84%
And I'm also going to switch
into the lab environment,

00:01:37.380 --> 00:01:40.860 align:middle line:84%
and we can take a look at
how to identify open ports

00:01:40.860 --> 00:01:43.440 align:middle line:84%
as well as the services
running on these open ports

00:01:43.440 --> 00:01:44.370 align:middle line:90%
on the target system.

00:01:44.370 --> 00:01:48.050 align:middle line:90%


00:01:48.050 --> 00:01:50.510 align:middle line:84%
All right, so I'm back
within the lab environment.

00:01:50.510 --> 00:01:53.520 align:middle line:84%
And the first step
will, of course,

00:01:53.520 --> 00:01:57.200 align:middle line:84%
involve identifying the target
IP address, which can easily

00:01:57.200 --> 00:02:00.050 align:middle line:84%
be done by taking a
look or catting out

00:02:00.050 --> 00:02:03.980 align:middle line:84%
the contents of your hosts
file, which contains DNS entries

00:02:03.980 --> 00:02:05.330 align:middle line:90%
or DNS records.

00:02:05.330 --> 00:02:07.370 align:middle line:84%
And the target IP
should be assigned

00:02:07.370 --> 00:02:10.190 align:middle line:84%
to the following address--
so demo.ine.local,

00:02:10.190 --> 00:02:13.020 align:middle line:84%
and this is your target
IP right over here.

00:02:13.020 --> 00:02:14.750 align:middle line:84%
Now, again, as I
said, every time you

00:02:14.750 --> 00:02:17.130 align:middle line:84%
restart your lab environment,
this is going to change.

00:02:17.130 --> 00:02:19.400 align:middle line:84%
So always check
for the latest IP.

00:02:19.400 --> 00:02:21.770 align:middle line:84%
You can also ping
demo.ine.local.

00:02:21.770 --> 00:02:25.580 align:middle line:84%
However, I also have to mention
that this actual address here

00:02:25.580 --> 00:02:31.290 align:middle line:84%
might change to something like
ap.ine.local or lab.ine.local.

00:02:31.290 --> 00:02:32.540 align:middle line:90%
So just keep that in mind.

00:02:32.540 --> 00:02:34.490 align:middle line:84%
Always consult
with the host file,

00:02:34.490 --> 00:02:38.005 align:middle line:84%
and you should be able to
obtain the target IP that way.

00:02:38.005 --> 00:02:40.130 align:middle line:84%
All right, so let's get
started with port scanning.

00:02:40.130 --> 00:02:42.410 align:middle line:84%
Now, again, you have
the ability to output

00:02:42.410 --> 00:02:46.170 align:middle line:84%
your actual scan results into
the Metasploit framework.

00:02:46.170 --> 00:02:49.070 align:middle line:84%
But in this case, I'm just going
to be performing an Nmap scan.

00:02:49.070 --> 00:02:52.160 align:middle line:84%
And my objective here is
to identify the open ports.

00:02:52.160 --> 00:02:56.390 align:middle line:84%
So we can perform a service
version detection scan

00:02:56.390 --> 00:03:01.370 align:middle line:84%
on the target system,
and we can scan

00:03:01.370 --> 00:03:03.350 align:middle line:90%
the port range of 1 to 10,000.

00:03:03.350 --> 00:03:06.920 align:middle line:84%
So this is TCP, of
course, so 1 to 10,000.

00:03:06.920 --> 00:03:09.810 align:middle line:84%
And you can also increase
that to the entire TCP range,

00:03:09.810 --> 00:03:13.610 align:middle line:90%
which is about 65,535 ports.

00:03:13.610 --> 00:03:17.600 align:middle line:84%
And I can paste in
the target IP there.

00:03:17.600 --> 00:03:20.420 align:middle line:84%
I can also output it
into a readable format

00:03:20.420 --> 00:03:25.020 align:middle line:84%
by saying, oN or -oN and then
specifying the file name.

00:03:25.020 --> 00:03:29.690 align:middle line:84%
So I can say you
know nmap_10k.txt,

00:03:29.690 --> 00:03:32.180 align:middle line:84%
and that'll save it
within that file,

00:03:32.180 --> 00:03:35.710 align:middle line:84%
which I also recommend that
you do for later access.

00:03:35.710 --> 00:03:37.460 align:middle line:84%
So I'll hit Enter, and
I'll give this scan

00:03:37.460 --> 00:03:39.980 align:middle line:84%
a couple of seconds to a
couple of minutes to complete.

00:03:39.980 --> 00:03:44.740 align:middle line:84%
And let's see what services are
running on the target system.

00:03:44.740 --> 00:03:47.170 align:middle line:84%
All right, so the
Nmap scan is complete.

00:03:47.170 --> 00:03:49.400 align:middle line:84%
And let's take a
look at the results.

00:03:49.400 --> 00:03:51.638 align:middle line:84%
So right over here, we
have all the services

00:03:51.638 --> 00:03:52.930 align:middle line:90%
that are running on the target.

00:03:52.930 --> 00:03:54.430 align:middle line:90%
There are quite a few.

00:03:54.430 --> 00:03:57.310 align:middle line:84%
So starting off on port 21,
we, of course, have FTP,

00:03:57.310 --> 00:04:00.820 align:middle line:90%
and the version is vsftpd 2.3.4.

00:04:00.820 --> 00:04:01.720 align:middle line:90%
Interesting.

00:04:01.720 --> 00:04:05.770 align:middle line:84%
I think we actually covered this
or identified a vulnerability

00:04:05.770 --> 00:04:10.180 align:middle line:84%
within vsftpd 2.3.4 in
one of the earlier videos

00:04:10.180 --> 00:04:12.740 align:middle line:84%
that could be a
possible entry point.

00:04:12.740 --> 00:04:17.170 align:middle line:84%
We then have SSH
and OpenSSH 8.2p1,

00:04:17.170 --> 00:04:19.760 align:middle line:84%
which is currently not
vulnerable to any particular

00:04:19.760 --> 00:04:20.260 align:middle line:90%
exploit.

00:04:20.260 --> 00:04:23.920 align:middle line:84%
So the only alternative is
to perform a brute force.

00:04:23.920 --> 00:04:26.470 align:middle line:84%
And the great thing here
is that it provides us

00:04:26.470 --> 00:04:29.350 align:middle line:90%
with the distribution name.

00:04:29.350 --> 00:04:31.090 align:middle line:84%
So we can tell that
the target is running

00:04:31.090 --> 00:04:32.800 align:middle line:84%
Ubuntu, although we
are not really sure

00:04:32.800 --> 00:04:34.810 align:middle line:90%
about the version of Ubuntu.

00:04:34.810 --> 00:04:36.670 align:middle line:84%
And interestingly
enough, we actually

00:04:36.670 --> 00:04:38.470 align:middle line:84%
have Telnet running
on the target.

00:04:38.470 --> 00:04:41.470 align:middle line:84%
That's always something
nice to see once in a while.

00:04:41.470 --> 00:04:44.440 align:middle line:84%
So for those of you who
are not familiar, Telnet--

00:04:44.440 --> 00:04:47.650 align:middle line:84%
it was essentially the old
the first version of SSH.

00:04:47.650 --> 00:04:49.390 align:middle line:84%
And, of course, it
had a lot of issues

00:04:49.390 --> 00:04:53.740 align:middle line:84%
with security, one of which
was a lack of encryption

00:04:53.740 --> 00:04:56.320 align:middle line:84%
of the data that's
being transferred

00:04:56.320 --> 00:04:58.310 align:middle line:84%
between the client
and the server.

00:04:58.310 --> 00:05:02.360 align:middle line:84%
And open SSH it was developed
as a more secure alternative.

00:05:02.360 --> 00:05:04.480 align:middle line:84%
So that's good to see
that we have Telnet.

00:05:04.480 --> 00:05:05.920 align:middle line:84%
It's always an
interesting service

00:05:05.920 --> 00:05:07.820 align:middle line:90%
to test or play around with.

00:05:07.820 --> 00:05:11.350 align:middle line:84%
We then have SMTP
running on port 25.

00:05:11.350 --> 00:05:13.990 align:middle line:90%
And the version is Postfix.

00:05:13.990 --> 00:05:17.980 align:middle line:84%
It looks like we also have
another open SSH server that's

00:05:17.980 --> 00:05:19.180 align:middle line:90%
running on port 51.

00:05:19.180 --> 00:05:20.230 align:middle line:90%
Interesting.

00:05:20.230 --> 00:05:25.000 align:middle line:84%
And in addition to that, we have
a web server right over here,

00:05:25.000 --> 00:05:26.680 align:middle line:90%
running on port 80.

00:05:26.680 --> 00:05:32.710 align:middle line:84%
And it's saying it's Apache
httpd 2.2.8 (Ubuntu) and DAV.

00:05:32.710 --> 00:05:33.940 align:middle line:90%
I have covered DAV--

00:05:33.940 --> 00:05:37.320 align:middle line:84%
or WebDAV-- in the system in
Host-Based Attacks course.

00:05:37.320 --> 00:05:40.570 align:middle line:84%
So could we actually
launch an attack there?

00:05:40.570 --> 00:05:41.800 align:middle line:90%
We have RPC.

00:05:41.800 --> 00:05:46.120 align:middle line:84%
We have SMB, which, in the
case of Linux, is Samba.

00:05:46.120 --> 00:05:49.690 align:middle line:84%
So Samba is the open
source Linux implementation

00:05:49.690 --> 00:05:51.640 align:middle line:90%
of SMB for Linux.

00:05:51.640 --> 00:05:54.920 align:middle line:84%
And again, it works
exactly the same.

00:05:54.920 --> 00:05:58.940 align:middle line:84%
We also have a few
ambiguous ports here.

00:05:58.940 --> 00:06:01.960 align:middle line:84%
So 512-- you can see that,
whenever Nmap provides you

00:06:01.960 --> 00:06:03.460 align:middle line:84%
with the service
and then a question

00:06:03.460 --> 00:06:05.290 align:middle line:84%
mark at the end,
that means that it's

00:06:05.290 --> 00:06:07.420 align:middle line:84%
not really sure
what this service is

00:06:07.420 --> 00:06:08.870 align:middle line:90%
and what it's used for.

00:06:08.870 --> 00:06:11.500 align:middle line:84%
So we would probably
need to manually check

00:06:11.500 --> 00:06:14.710 align:middle line:84%
these ports with Netcat to
see what banner they actually

00:06:14.710 --> 00:06:15.490 align:middle line:90%
bring up.

00:06:15.490 --> 00:06:20.170 align:middle line:90%
So we have 512, 513, 514.

00:06:20.170 --> 00:06:25.360 align:middle line:84%
And then, on 1099, we have a
GNU Classpath grmiregistry.

00:06:25.360 --> 00:06:29.607 align:middle line:84%
On port 1524, we have a
service called ingreslock?,

00:06:29.607 --> 00:06:31.690 align:middle line:84%
although that's something
that we'll need to test.

00:06:31.690 --> 00:06:35.950 align:middle line:84%
We have a MySQL database
server running on port 3306,

00:06:35.950 --> 00:06:39.160 align:middle line:90%
and the version is 5.0.51a.

00:06:39.160 --> 00:06:42.970 align:middle line:84%
And we get the operating system
or the distribution release

00:06:42.970 --> 00:06:44.380 align:middle line:90%
name there.

00:06:44.380 --> 00:06:49.030 align:middle line:84%
On port 3632, we have a
service that's quite difficult

00:06:49.030 --> 00:06:50.220 align:middle line:90%
to tell what it is.

00:06:50.220 --> 00:06:52.030 align:middle line:90%
So distccd.

00:06:52.030 --> 00:06:55.030 align:middle line:84%
We have a PostgresSQL
database service or server

00:06:55.030 --> 00:06:58.400 align:middle line:90%
running on port 5432.

00:06:58.400 --> 00:07:05.830 align:middle line:84%
And we have an irc server
running on port 6667 and 6697.

00:07:05.830 --> 00:07:11.060 align:middle line:84%
That is UnrealIRCd, or
the UnrealIRCd daemon,

00:07:11.060 --> 00:07:14.750 align:middle line:90%
and Apache Jserv on port 8009.

00:07:14.750 --> 00:07:18.980 align:middle line:84%
And on port 8180, it looks
like we have Apache Tomcat.

00:07:18.980 --> 00:07:23.300 align:middle line:90%
And 8787, we have Ruby DRb RMI.

00:07:23.300 --> 00:07:26.030 align:middle line:84%
OK, so these are very
interesting services.

00:07:26.030 --> 00:07:27.620 align:middle line:84%
And, of course,
I'll be taking you

00:07:27.620 --> 00:07:30.860 align:middle line:84%
through how to exploit some
of the low-hanging fruit

00:07:30.860 --> 00:07:32.540 align:middle line:90%
in terms of vulnerable services.

00:07:32.540 --> 00:07:33.800 align:middle line:90%
And there are quite a few--

00:07:33.800 --> 00:07:36.390 align:middle line:84%
or fairly less than
the Windows system.

00:07:36.390 --> 00:07:38.900 align:middle line:84%
But again, these ones
are much more interesting

00:07:38.900 --> 00:07:40.310 align:middle line:84%
and are different,
and that's why

00:07:40.310 --> 00:07:43.140 align:middle line:84%
I wanted to highlight
both Windows and Linux.

00:07:43.140 --> 00:07:45.680 align:middle line:84%
So let's try and
identify or learn

00:07:45.680 --> 00:07:50.600 align:middle line:84%
more about these weird
services here, like 512, 513.

00:07:50.600 --> 00:07:55.010 align:middle line:84%
So again, whenever you don't get
a service or the actual banner

00:07:55.010 --> 00:07:58.010 align:middle line:90%
from a service with Nmap--

00:07:58.010 --> 00:08:00.170 align:middle line:84%
again, this is where
manual banner grabbing

00:08:00.170 --> 00:08:01.140 align:middle line:90%
would come into play.

00:08:01.140 --> 00:08:05.630 align:middle line:84%
So we can say Netcat and
nv, specify the target IP

00:08:05.630 --> 00:08:09.170 align:middle line:84%
and the port that we would like
to learn more about, so 512.

00:08:09.170 --> 00:08:12.180 align:middle line:84%
We hit Enter, and we
don't get any banner.

00:08:12.180 --> 00:08:13.640 align:middle line:84%
And if we type in
a system command,

00:08:13.640 --> 00:08:15.750 align:middle line:84%
it doesn't look like
anything much here.

00:08:15.750 --> 00:08:18.360 align:middle line:84%
So again, that
could be a dead end.

00:08:18.360 --> 00:08:19.940 align:middle line:90%
So let's keep our eye on that.

00:08:19.940 --> 00:08:23.180 align:middle line:84%
We then have port
5134, which says login.

00:08:23.180 --> 00:08:24.530 align:middle line:90%
We hit Enter.

00:08:24.530 --> 00:08:25.370 align:middle line:90%
Can we log in?

00:08:25.370 --> 00:08:28.850 align:middle line:84%
It looks like it's saying,
Connection reset by peer.

00:08:28.850 --> 00:08:31.550 align:middle line:84%
So can I enter something
like, test, for example?

00:08:31.550 --> 00:08:32.480 align:middle line:90%
Reset by peer.

00:08:32.480 --> 00:08:32.990 align:middle line:90%
Interesting.

00:08:32.990 --> 00:08:34.650 align:middle line:90%
Very, very interesting.

00:08:34.650 --> 00:08:37.190 align:middle line:90%
We then have port 514.

00:08:37.190 --> 00:08:41.270 align:middle line:84%
So I'll hit Enter and
again, we're connected. ls--

00:08:41.270 --> 00:08:42.590 align:middle line:90%
you can see broken pipe.

00:08:42.590 --> 00:08:43.610 align:middle line:90%
OK, OK.

00:08:43.610 --> 00:08:45.800 align:middle line:90%
Very interesting stuff.

00:08:45.800 --> 00:08:49.430 align:middle line:84%
And let's take a look
at the last one, which--

00:08:49.430 --> 00:08:50.810 align:middle line:90%
it looks very interesting.

00:08:50.810 --> 00:08:53.390 align:middle line:90%
That's on port 1524.

00:08:53.390 --> 00:08:56.720 align:middle line:90%
So I'll say Netcat nv.

00:08:56.720 --> 00:08:59.720 align:middle line:84%
And we're looking
for port 1524, or we

00:08:59.720 --> 00:09:00.980 align:middle line:90%
want to connect to that port.

00:09:00.980 --> 00:09:02.300 align:middle line:90%
I'll hit Enter.

00:09:02.300 --> 00:09:04.100 align:middle line:90%
And what do we have here?

00:09:04.100 --> 00:09:06.347 align:middle line:84%
And this is one of
the really cool things

00:09:06.347 --> 00:09:07.680 align:middle line:90%
that I wanted to share with you.

00:09:07.680 --> 00:09:10.370 align:middle line:90%
So what has just happened here?

00:09:10.370 --> 00:09:14.090 align:middle line:84%
I've connected to a specific
port on the target system

00:09:14.090 --> 00:09:17.270 align:middle line:84%
with Netcat, and I've
received a root shell

00:09:17.270 --> 00:09:19.040 align:middle line:90%
on the target system.

00:09:19.040 --> 00:09:22.340 align:middle line:84%
Well, what this is a
bind shell listener.

00:09:22.340 --> 00:09:24.860 align:middle line:84%
And if you remember, if you go
back to the Bind and Reverse

00:09:24.860 --> 00:09:28.610 align:middle line:84%
Shells section of this course, I
mentioned how bind shells work.

00:09:28.610 --> 00:09:32.060 align:middle line:84%
You need to have the listener
on the target system,

00:09:32.060 --> 00:09:35.690 align:middle line:84%
and then the attacker
connects to the target system

00:09:35.690 --> 00:09:38.420 align:middle line:84%
or to the listener on the
target system with Netcat,

00:09:38.420 --> 00:09:40.230 align:middle line:90%
and that's exactly what we did.

00:09:40.230 --> 00:09:44.030 align:middle line:84%
So port 1524 is a
bind shell listener,

00:09:44.030 --> 00:09:47.370 align:middle line:84%
and it's provided us with root
access on the target system.

00:09:47.370 --> 00:09:50.810 align:middle line:84%
So again, this is why you should
always perform manual banner

00:09:50.810 --> 00:09:55.430 align:middle line:84%
grabbing, and I just set
this up to demonstrate

00:09:55.430 --> 00:09:59.480 align:middle line:84%
what a bind shell listener
would look like if you set it up

00:09:59.480 --> 00:10:03.200 align:middle line:84%
on a Linux system or even on
a Windows system, and the fact

00:10:03.200 --> 00:10:05.150 align:middle line:84%
that you really can't
tell what it is.

00:10:05.150 --> 00:10:08.250 align:middle line:84%
So again, if we list out the
contents of this directory,

00:10:08.250 --> 00:10:10.280 align:middle line:84%
you can see we're on
the target system.

00:10:10.280 --> 00:10:13.110 align:middle line:84%
If I get the distribution
information--

00:10:13.110 --> 00:10:18.020 align:middle line:84%
so I can say cat /etc,
and we can say *release.

00:10:18.020 --> 00:10:20.330 align:middle line:84%
You can see it's running
Ubuntu, and it looks

00:10:20.330 --> 00:10:22.400 align:middle line:90%
like it's running Ubuntu 8.4.

00:10:22.400 --> 00:10:23.120 align:middle line:90%
Interesting.

00:10:23.120 --> 00:10:24.260 align:middle line:90%
Very, very interesting.

00:10:24.260 --> 00:10:24.980 align:middle line:90%
OK.

00:10:24.980 --> 00:10:31.007 align:middle line:84%
So if we take a look at maybe
a few directories on the Home,

00:10:31.007 --> 00:10:32.340 align:middle line:90%
let's see what we have in there.

00:10:32.340 --> 00:10:34.250 align:middle line:84%
It looks like we have
a few directories.

00:10:34.250 --> 00:10:37.670 align:middle line:84%
We have FTP, msf admin
service, user, et cetera.

00:10:37.670 --> 00:10:41.150 align:middle line:84%
All right, so this was just a
simple demonstration or example

00:10:41.150 --> 00:10:44.120 align:middle line:84%
to show you how bind
shell listeners work

00:10:44.120 --> 00:10:45.590 align:middle line:90%
and how you can connect to them.

00:10:45.590 --> 00:10:48.230 align:middle line:84%
And, as I said, if you followed
along with those sections

00:10:48.230 --> 00:10:52.610 align:middle line:84%
closely and you also, again,
took into consideration banner

00:10:52.610 --> 00:10:56.510 align:middle line:84%
grabbing, then this would have
been a very easy initial win.

00:10:56.510 --> 00:11:00.950 align:middle line:84%
However, for the purpose of
this video and the next videos,

00:11:00.950 --> 00:11:05.090 align:middle line:84%
I am not going to be using the
bind shell listener for access.

00:11:05.090 --> 00:11:08.540 align:middle line:84%
We're going to be finding more
legitimate ways because you'll

00:11:08.540 --> 00:11:10.790 align:middle line:84%
hardly find a bind
shell listener running

00:11:10.790 --> 00:11:13.700 align:middle line:84%
on an enterprise
system or a system that

00:11:13.700 --> 00:11:15.210 align:middle line:90%
has been set up by a company.

00:11:15.210 --> 00:11:18.050 align:middle line:84%
So that was a really,
really cool example

00:11:18.050 --> 00:11:19.790 align:middle line:84%
that I wanted to
highlight there.

00:11:19.790 --> 00:11:22.250 align:middle line:84%
OK, so we've been
able to identify

00:11:22.250 --> 00:11:25.100 align:middle line:84%
most of the important
services, like the web server,

00:11:25.100 --> 00:11:26.490 align:middle line:90%
and we can learn more about it.

00:11:26.490 --> 00:11:28.610 align:middle line:84%
Let's actually open
this up in the browser.

00:11:28.610 --> 00:11:32.040 align:middle line:84%
And it looks like we
have WebDAV configured.

00:11:32.040 --> 00:11:33.860 align:middle line:84%
So if we click on
that there, this

00:11:33.860 --> 00:11:35.940 align:middle line:90%
is the target system's hostname.

00:11:35.940 --> 00:11:38.010 align:middle line:84%
And we have a few
web applications.

00:11:38.010 --> 00:11:42.380 align:middle line:84%
Now, these two web applications
are intentionally vulnerable

00:11:42.380 --> 00:11:43.970 align:middle line:84%
web applications
that have been set

00:11:43.970 --> 00:11:48.300 align:middle line:84%
to highlight or to demonstrate
web application pen tests.

00:11:48.300 --> 00:11:50.900 align:middle line:84%
So again, I wouldn't recommend
targeting any of them.

00:11:50.900 --> 00:11:53.930 align:middle line:84%
But we have a web
app called TWiki.

00:11:53.930 --> 00:11:57.960 align:middle line:84%
We also have a phpMyAdmin,
which is very, very interesting.

00:11:57.960 --> 00:12:00.920 align:middle line:84%
We have already targeted that
in the Windows Exploitation

00:12:00.920 --> 00:12:01.640 align:middle line:90%
section.

00:12:01.640 --> 00:12:03.230 align:middle line:90%
And we have WebDAV.

00:12:03.230 --> 00:12:07.280 align:middle line:84%
OK, so if you've actually
gone through the system

00:12:07.280 --> 00:12:09.410 align:middle line:84%
and Host-Based
Attacks course, you

00:12:09.410 --> 00:12:12.410 align:middle line:84%
should be familiar
with what WebDAV is

00:12:12.410 --> 00:12:14.100 align:middle line:90%
and how it can be exploited.

00:12:14.100 --> 00:12:18.380 align:middle line:84%
So we have a very good mix of
services here, some of which

00:12:18.380 --> 00:12:19.910 align:middle line:90%
we can actually explore.

00:12:19.910 --> 00:12:22.220 align:middle line:84%
And again, I'll
not tell you what

00:12:22.220 --> 00:12:23.840 align:middle line:90%
the next video is going to be.

00:12:23.840 --> 00:12:25.700 align:middle line:84%
And again, the
reason for that is I

00:12:25.700 --> 00:12:27.860 align:middle line:84%
want you to actually go
through this yourself

00:12:27.860 --> 00:12:30.920 align:middle line:84%
and try and gain access
via another vector,

00:12:30.920 --> 00:12:34.280 align:middle line:84%
apart from the actual
bind shell listener

00:12:34.280 --> 00:12:36.720 align:middle line:84%
that we actually
use to gain access.

00:12:36.720 --> 00:12:40.640 align:middle line:84%
So that is going to conclude
the practical demonstration

00:12:40.640 --> 00:12:41.850 align:middle line:90%
side of this video.

00:12:41.850 --> 00:12:44.630 align:middle line:84%
Now, as I said, you can also
output your Nmap scan results

00:12:44.630 --> 00:12:47.562 align:middle line:84%
and import them into the
Metasploit framework.

00:12:47.562 --> 00:12:49.520 align:middle line:84%
But in my case, I'm not
going to be doing this.

00:12:49.520 --> 00:12:53.570 align:middle line:84%
I'm going to be targeting each
of these services individually.

00:12:53.570 --> 00:12:55.670 align:middle line:84%
And yeah, so that's
going to conclude

00:12:55.670 --> 00:12:59.390 align:middle line:84%
the practical demonstration
side of this video.

00:12:59.390 --> 00:13:02.560 align:middle line:84%
All right, so that concludes the
port scanning and enumeration

00:13:02.560 --> 00:13:05.650 align:middle line:84%
section of video
within this section.

00:13:05.650 --> 00:13:08.350 align:middle line:84%
In the next video, we're going
to be taking a look at how

00:13:08.350 --> 00:13:11.500 align:middle line:84%
to target the next service
or our first service

00:13:11.500 --> 00:13:12.860 align:middle line:90%
on the target system.

00:13:12.860 --> 00:13:15.500 align:middle line:90%
So I'll see you there.

00:13:15.500 --> 00:13:16.000 align:middle line:90%