WEBVTT

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


00:00:03.880 --> 00:00:06.790 align:middle line:90%
[MUSIC PLAYING]

00:00:06.790 --> 00:00:10.200 align:middle line:90%


00:00:10.200 --> 00:00:13.720 align:middle line:84%
Vulnerability scanning with
Metasploit-- in this video,

00:00:13.720 --> 00:00:17.070 align:middle line:84%
we will be exploring the process
of performing vulnerability

00:00:17.070 --> 00:00:20.220 align:middle line:84%
scanning and detection with
the Metasploit Framework,

00:00:20.220 --> 00:00:23.520 align:middle line:84%
very similar to what we did
with the Nmap Scripting Engine,

00:00:23.520 --> 00:00:27.090 align:middle line:84%
the main objective
being to essentially

00:00:27.090 --> 00:00:30.150 align:middle line:84%
be able to identify
services that are running

00:00:30.150 --> 00:00:33.060 align:middle line:84%
on open ports on a target
system and consequently

00:00:33.060 --> 00:00:35.130 align:middle line:84%
identify or detect
vulnerabilities

00:00:35.130 --> 00:00:36.760 align:middle line:90%
within those services.

00:00:36.760 --> 00:00:39.210 align:middle line:84%
Now, I've already
explored how to perform

00:00:39.210 --> 00:00:42.820 align:middle line:84%
this process in depth within
the Metasploit Framework course.

00:00:42.820 --> 00:00:44.490 align:middle line:84%
So if you want to
learn more about how

00:00:44.490 --> 00:00:47.550 align:middle line:84%
to perform vulnerability
scanning with Metasploit,

00:00:47.550 --> 00:00:50.080 align:middle line:84%
definitely check
out that course.

00:00:50.080 --> 00:00:51.760 align:middle line:84%
However, in this
particular video,

00:00:51.760 --> 00:00:54.900 align:middle line:84%
we will be exploring a simple
example of how a penetration

00:00:54.900 --> 00:00:58.140 align:middle line:84%
tester can utilize the
Metasploit Framework to detect

00:00:58.140 --> 00:01:01.540 align:middle line:84%
a vulnerability on
a target system.

00:01:01.540 --> 00:01:03.210 align:middle line:84%
So again, we'll
just dive straight

00:01:03.210 --> 00:01:05.550 align:middle line:84%
into the actual
practical demonstration.

00:01:05.550 --> 00:01:09.640 align:middle line:84%
Now, this video doesn't have a
lab environment attached to it.

00:01:09.640 --> 00:01:11.760 align:middle line:84%
And the reason for
that is primarily

00:01:11.760 --> 00:01:14.190 align:middle line:84%
because I will be
focusing on techniques

00:01:14.190 --> 00:01:17.710 align:middle line:84%
as opposed to replication of
techniques because, as I said,

00:01:17.710 --> 00:01:18.960 align:middle line:90%
I've already covered this.

00:01:18.960 --> 00:01:21.270 align:middle line:84%
And all you really
need to take note

00:01:21.270 --> 00:01:24.180 align:middle line:84%
of is the actual flow
or the techniques

00:01:24.180 --> 00:01:27.840 align:middle line:84%
that you can use in conjunction
with the Metasploit framework

00:01:27.840 --> 00:01:30.210 align:middle line:84%
to essentially detect
vulnerabilities.

00:01:30.210 --> 00:01:31.710 align:middle line:84%
And of course, you
are going to be

00:01:31.710 --> 00:01:33.390 align:middle line:84%
faced with different
types of services

00:01:33.390 --> 00:01:35.560 align:middle line:84%
whenever you're performing
a penetration test.

00:01:35.560 --> 00:01:37.320 align:middle line:84%
So all you really
need to know how to do

00:01:37.320 --> 00:01:39.960 align:middle line:84%
is to essentially replicate
the techniques that I

00:01:39.960 --> 00:01:41.070 align:middle line:90%
will be performing.

00:01:41.070 --> 00:01:44.700 align:middle line:84%
So I'll switch over
to my Kali Linux VM,

00:01:44.700 --> 00:01:48.910 align:middle line:84%
and we can get started with
the practical demonstration.

