WEBVTT

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


00:00:10.180 --> 00:00:14.110 align:middle line:84%
Exploiting a Vulnerable
HTTP File Server.

00:00:14.110 --> 00:00:16.329 align:middle line:84%
Welcome to the
Exploitation section

00:00:16.329 --> 00:00:18.730 align:middle line:84%
of this course, where
we will be exploring

00:00:18.730 --> 00:00:21.700 align:middle line:84%
the process of exploiting
vulnerable services

00:00:21.700 --> 00:00:24.160 align:middle line:84%
on both Windows
and Linux systems.

00:00:24.160 --> 00:00:26.170 align:middle line:84%
And to start off, we
are going to explore

00:00:26.170 --> 00:00:30.440 align:middle line:84%
the process of exploiting a
vulnerable HTTP File Server.

00:00:30.440 --> 00:00:34.610 align:middle line:84%
So first and foremost, what
is an HTTP File Server?

00:00:34.610 --> 00:00:38.350 align:middle line:84%
Well, an HTTP File Server,
also known as an HFS,

00:00:38.350 --> 00:00:42.700 align:middle line:84%
is a web server that is designed
for file and document sharing.

00:00:42.700 --> 00:00:45.820 align:middle line:84%
Now, the difference, or
the primary difference

00:00:45.820 --> 00:00:49.090 align:middle line:84%
between an HTTP File Server
and a typical web server

00:00:49.090 --> 00:00:52.390 align:middle line:84%
comes down to the actual
features list available.

00:00:52.390 --> 00:00:55.570 align:middle line:84%
So the HTTP File
Server is specifically

00:00:55.570 --> 00:00:58.630 align:middle line:84%
designed to host
and share documents

00:00:58.630 --> 00:00:59.900 align:middle line:90%
and files for download.

00:00:59.900 --> 00:01:02.110 align:middle line:84%
So that's what it's
typically designed to do.

00:01:02.110 --> 00:01:05.050 align:middle line:84%
And it really doesn't
offer much in regards

00:01:05.050 --> 00:01:06.190 align:middle line:90%
to other web servers.

00:01:06.190 --> 00:01:09.490 align:middle line:84%
So you can't host a website
on the HTTP File Server,

00:01:09.490 --> 00:01:11.950 align:middle line:84%
you're just hosting
files and documents

00:01:11.950 --> 00:01:14.590 align:middle line:84%
that you want to share
with users around the world

00:01:14.590 --> 00:01:15.430 align:middle line:90%
or on the internet.

00:01:15.430 --> 00:01:18.140 align:middle line:84%
And they can then again,
download those files.

00:01:18.140 --> 00:01:20.290 align:middle line:84%
So again, that's the
primary difference

00:01:20.290 --> 00:01:23.200 align:middle line:84%
between an HTTP File Server
and a typical web server.

00:01:23.200 --> 00:01:25.420 align:middle line:84%
So a web server can
be utilized again

00:01:25.420 --> 00:01:27.460 align:middle line:84%
to share files and
documents, but it can also

00:01:27.460 --> 00:01:29.750 align:middle line:90%
be utilized to host a website.

00:01:29.750 --> 00:01:33.920 align:middle line:84%
So that's the key difference
that you need to keep in mind.

00:01:33.920 --> 00:01:36.490 align:middle line:84%
Other than that, they
all operate the same

00:01:36.490 --> 00:01:38.470 align:middle line:84%
in regards to the
fact that they utilize

00:01:38.470 --> 00:01:41.830 align:middle line:84%
the HTTP protocol for the
underlying communication.

00:01:41.830 --> 00:01:44.440 align:middle line:84%
And HTTP file servers
will typically

00:01:44.440 --> 00:01:48.310 align:middle line:84%
run on TCP port 80-- that's
the quickest way of actually

00:01:48.310 --> 00:01:49.372 align:middle line:90%
recognizing one.