00:01:48.910 --> 00:01:51.600 align:middle line:84%
All right, I'm
back on my Kali VM.

00:01:51.600 --> 00:01:56.220 align:middle line:84%
And I'm going to be performing
an Nmap scan first and foremost

00:01:56.220 --> 00:01:57.390 align:middle line:90%
on the target system.

00:01:57.390 --> 00:02:01.620 align:middle line:84%
The target system, we really
do not know much about it other

00:02:01.620 --> 00:02:02.920 align:middle line:90%
than its IP address.

00:02:02.920 --> 00:02:05.500 align:middle line:90%
So we can get started with that.

00:02:05.500 --> 00:02:07.080 align:middle line:84%
So what I'll do
here is I'll just

00:02:07.080 --> 00:02:11.039 align:middle line:84%
perform an Nmap scan to learn
as much information as possible

00:02:11.039 --> 00:02:12.760 align:middle line:90%
about this particular target.

00:02:12.760 --> 00:02:13.260 align:middle line:90%
Right?

00:02:13.260 --> 00:02:16.420 align:middle line:90%
So we can perform a SYN scan.

00:02:16.420 --> 00:02:17.790 align:middle line:90%
So that is SS.

00:02:17.790 --> 00:02:20.460 align:middle line:84%
And we can then perform a
Service Version Detection

00:02:20.460 --> 00:02:21.600 align:middle line:90%
scan here.

00:02:21.600 --> 00:02:26.100 align:middle line:84%
And the target IP, in
my case, is 10.10.10.7.

00:02:26.100 --> 00:02:30.150 align:middle line:84%
All right, I can also
output this into an XML file

00:02:30.150 --> 00:02:32.850 align:middle line:84%
so that I can import it into
the Metasploit Framework.

00:02:32.850 --> 00:02:36.450 align:middle line:84%
But that will really not
be applicable at this point

00:02:36.450 --> 00:02:37.030 align:middle line:90%
in time.

00:02:37.030 --> 00:02:39.090 align:middle line:90%
So, I'll just hit Enter.

00:02:39.090 --> 00:02:40.710 align:middle line:90%
And let's see.

00:02:40.710 --> 00:02:42.480 align:middle line:84%
The scan will begin,
and this is going

00:02:42.480 --> 00:02:44.560 align:middle line:84%
to take a few seconds
to a couple of minutes.

00:02:44.560 --> 00:02:47.940 align:middle line:84%
So I'll just wait for
the scan to complete.

00:02:47.940 --> 00:02:48.440 align:middle line:90%
All right.

00:02:48.440 --> 00:02:51.110 align:middle line:84%
So after a couple of minutes,
the Nmap scan is done.

00:02:51.110 --> 00:02:54.950 align:middle line:84%
And we can see that it has the
typical ports you'd associate

00:02:54.950 --> 00:02:56.300 align:middle line:90%
with a Windows system.

00:02:56.300 --> 00:02:59.425 align:middle line:84%
And indeed, on the SMB
port, which is port 445,

00:02:59.425 --> 00:03:03.740 align:middle line:84%
we can see that it prints out
the actual operating system

00:03:03.740 --> 00:03:06.560 align:middle line:84%
banner, or it gives
us a rough idea

00:03:06.560 --> 00:03:10.740 align:middle line:84%
as to what operating system
is running on the target.

00:03:10.740 --> 00:03:13.220 align:middle line:84%
And in this case, we do
know that it is Windows.

00:03:13.220 --> 00:03:16.940 align:middle line:84%
However, in the case of the SMB
banner or the service version,

00:03:16.940 --> 00:03:20.090 align:middle line:84%
it really doesn't give
us a concrete version of

00:03:20.090 --> 00:03:21.560 align:middle line:90%
or edition of Windows.

00:03:21.560 --> 00:03:23.970 align:middle line:84%
It just says from
Windows 7 to 10.

00:03:23.970 --> 00:03:26.780 align:middle line:84%
However, if we take a
look at the service info,

00:03:26.780 --> 00:03:29.220 align:middle line:84%
we can see that as
for the hostname,