00:01:49.372 --> 00:01:50.830 align:middle line:84%
And they'll
essentially provide you

00:01:50.830 --> 00:01:54.880 align:middle line:84%
with a list of files or
documents that have been shared

00:01:54.880 --> 00:01:56.120 align:middle line:90%
and that can be downloaded.

00:01:56.120 --> 00:01:59.320 align:middle line:84%
So they're really very simple
in regards to the functionality

00:01:59.320 --> 00:02:00.430 align:middle line:90%
that they offer.

00:02:00.430 --> 00:02:05.380 align:middle line:84%
Now, when it comes down
to HTTP File Servers, what

00:02:05.380 --> 00:02:07.840 align:middle line:84%
services or softwares
are out there that

00:02:07.840 --> 00:02:11.740 align:middle line:84%
actually allow us to, again,
set up an HTTP File Server?

00:02:11.740 --> 00:02:16.030 align:middle line:84%
For example, in the case
of a typical web server,

00:02:16.030 --> 00:02:19.570 align:middle line:84%
we have our servers
like Apache NGINX,

00:02:19.570 --> 00:02:22.150 align:middle line:90%
Microsoft IaaS to name a few.

00:02:22.150 --> 00:02:24.970 align:middle line:84%
In the case of
HTTP File Servers,

00:02:24.970 --> 00:02:30.190 align:middle line:84%
a popular HTTP File Server is
the Rejetto HFS or HTTP File

00:02:30.190 --> 00:02:31.015 align:middle line:90%
Server.

00:02:31.015 --> 00:02:34.900 align:middle line:84%
The Rejetto HFS is a
popular free and open source

00:02:34.900 --> 00:02:38.650 align:middle line:84%
HTTP File Server that can be set
up on both Windows and Linux.

00:02:38.650 --> 00:02:42.010 align:middle line:84%
It's extremely simple to set
up and it allows you to easily

00:02:42.010 --> 00:02:45.700 align:middle line:84%
share files and documents
locally on your local network,

00:02:45.700 --> 00:02:47.710 align:middle line:84%
as well as online
on the internet.

00:02:47.710 --> 00:02:49.990 align:middle line:84%
So you can essentially
just set it up,

00:02:49.990 --> 00:02:53.080 align:middle line:84%
specify the files and documents
that you want to share.

00:02:53.080 --> 00:02:55.090 align:middle line:84%
And once that is done,
they're essentially

00:02:55.090 --> 00:02:58.060 align:middle line:84%
shared within that
particular directory or URL

00:02:58.060 --> 00:03:01.960 align:middle line:84%
and can be accessed by again,
entering or heading over

00:03:01.960 --> 00:03:04.090 align:middle line:84%
to your browser, typing
in the IP address

00:03:04.090 --> 00:03:06.280 align:middle line:90%
of the domain of the website.

00:03:06.280 --> 00:03:09.190 align:middle line:84%
And then, of course,
on port 80 or port 443,

00:03:09.190 --> 00:03:11.470 align:middle line:84%
based on whether or not
there is an SSL certificate,

00:03:11.470 --> 00:03:15.250 align:middle line:84%
you'll get a listing of the
files that you can download.

00:03:15.250 --> 00:03:18.820 align:middle line:84%
Now, when we talk
about the Rejetto HFS,

00:03:18.820 --> 00:03:23.710 align:middle line:84%
version 2.3 of Rejetto HFS is
vulnerable to a remote code

00:03:23.710 --> 00:03:26.800 align:middle line:84%
or remote command execution
attack that can essentially

00:03:26.800 --> 00:03:30.310 align:middle line:84%
allow attackers to remotely
execute arbitrary commands

00:03:30.310 --> 00:03:32.770 align:middle line:90%
on the target operating system.

00:03:32.770 --> 00:03:35.140 align:middle line:84%
Luckily for us, the
Metasploit framework

00:03:35.140 --> 00:03:36.820 align:middle line:84%
has an exploit
module that we can