00:03:29.220 --> 00:03:31.700 align:middle line:84%
the system is
called Windows 7-PC.

00:03:31.700 --> 00:03:34.700 align:middle line:84%
So we have a good idea of
what version of Windows

00:03:34.700 --> 00:03:36.260 align:middle line:90%
is running on the target.

00:03:36.260 --> 00:03:39.860 align:middle line:84%
Now, how do we utilize this
information in conjunction

00:03:39.860 --> 00:03:41.360 align:middle line:90%
with the Metasploit Framework?

00:03:41.360 --> 00:03:45.350 align:middle line:84%
Well, if we take a look at
the vulnerabilities that

00:03:45.350 --> 00:03:49.160 align:middle line:84%
affect Windows seven, or maybe
older versions of Windows

00:03:49.160 --> 00:03:51.680 align:middle line:84%
or Windows versions
prior to Windows 7,

00:03:51.680 --> 00:03:56.840 align:middle line:84%
we are aware of a vulnerability
or exploit called EternalBlue

00:03:56.840 --> 00:03:59.750 align:middle line:84%
that essentially
targets SMB version 1

00:03:59.750 --> 00:04:03.530 align:middle line:84%
and allows an attacker to
execute arbitrary code,

00:04:03.530 --> 00:04:07.340 align:middle line:84%
which can consequently provide
them with remote access.

00:04:07.340 --> 00:04:11.390 align:middle line:84%
And of course, we can learn more
about this particular exploit

00:04:11.390 --> 00:04:14.370 align:middle line:84%
by using the
searchsploit utility.

00:04:14.370 --> 00:04:17.029 align:middle line:84%
So we can say
searchsploit, and we

00:04:17.029 --> 00:04:19.850 align:middle line:84%
can launch a search for
the EternalBlue exploit.

00:04:19.850 --> 00:04:22.610 align:middle line:84%
And if we click on it, we
can see that it provides us

00:04:22.610 --> 00:04:24.830 align:middle line:90%
with three options here.

00:04:24.830 --> 00:04:27.890 align:middle line:84%
You can see we have Microsoft
Windows 7 and Windows Server

00:04:27.890 --> 00:04:29.510 align:middle line:90%
2008 R2.

00:04:29.510 --> 00:04:31.400 align:middle line:90%
And that's exactly where we are.

00:04:31.400 --> 00:04:33.290 align:middle line:84%
And it gives you a
description as to what

00:04:33.290 --> 00:04:35.090 align:middle line:90%
this particular exploit does.

00:04:35.090 --> 00:04:36.898 align:middle line:90%
So it's codenamed EternalBlue.

00:04:36.898 --> 00:04:38.690 align:middle line:84%
And of course, I've
covered the EternalBlue

00:04:38.690 --> 00:04:40.140 align:middle line:90%
exploit multiple times.

00:04:40.140 --> 00:04:42.690 align:middle line:84%
So you should be fairly
familiar with it.

00:04:42.690 --> 00:04:45.080 align:middle line:84%
So this is SMB Remote
Code Execution.

00:04:45.080 --> 00:04:48.890 align:middle line:84%
This is the Microsoft security
or vulnerability identifier.

00:04:48.890 --> 00:04:52.100 align:middle line:90%
So that is MS17-010.

00:04:52.100 --> 00:04:55.910 align:middle line:84%
And it was released or
made public in 2017.

00:04:55.910 --> 00:04:59.630 align:middle line:84%
And of course, if you take
a closer look at the results

00:04:59.630 --> 00:05:02.160 align:middle line:84%
here-- and I'm just going to
zoom out a little bit here

00:05:02.160 --> 00:05:07.010 align:middle line:84%
so you can actually see the
actual output displayed much

00:05:07.010 --> 00:05:08.460 align:middle line:90%
more clearly--

00:05:08.460 --> 00:05:13.580 align:middle line:84%
you can see that, for
specific for specific exploits

00:05:13.580 --> 00:05:18.320 align:middle line:84%
here, in some cases you may
be provided with a Metasploit

00:05:18.320 --> 00:05:18.860 align:middle line:90%
option.

00:05:18.860 --> 00:05:22.440 align:middle line:84%
Or Metasploit might be
highlighted in brackets here.