00:03:36.820 --> 00:03:40.550 align:middle line:84%
utilize to gain access to the
target system hosting Rejetto

00:03:40.550 --> 00:03:41.320 align:middle line:90%
HFS.

00:03:41.320 --> 00:03:45.490 align:middle line:84%
So if the target system is
running Rejetto HFS 2.3,

00:03:45.490 --> 00:03:48.370 align:middle line:84%
we can utilize the
Metasploit framework module

00:03:48.370 --> 00:03:50.560 align:middle line:84%
to essentially obtain
a Meterpreter session

00:03:50.560 --> 00:03:52.150 align:middle line:90%
on the target system.

00:03:52.150 --> 00:03:54.460 align:middle line:84%
Now, the exploitation
process is going

00:03:54.460 --> 00:03:56.890 align:middle line:84%
to be a combination of
all the previous sections

00:03:56.890 --> 00:03:57.730 align:middle line:90%
that we've explored.

00:03:57.730 --> 00:03:59.980 align:middle line:84%
So first and foremost,
when we head over

00:03:59.980 --> 00:04:01.810 align:middle line:84%
into the lab
environment, we are going

00:04:01.810 --> 00:04:04.900 align:middle line:84%
to perform some port scanning
and enumeration on the target

00:04:04.900 --> 00:04:09.190 align:middle line:84%
to identify whether or not there
is an HTTP File Server running

00:04:09.190 --> 00:04:10.030 align:middle line:90%
on the target.

00:04:10.030 --> 00:04:13.210 align:middle line:84%
We are then going to enumerate
the actual version of the HTTP

00:04:13.210 --> 00:04:14.000 align:middle line:90%
File Server.

00:04:14.000 --> 00:04:17.950 align:middle line:84%
And in this case, it
should be Rejetto HFS 2.3.

00:04:17.950 --> 00:04:20.410 align:middle line:84%
We are then going to
again, load or search

00:04:20.410 --> 00:04:23.880 align:middle line:84%
for the relevant exploit module,
configure it, and then exploit

00:04:23.880 --> 00:04:24.380 align:middle line:90%
it.

00:04:24.380 --> 00:04:27.130 align:middle line:84%
And we should get a
Meterpreter session.

00:04:27.130 --> 00:04:29.320 align:middle line:84%
All right, so in
order to get started,

00:04:29.320 --> 00:04:31.310 align:middle line:84%
just start up your
lab environment

00:04:31.310 --> 00:04:34.330 align:middle line:84%
and we'll be able to explore
the process of exploiting

00:04:34.330 --> 00:04:36.460 align:middle line:90%
a vulnerable HTTP File Server.

00:04:36.460 --> 00:04:41.060 align:middle line:84%
So I'll see you within
the lab environment.

00:04:41.060 --> 00:04:43.980 align:middle line:84%
All right, so I'm back
in the lab environment.

00:04:43.980 --> 00:04:47.090 align:middle line:84%
And the target IP address
is conveniently stored

00:04:47.090 --> 00:04:50.120 align:middle line:84%
for us-- or actually,
displayed here

00:04:50.120 --> 00:04:54.510 align:middle line:84%
within the actual target IP
address document or TXT file.

00:04:54.510 --> 00:04:57.000 align:middle line:84%
So we can copy the
target IP address.

00:04:57.000 --> 00:04:59.400 align:middle line:84%
Of course, in your case,
it's going to be different.

00:04:59.400 --> 00:05:01.490 align:middle line:84%
We are then going to
open up a terminal.

00:05:01.490 --> 00:05:03.500 align:middle line:84%
And I'm just going
to maximize that.

00:05:03.500 --> 00:05:06.060 align:middle line:84%
And let me just zoom
in a little bit here.

00:05:06.060 --> 00:05:07.200 align:middle line:90%
So there we are.

00:05:07.200 --> 00:05:09.390 align:middle line:84%
And then the first
step, of course,