00:05:22.440 --> 00:05:26.210 align:middle line:84%
So what we can do is we can
perform the search again,

00:05:26.210 --> 00:05:31.130 align:middle line:84%
or we can just say
MS17-010, just that

00:05:31.130 --> 00:05:33.920 align:middle line:84%
is the Microsoft
security identifier.

00:05:33.920 --> 00:05:35.210 align:middle line:90%
And we hit Enter.

00:05:35.210 --> 00:05:37.910 align:middle line:84%
You can see that we
have a Metasploit

00:05:37.910 --> 00:05:40.460 align:middle line:84%
module for this
particular-- or rather,

00:05:40.460 --> 00:05:42.680 align:middle line:84%
we have two
Metasploit modules for

00:05:42.680 --> 00:05:44.160 align:middle line:90%
this particular vulnerability.

00:05:44.160 --> 00:05:44.660 align:middle line:90%
Right?

00:05:44.660 --> 00:05:46.790 align:middle line:84%
And of course, I will
cover the process

00:05:46.790 --> 00:05:49.880 align:middle line:84%
of utilizing searchsploits
to essentially fine-tune

00:05:49.880 --> 00:05:50.540 align:middle line:90%
your searches.

00:05:50.540 --> 00:05:54.530 align:middle line:84%
But for now, the two that
we want to take a look at

00:05:54.530 --> 00:05:55.730 align:middle line:90%
is this one right over here.

00:05:55.730 --> 00:05:59.840 align:middle line:84%
This is the EternalRomance,
EternalSynergy, EternalChampion

00:05:59.840 --> 00:06:01.550 align:middle line:90%
SMB Remote Code Execution.

00:06:01.550 --> 00:06:03.140 align:middle line:90%
That is a Metasploit module.

00:06:03.140 --> 00:06:05.240 align:middle line:84%
Or what that
indicates is there is

00:06:05.240 --> 00:06:09.500 align:middle line:84%
a Metasploit module available
for this particular exploit.

00:06:09.500 --> 00:06:12.290 align:middle line:84%
And the one that we're
interested in here

00:06:12.290 --> 00:06:15.390 align:middle line:84%
is the SMB Remote Code
Execution Scanner.

00:06:15.390 --> 00:06:15.890 align:middle line:90%
All right.

00:06:15.890 --> 00:06:17.598 align:middle line:84%
Now why are we interested
in the scanner?

00:06:17.598 --> 00:06:20.540 align:middle line:84%
Well, remember we're still
in the vulnerability scanning

00:06:20.540 --> 00:06:23.550 align:middle line:84%
and detection phase of
the penetration test.

00:06:23.550 --> 00:06:27.680 align:middle line:84%
So before we start throwing
exploits at the target system,

00:06:27.680 --> 00:06:30.500 align:middle line:84%
we need to verify whether
the system is indeed

00:06:30.500 --> 00:06:34.220 align:middle line:84%
vulnerable to this particular
vulnerability or exploit.

00:06:34.220 --> 00:06:36.260 align:middle line:84%
And of course, there
is an Nmap script

00:06:36.260 --> 00:06:40.580 align:middle line:84%
that can actually be used
to verify whether or not

00:06:40.580 --> 00:06:42.800 align:middle line:84%
the system is vulnerable
to this particular exploit.

00:06:42.800 --> 00:06:46.230 align:middle line:84%
But in this case, we're focusing
on the Metasploit Framework.

00:06:46.230 --> 00:06:50.300 align:middle line:84%
So what we can do is we
can open up MSF Console.

00:06:50.300 --> 00:06:53.470 align:middle line:84%
So I'm just going
to say msfconsole.

00:06:53.470 --> 00:06:56.570 align:middle line:84%
And I'll zoom in here so
you can see what's going on.

00:06:56.570 --> 00:06:59.770 align:middle line:84%
And let me just wait for the
Metasploit Framework console

00:06:59.770 --> 00:07:00.970 align:middle line:90%
to start up.

00:07:00.970 --> 00:07:01.720 align:middle line:90%
There we are.

00:07:01.720 --> 00:07:04.680 align:middle line:90%
It's starting up.

00:07:04.680 --> 00:07:06.540 align:middle line:90%
And I'll clear up the terminal.

00:07:06.540 --> 00:07:10.090 align:middle line:84%
And we can now launch a search
for that particular module.

00:07:10.090 --> 00:07:12.210 align:middle line:84%
Now remember, vulnerability
scanning and detection

00:07:12.210 --> 00:07:13.500 align:middle line:90%
isn't exploitation.

00:07:13.500 --> 00:07:18.510 align:middle line:84%
We're simply trying to identify
whether the target is indeed

00:07:18.510 --> 00:07:20.610 align:middle line:84%
vulnerable to a
particular exploit.

00:07:20.610 --> 00:07:23.310 align:middle line:84%
And in this case, as
we were able to deduce

00:07:23.310 --> 00:07:27.630 align:middle line:84%
from the searchsploit results,
the EternalBlue vulnerability,

00:07:27.630 --> 00:07:32.340 align:middle line:84%
or exploit if you will, affects
the specific version of Windows

00:07:32.340 --> 00:07:35.110 align:middle line:84%
that is running on
the target system.

00:07:35.110 --> 00:07:39.150 align:middle line:84%
However, we can't be sure
completely because, again,

00:07:39.150 --> 00:07:41.370 align:middle line:84%
in terms of
EternalBlue, it really

00:07:41.370 --> 00:07:44.520 align:middle line:84%
doesn't state what build
number of Windows it affects.

00:07:44.520 --> 00:07:48.420 align:middle line:84%
So this is where the whole
aspect of auxiliary modules

00:07:48.420 --> 00:07:49.540 align:middle line:90%
comes into play.

00:07:49.540 --> 00:07:54.160 align:middle line:84%
So we can launch a
search for EternalBlue.

00:07:54.160 --> 00:07:54.760 align:middle line:90%
There we are.

00:07:54.760 --> 00:07:57.190 align:middle line:84%
And it'll provide us
with multiple modules.

00:07:57.190 --> 00:07:59.480 align:middle line:84%
Now remember, we're not
looking for exploit modules

00:07:59.480 --> 00:08:00.730 align:middle line:90%
like this one right over here.

00:08:00.730 --> 00:08:03.700 align:middle line:84%
That will only become
helpful when we

00:08:03.700 --> 00:08:05.170 align:middle line:90%
get to the exploitation phase.

00:08:05.170 --> 00:08:07.520 align:middle line:84%
We are looking for
the auxiliary module.

00:08:07.520 --> 00:08:08.020 align:middle line:90%
Right?

00:08:08.020 --> 00:08:09.500 align:middle line:90%
So this is the one here.

00:08:09.500 --> 00:08:12.870 align:middle line:84%
So as you can see,
auxiliary/scanner/smb/smb ms17

00:08:12.870 --> 00:08:15.190 align:middle line:90%
0101.

00:08:15.190 --> 00:08:17.990 align:middle line:90%
This performs the RCE detection.

00:08:17.990 --> 00:08:20.600 align:middle line:84%
So this will tell us whether
the target is indeed vulnerable.

00:08:20.600 --> 00:08:22.870 align:middle line:84%
And this is very
important to run

00:08:22.870 --> 00:08:26.120 align:middle line:84%
or to check before you start
throwing exploits at a target.

00:08:26.120 --> 00:08:27.340 align:middle line:90%
So we can say use--

00:08:27.340 --> 00:08:29.290 align:middle line:90%
paste in the module name there.

00:08:29.290 --> 00:08:31.820 align:middle line:84%
I can then show the
options that are required.

00:08:31.820 --> 00:08:34.720 align:middle line:84%
And in this case, the only
option that I need to specify

00:08:34.720 --> 00:08:36.799 align:middle line:90%
is the target IP address.

00:08:36.799 --> 00:08:38.950 align:middle line:90%
So I can say set RHOSTS.

00:08:38.950 --> 00:08:43.830 align:middle line:84%
And in this case, the
target IP is 10.10.10.7.

00:08:43.830 --> 00:08:44.400 align:middle line:90%
There we are.