00:05:09.390 --> 00:05:12.800 align:middle line:84%
is to ensure that the PostgreSQL
database service is started.

00:05:12.800 --> 00:05:16.440 align:middle line:84%
So we can do that by typing
Service PostgreSQL Start.

00:05:16.440 --> 00:05:19.010 align:middle line:84%
That'll ensure that we can
communicate with the Metasploit

00:05:19.010 --> 00:05:21.860 align:middle line:84%
framework database and
create our workspaces.

00:05:21.860 --> 00:05:23.930 align:middle line:84%
We're then going to
type in MSFConsole

00:05:23.930 --> 00:05:27.750 align:middle line:84%
to start up the Metasploit
framework console.

00:05:27.750 --> 00:05:28.860 align:middle line:90%
Give that a few seconds.

00:05:28.860 --> 00:05:32.820 align:middle line:90%


00:05:32.820 --> 00:05:35.270 align:middle line:84%
We can then check the
status of the database

00:05:35.270 --> 00:05:38.360 align:middle line:84%
to ensure that we are
connected, and indeed we are.

00:05:38.360 --> 00:05:42.590 align:middle line:84%
We are then going to create a
workspace called HFS as we are

00:05:42.590 --> 00:05:44.820 align:middle line:90%
dealing with HFS exploitation.

00:05:44.820 --> 00:05:45.560 align:middle line:90%
So there we are.

00:05:45.560 --> 00:05:47.227 align:middle line:84%
As you can see, we
are currently working

00:05:47.227 --> 00:05:49.105 align:middle line:90%
within the HFS workspace.

00:05:49.105 --> 00:05:50.480 align:middle line:84%
The first thing
we're going to do

00:05:50.480 --> 00:05:53.720 align:middle line:84%
is set up the global
variable for the RHOST option

00:05:53.720 --> 00:05:56.810 align:middle line:84%
so that we don't need to
specify the target IP whenever

00:05:56.810 --> 00:05:58.855 align:middle line:90%
we want to load a module.

00:05:58.855 --> 00:05:59.480 align:middle line:90%
So that we are.

00:05:59.480 --> 00:06:01.580 align:middle line:84%
As you can see, that's
going to set RHOST

00:06:01.580 --> 00:06:04.190 align:middle line:84%
and it's going to set the
target IP for every module

00:06:04.190 --> 00:06:05.270 align:middle line:90%
that we load.

00:06:05.270 --> 00:06:06.830 align:middle line:84%
The next thing
we're going to do is

00:06:06.830 --> 00:06:08.870 align:middle line:84%
we're going to perform
an Nmap scan and store

00:06:08.870 --> 00:06:12.110 align:middle line:84%
the results directly into the
Metasploit framework database.

00:06:12.110 --> 00:06:13.730 align:middle line:84%
And as we've already
explored, this

00:06:13.730 --> 00:06:16.340 align:middle line:84%
can be done by using
the db_nmap command.

00:06:16.340 --> 00:06:19.370 align:middle line:84%
We're going to perform
a SYN scan and then

00:06:19.370 --> 00:06:23.420 align:middle line:84%
some service version detection,
as well as some operating

00:06:23.420 --> 00:06:24.380 align:middle line:90%
system detection.

00:06:24.380 --> 00:06:26.390 align:middle line:84%
And we're going to
paste in the IP there.

00:06:26.390 --> 00:06:28.370 align:middle line:84%
And that is going to
start the Nmap scan

00:06:28.370 --> 00:06:31.790 align:middle line:84%
and it'll actually store the
Nmap scan results directly

00:06:31.790 --> 00:06:33.980 align:middle line:84%
into the Metasploit
framework database

00:06:33.980 --> 00:06:35.540 align:middle line:90%
in our current workspace.

00:06:35.540 --> 00:06:37.820 align:middle line:84%
So we'll be able to analyze
the results directly

00:06:37.820 --> 00:06:39.020 align:middle line:90%
from MSFConsole.