00:08:44.400 --> 00:08:47.700 align:middle line:90%
And I can then hit run.

00:08:47.700 --> 00:08:49.140 align:middle line:90%
Give that a couple of seconds.

00:08:49.140 --> 00:08:51.270 align:middle line:84%
As you can see, it'll
tell you right over here,

00:08:51.270 --> 00:08:55.710 align:middle line:84%
the host is likely vulnerable
to MS17-010 Windows.

00:08:55.710 --> 00:08:59.070 align:middle line:84%
And then it provides us with
the actual specific version

00:08:59.070 --> 00:09:01.290 align:middle line:84%
of Windows that's running
on the target as well

00:09:01.290 --> 00:09:02.740 align:middle line:90%
as the architecture.

00:09:02.740 --> 00:09:06.750 align:middle line:84%
So it's running Windows
7 Ultimate, Build 7601,

00:09:06.750 --> 00:09:09.970 align:middle line:84%
Service Pack 1,
and it is 64-bit.

00:09:09.970 --> 00:09:13.020 align:middle line:84%
So now that we've confirmed
that this target is indeed

00:09:13.020 --> 00:09:16.117 align:middle line:84%
vulnerable, we can now move
on to the exploitation phase.

00:09:16.117 --> 00:09:18.450 align:middle line:84%
Now as I said, I really don't
want to cover exploitation

00:09:18.450 --> 00:09:18.970 align:middle line:90%
right now.

00:09:18.970 --> 00:09:22.060 align:middle line:84%
But again, just to show you
that this does indeed work,

00:09:22.060 --> 00:09:24.540 align:middle line:84%
I can utilize the
EternalBlue exploit now.

00:09:24.540 --> 00:09:26.130 align:middle line:90%
So I'll copy that to there.

00:09:26.130 --> 00:09:29.040 align:middle line:84%
And I'll say use--
paste that in there.

00:09:29.040 --> 00:09:34.440 align:middle line:84%
And I can set the target
IP to RHOSTS 10.10.10.7.

00:09:34.440 --> 00:09:37.320 align:middle line:84%
I will not change the
default payload because it

00:09:37.320 --> 00:09:38.800 align:middle line:90%
is appropriate in this case.

00:09:38.800 --> 00:09:41.460 align:middle line:84%
This is the 64-bit
meterpreter module.

00:09:41.460 --> 00:09:43.320 align:middle line:90%
And I can then hit exploit.

00:09:43.320 --> 00:09:45.150 align:middle line:84%
However, before I do
that, I would still

00:09:45.150 --> 00:09:47.680 align:middle line:84%
need to configure
the payload options.

00:09:47.680 --> 00:09:49.260 align:middle line:84%
So in this case,
the payload options

00:09:49.260 --> 00:09:51.900 align:middle line:90%
have been set correctly.

00:09:51.900 --> 00:09:55.110 align:middle line:84%
This is the Kali Linux
IP address, in my case.

00:09:55.110 --> 00:09:57.360 align:middle line:84%
And this is the L
port, the default L

00:09:57.360 --> 00:09:58.650 align:middle line:90%
port that's been specified.

00:09:58.650 --> 00:10:01.630 align:middle line:84%
I will not change that
because, again, in my case,

00:10:01.630 --> 00:10:03.840 align:middle line:84%
I don't have anything,
any service that's

00:10:03.840 --> 00:10:06.636 align:middle line:90%
currently utilizing port 4444.

00:10:06.636 --> 00:10:10.370 align:middle line:90%
So I can just hit exploit.

00:10:10.370 --> 00:10:12.200 align:middle line:84%
We'll give that a
couple of seconds.

00:10:12.200 --> 00:10:14.180 align:middle line:84%
Again, this particular
exploit module

00:10:14.180 --> 00:10:16.520 align:middle line:84%
will actually run the
auxiliary scanner module

00:10:16.520 --> 00:10:20.210 align:middle line:84%
to check and verify whether the
target is indeed vulnerable.

00:10:20.210 --> 00:10:22.940 align:middle line:84%
If it is not vulnerable,
then it will not go forward

00:10:22.940 --> 00:10:26.250 align:middle line:84%
or will not go through with the
actual exploitation process.

00:10:26.250 --> 00:10:28.670 align:middle line:84%
However, it's very
important to keep in mind

00:10:28.670 --> 00:10:31.520 align:middle line:84%
that most Metasploit
exploit modules have not

00:10:31.520 --> 00:10:34.310 align:middle line:84%
been designed this well
in that they will not

00:10:34.310 --> 00:10:36.020 align:middle line:84%
check whether the
target is indeed

00:10:36.020 --> 00:10:38.870 align:middle line:84%
vulnerable before running
the actual exploit.

00:10:38.870 --> 00:10:41.090 align:middle line:84%
Now in this case, we can
see that the exploitation

00:10:41.090 --> 00:10:42.260 align:middle line:90%
was successful.

00:10:42.260 --> 00:10:44.510 align:middle line:84%
And we were able to
obtain a meterpreter

00:10:44.510 --> 00:10:46.110 align:middle line:90%
session on the target system.

00:10:46.110 --> 00:10:47.720 align:middle line:90%
So I can say sysinfo.

00:10:47.720 --> 00:10:50.480 align:middle line:84%
And indeed, you can confirm
that the information obtained

00:10:50.480 --> 00:10:53.240 align:middle line:84%
from the auxiliary module
was indeed correct.

00:10:53.240 --> 00:10:57.830 align:middle line:84%
It is running Windows 7,
Build 7601, Service Pack 1.

00:10:57.830 --> 00:11:00.960 align:middle line:84%
And it is a 64-bit
version of Windows 7.

00:11:00.960 --> 00:11:01.460 align:middle line:90%
All right?

00:11:01.460 --> 00:11:04.730 align:middle line:84%
So that is going to conclude
the practical demonstration

00:11:04.730 --> 00:11:07.340 align:middle line:90%
side of this video.

00:11:07.340 --> 00:11:07.840 align:middle line:90%
All right.

00:11:07.840 --> 00:11:10.300 align:middle line:84%
So that concludes the
vulnerability scanning

00:11:10.300 --> 00:11:13.960 align:middle line:84%
and detection section
of this course.

00:11:13.960 --> 00:11:16.510 align:middle line:84%
If you want to learn more
about performing vulnerability

00:11:16.510 --> 00:11:18.670 align:middle line:84%
scanning with Metasploit,
you can take a look

00:11:18.670 --> 00:11:22.090 align:middle line:84%
at the Metasploit course, as
I did cover it quite in depth

00:11:22.090 --> 00:11:24.170 align:middle line:90%
within that particular course.

00:11:24.170 --> 00:11:26.140 align:middle line:84%
However, now that
we've identified

00:11:26.140 --> 00:11:29.770 align:middle line:84%
or we've learned how to identify
and detect vulnerabilities

00:11:29.770 --> 00:11:33.500 align:middle line:84%
on or within services that are
running on a target system,

00:11:33.500 --> 00:11:35.930 align:middle line:84%
we can move on to
the next section,

00:11:35.930 --> 00:11:39.250 align:middle line:84%
which will focus on the process
of searching for exploits.

00:11:39.250 --> 00:11:42.880 align:middle line:84%
And again, we will not be
relying on exploit modules

00:11:42.880 --> 00:11:44.470 align:middle line:90%
for the Metasploit Framework.

00:11:44.470 --> 00:11:50.320 align:middle line:84%
We'll also take a look at how
to identify publicly available

00:11:50.320 --> 00:11:53.590 align:middle line:84%
exploit code through
various legitimate sources,

00:11:53.590 --> 00:11:56.740 align:middle line:84%
and of course, how to utilize
the searchsploit utility

00:11:56.740 --> 00:12:00.310 align:middle line:84%
to search for exploits pertinent
to the actual service that

00:12:00.310 --> 00:12:02.170 align:middle line:90%
is running on a target system.

00:12:02.170 --> 00:12:04.240 align:middle line:84%
With that being
said, I'll see you

00:12:04.240 --> 00:12:07.050 align:middle line:84%
in the next section
of this course.

00:12:07.050 --> 00:12:08.000 align:middle line:90%