00:06:39.020 --> 00:06:43.570 align:middle line:84%
So I'm just going to wait for
the Nmap scan to complete.

00:06:43.570 --> 00:06:45.400 align:middle line:84%
All right, the Nmap
scan is complete.

00:06:45.400 --> 00:06:49.440 align:middle line:84%
And as you can see, we have
the Rejetto HTTP File Server

00:06:49.440 --> 00:06:52.680 align:middle line:84%
version 2.3 running
on port 80, as well as

00:06:52.680 --> 00:06:54.150 align:middle line:90%
a few other services.

00:06:54.150 --> 00:06:57.600 align:middle line:84%
From the Nmap scan, we're
also able to deduce the target

00:06:57.600 --> 00:06:58.445 align:middle line:90%
operating system.

00:06:58.445 --> 00:06:59.820 align:middle line:84%
And in this case,
we can see it's

00:06:59.820 --> 00:07:03.520 align:middle line:84%
running Windows Server
2008 R2, which again,

00:07:03.520 --> 00:07:06.780 align:middle line:84%
is very important when we will
be specifying the Meterpreter

00:07:06.780 --> 00:07:10.230 align:middle line:84%
payload and the platform
that we want to utilize

00:07:10.230 --> 00:07:12.300 align:middle line:84%
with the Meterpreter
payload when again,

00:07:12.300 --> 00:07:14.230 align:middle line:90%
utilizing the exploit module.

00:07:14.230 --> 00:07:18.720 align:middle line:84%
Now that we have an idea of
what HTTP File Server is running

00:07:18.720 --> 00:07:21.300 align:middle line:84%
on the target system,
as well as the version,

00:07:21.300 --> 00:07:23.790 align:middle line:84%
we can search or perform
some vulnerability

00:07:23.790 --> 00:07:27.120 align:middle line:84%
scanning directly through
MSFConsole by saying Search

00:07:27.120 --> 00:07:29.760 align:middle line:84%
and then specifying
the type of a module.

00:07:29.760 --> 00:07:32.110 align:middle line:84%
And the type is going
to be an exploit module.

00:07:32.110 --> 00:07:34.620 align:middle line:84%
We can then specify the
name, which in this case,

00:07:34.620 --> 00:07:36.000 align:middle line:90%
is going to be Rejetto.

00:07:36.000 --> 00:07:38.940 align:middle line:84%
So we're going to say
Rejetto There we are.

00:07:38.940 --> 00:07:39.990 align:middle line:90%
Hit Enter.

00:07:39.990 --> 00:07:42.960 align:middle line:84%
And as you can see, we get the
appropriate exploit module.

00:07:42.960 --> 00:07:45.400 align:middle line:84%
And we can again, confirm
that by utilizing it.

00:07:45.400 --> 00:07:47.850 align:middle line:84%
So I'm just going to copy
the module name here.

00:07:47.850 --> 00:07:51.190 align:middle line:84%
And we're then going to
say Use, paste it in there.

00:07:51.190 --> 00:07:54.880 align:middle line:84%
And if we show the
options here, you

00:07:54.880 --> 00:07:57.760 align:middle line:84%
can see that it allows us to
specify the target IP, which

00:07:57.760 --> 00:07:59.410 align:middle line:84%
is already done
because we set up

00:07:59.410 --> 00:08:02.540 align:middle line:84%
the global variable
for the RHOST option.

00:08:02.540 --> 00:08:05.110 align:middle line:84%
And if you want to learn more
about this particular exploit

00:08:05.110 --> 00:08:07.730 align:middle line:84%
module, you can type
in the Info command.

00:08:07.730 --> 00:08:09.880 align:middle line:84%
And as you can see right
here under description,

00:08:09.880 --> 00:08:14.200 align:middle line:84%
you can see it says Rejetto HTTP
File Server, also known as HFS,

00:08:14.200 --> 00:08:16.360 align:middle line:84%
is vulnerable to a
remote command execution

00:08:16.360 --> 00:08:21.520 align:middle line:84%
attack due to a pour rejex
in the file ParserLib.pas.

00:08:21.520 --> 00:08:24.700 align:middle line:84%
This module exploits the
HFS scripting commands

00:08:24.700 --> 00:08:28.030 align:middle line:84%
by using the null byte
to bypass the filtering.

00:08:28.030 --> 00:08:33.130 align:middle line:84%
This module has been tested
successfully on HFS 2.3

00:08:33.130 --> 00:08:36.940 align:middle line:84%
over Windows XP service pack
3, Windows 7 service pack 1,

00:08:36.940 --> 00:08:38.080 align:middle line:90%
and Windows 8.

00:08:38.080 --> 00:08:41.860 align:middle line:84%
So this falls within the actual
category of operating systems

00:08:41.860 --> 00:08:44.710 align:middle line:84%
as a Windows Server
2008 was released

00:08:44.710 --> 00:08:48.310 align:middle line:84%
in between the releases of
Windows XP and Windows 7.

00:08:48.310 --> 00:08:52.730 align:middle line:84%
So in order to execute this
particular exploit module,

00:08:52.730 --> 00:08:56.110 align:middle line:84%
we can actually specify the
target IP and the target port,

00:08:56.110 --> 00:08:57.160 align:middle line:90%
which is done.

00:08:57.160 --> 00:09:02.410 align:middle line:84%
If we try and access the port
80 within our browser just

00:09:02.410 --> 00:09:05.360 align:middle line:84%
to confirm that we
indeed have HFS running,

00:09:05.360 --> 00:09:08.560 align:middle line:84%
which I'll do right now-- so
I'll paste in the IP in Firefox

00:09:08.560 --> 00:09:09.220 align:middle line:90%
here--

00:09:09.220 --> 00:09:12.970 align:middle line:84%
as you can see, this is
running HTTP File Server 2.3,

00:09:12.970 --> 00:09:14.770 align:middle line:90%
and it is running on port 80.

00:09:14.770 --> 00:09:18.230 align:middle line:84%
What we need to do now is,
of course, set our payload.

00:09:18.230 --> 00:09:20.800 align:middle line:84%
So the payload that we
are going to be utilizing

00:09:20.800 --> 00:09:23.890 align:middle line:84%
is the Windows
Meterpreter Reverse TCP

00:09:23.890 --> 00:09:26.980 align:middle line:84%
payload, as we require a
payload because one is not

00:09:26.980 --> 00:09:30.730 align:middle line:84%
specified by default.
If we try and run

00:09:30.730 --> 00:09:33.750 align:middle line:90%
this particular module as is--

00:09:33.750 --> 00:09:37.390 align:middle line:90%
give that a few seconds--

00:09:37.390 --> 00:09:39.400 align:middle line:84%
you can see that it
automatically opens up

00:09:39.400 --> 00:09:40.480 align:middle line:90%
a Meterpreter session.

00:09:40.480 --> 00:09:42.760 align:middle line:84%
And the reason for
that is fairly simple,

00:09:42.760 --> 00:09:44.570 align:middle line:84%
and I'll get to
that in a second.

00:09:44.570 --> 00:09:46.720 align:middle line:84%
But we get a Meterpreter
session on the target.

00:09:46.720 --> 00:09:49.270 align:middle line:84%
So if I type in
sysinfo, you can see

00:09:49.270 --> 00:09:52.300 align:middle line:84%
that this is a Windows
Server 2012 R2 box,

00:09:52.300 --> 00:09:54.610 align:middle line:84%
contrary to the
Nmap scan results

00:09:54.610 --> 00:09:58.630 align:middle line:84%
that were giving us an option
between Windows Server 2008

00:09:58.630 --> 00:10:00.460 align:middle line:90%
and Windows Server 2012.

00:10:00.460 --> 00:10:02.590 align:middle line:84%
So irregardless of
that, we were still

00:10:02.590 --> 00:10:05.500 align:middle line:84%
able to obtain a
Meterpreter session

00:10:05.500 --> 00:10:07.150 align:middle line:90%
without specifying a payload.

00:10:07.150 --> 00:10:11.860 align:middle line:84%
The reason that was the case is
because, as you can see here,

00:10:11.860 --> 00:10:16.810 align:middle line:84%
we have two options that we
can specify for this module.

00:10:16.810 --> 00:10:18.850 align:middle line:84%
This is the local
host to list it on.

00:10:18.850 --> 00:10:21.670 align:middle line:84%
This must be an address on
the local machine that's used

00:10:21.670 --> 00:10:23.750 align:middle line:90%
to deliver the actual payload.

00:10:23.750 --> 00:10:27.010 align:middle line:84%
So we can actually change
the actual type of payload

00:10:27.010 --> 00:10:29.500 align:middle line:84%
that we're utilizing based
on the operating system

00:10:29.500 --> 00:10:31.070 align:middle line:90%
architecture we want.

00:10:31.070 --> 00:10:33.520 align:middle line:84%
So if I terminate this
Meterpreter session--

00:10:33.520 --> 00:10:36.070 align:middle line:84%
if I say Exit and
then set the payload

00:10:36.070 --> 00:10:38.072 align:middle line:84%
to
windows/x64/meterpreter/reverse

00:10:38.072 --> 00:10:52.540 align:middle line:84%
tcp and show the options now,
we can then set the LPORT

00:10:52.540 --> 00:10:53.770 align:middle line:90%
and the LHOST options.

00:10:53.770 --> 00:10:56.860 align:middle line:84%
And the LHOST option is going
to be your IP address, your Kali

00:10:56.860 --> 00:10:58.250 align:middle line:90%
Linux IP address.

00:10:58.250 --> 00:11:01.780 align:middle line:84%
And then you can specify any
open port on the Kali Linux IP

00:11:01.780 --> 00:11:03.580 align:middle line:90%
to listen for the connection.

00:11:03.580 --> 00:11:11.695 align:middle line:84%
We can then hit Run, give
that a few seconds to open up

00:11:11.695 --> 00:11:12.695 align:middle line:90%
the Meterpreter session.

00:11:12.695 --> 00:11:17.220 align:middle line:90%


00:11:17.220 --> 00:11:19.430 align:middle line:84%
And if we type in
sysinfo, you can now

00:11:19.430 --> 00:11:22.460 align:middle line:84%
see we have a 64-bit
Meterpreter session as opposed

00:11:22.460 --> 00:11:26.330 align:middle line:84%
to previously, when the
default payload specified was

00:11:26.330 --> 00:11:28.760 align:middle line:90%
the 32-bit Meterpreter payload.

00:11:28.760 --> 00:11:30.590 align:middle line:84%
So again, you can
always customize

00:11:30.590 --> 00:11:34.640 align:middle line:84%
the payload you use for
every exploit module based

00:11:34.640 --> 00:11:38.840 align:middle line:84%
on the target operating system,
as well as the architecture.

00:11:38.840 --> 00:11:42.590 align:middle line:84%
All right, so that is how to
exploit a vulnerable HTTP File

00:11:42.590 --> 00:11:43.160 align:middle line:90%
Server.

00:11:43.160 --> 00:11:48.300 align:middle line:84%
And this will conclude the
practical demonstration.

00:11:48.300 --> 00:11:50.610 align:middle line:84%
In the next video, we
are going to be exploring

00:11:50.610 --> 00:11:52.950 align:middle line:84%
the process of exploiting
the EternalBlue

00:11:52.950 --> 00:11:56.160 align:middle line:84%
vulnerability on Windows,
which is an SMB exploit.

00:11:56.160 --> 00:11:59.030 align:middle line:90%
So I'll see you there.