WEBVTT

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


00:00:03.423 --> 00:00:06.357 align:middle line:90%
[MUSIC PLAYING]

00:00:06.357 --> 00:00:09.780 align:middle line:90%


00:00:09.780 --> 00:00:12.870 align:middle line:90%
Targeting Microsoft IIS FTP.

00:00:12.870 --> 00:00:14.850 align:middle line:84%
In this video,
we'll be exploring

00:00:14.850 --> 00:00:17.910 align:middle line:84%
the process of targeting
the FTP server that's

00:00:17.910 --> 00:00:19.530 align:middle line:90%
running on the target system.

00:00:19.530 --> 00:00:24.210 align:middle line:84%
And let's see what we're able to
do in terms of gaining access.

00:00:24.210 --> 00:00:27.000 align:middle line:84%
And we'll also learn a
few interesting things

00:00:27.000 --> 00:00:30.490 align:middle line:84%
regarding how the target
system has been configured.

00:00:30.490 --> 00:00:34.110 align:middle line:84%
Now as I said, this video or
this section of the course

00:00:34.110 --> 00:00:35.850 align:middle line:90%
utilizes one lab environment.

00:00:35.850 --> 00:00:37.780 align:middle line:84%
And the target is
essentially the same.

00:00:37.780 --> 00:00:40.360 align:middle line:84%
If you have stopped
the lab environment,

00:00:40.360 --> 00:00:42.490 align:middle line:84%
remember that the target
IP will be different.

00:00:42.490 --> 00:00:45.990 align:middle line:84%
So go through the process
of essentially identifying

00:00:45.990 --> 00:00:47.130 align:middle line:90%
the target IP.

00:00:47.130 --> 00:00:49.830 align:middle line:84%
And then, of course, if you
still have your results,

00:00:49.830 --> 00:00:52.980 align:middle line:84%
or you've stored them
externally or within your note

00:00:52.980 --> 00:00:56.530 align:middle line:84%
taking application, then you
can use that as a guideline.

00:00:56.530 --> 00:00:59.550 align:middle line:84%
So again, given
the infrastructure

00:00:59.550 --> 00:01:00.930 align:middle line:84%
of the lab
environment, just make

00:01:00.930 --> 00:01:03.690 align:middle line:84%
sure that you understand
that whenever you terminate

00:01:03.690 --> 00:01:06.120 align:middle line:84%
a lab, whenever you
start it up again,

00:01:06.120 --> 00:01:07.590 align:middle line:90%
the target IP will be changed.

00:01:07.590 --> 00:01:08.965 align:middle line:84%
But the services
remain the same.

00:01:08.965 --> 00:01:10.507 align:middle line:84%
And the ports that
they're running on

00:01:10.507 --> 00:01:11.565 align:middle line:90%
will remain the same.

00:01:11.565 --> 00:01:12.940 align:middle line:84%
So I just wanted
to mention that.

00:01:12.940 --> 00:01:16.230 align:middle line:84%
So I'm just going to switch
over into the lab environment.

00:01:16.230 --> 00:01:18.960 align:middle line:84%
And we can take a
look at how to exploit

00:01:18.960 --> 00:01:23.663 align:middle line:84%
or how to target Microsoft
IIS FTP or the FTP server

00:01:23.663 --> 00:01:24.580 align:middle line:90%
running on the target.

00:01:24.580 --> 00:01:27.570 align:middle line:90%
So let me switch over.

00:01:27.570 --> 00:01:28.070 align:middle line:90%
All right.

00:01:28.070 --> 00:01:30.320 align:middle line:84%
So I'm back within
the lab environment.

00:01:30.320 --> 00:01:32.000 align:middle line:84%
And in the previous
video, we explored

00:01:32.000 --> 00:01:35.000 align:middle line:84%
the process of performing
port scanning and enumeration.

00:01:35.000 --> 00:01:37.040 align:middle line:84%
And we were able
to identify that we

00:01:37.040 --> 00:01:41.780 align:middle line:84%
have port 21 open, that's
running Microsoft ftp, and port

00:01:41.780 --> 00:01:42.350 align:middle line:90%
80 open.

00:01:42.350 --> 00:01:44.600 align:middle line:84%
I'll just perform the
scan on these two ports,

00:01:44.600 --> 00:01:46.525 align:middle line:84%
as that's what we're
going to be targeting.

00:01:46.525 --> 00:01:48.150 align:middle line:84%
And you might be
asking yourself, well,

00:01:48.150 --> 00:01:50.510 align:middle line:90%
why am I also scanning port 80?

00:01:50.510 --> 00:01:53.870 align:middle line:84%
Well, the way Microsoft IIS
works, more specifically

00:01:53.870 --> 00:01:55.640 align:middle line:90%
on Windows Server--

00:01:55.640 --> 00:01:58.760 align:middle line:84%
and of course, we already
know what Microsoft IIS is.

00:01:58.760 --> 00:02:01.520 align:middle line:84%
It's a web server that's
used to host web applications

00:02:01.520 --> 00:02:03.540 align:middle line:90%
or website, et cetera.

00:02:03.540 --> 00:02:06.200 align:middle line:90%
And Microsoft FTP is a package.

00:02:06.200 --> 00:02:10.250 align:middle line:84%
Or it's part of the Microsoft
IIS package in its own

00:02:10.250 --> 00:02:12.540 align:middle line:90%
or the Microsoft IIS solution.

00:02:12.540 --> 00:02:15.410 align:middle line:84%
So in the context, or
in any event whenever

00:02:15.410 --> 00:02:19.280 align:middle line:84%
you see Microsoft ftp, and
that's very specific, ftpd

00:02:19.280 --> 00:02:24.050 align:middle line:84%
means FTP Daemon, and you also
see a Microsoft IIS web server,

00:02:24.050 --> 00:02:26.880 align:middle line:84%
it really means
one of two things.

00:02:26.880 --> 00:02:29.450 align:middle line:84%
Number one, it means
that they're both

00:02:29.450 --> 00:02:30.500 align:middle line:90%
intertwined in that.

00:02:30.500 --> 00:02:36.170 align:middle line:84%
The ftp server is used to allow
authenticated users to modify

00:02:36.170 --> 00:02:37.850 align:middle line:90%
the web server directory.

00:02:37.850 --> 00:02:40.430 align:middle line:84%
And that's what you typically
see with websites or web

00:02:40.430 --> 00:02:44.960 align:middle line:84%
hosting companies is they
have a web server that's

00:02:44.960 --> 00:02:46.340 align:middle line:90%
hosting web applications.

00:02:46.340 --> 00:02:47.990 align:middle line:90%
And they also have ftp running.

00:02:47.990 --> 00:02:50.900 align:middle line:84%
And it's via ftp you
can essentially modify

00:02:50.900 --> 00:02:53.620 align:middle line:84%
or upload website files,
download website files,

00:02:53.620 --> 00:02:54.860 align:middle line:90%
et cetera, et cetera.

00:02:54.860 --> 00:02:58.740 align:middle line:84%
So if we revisit
the web application,

00:02:58.740 --> 00:03:02.370 align:middle line:84%
and you can see in my case,
the target IP has changed,

00:03:02.370 --> 00:03:05.690 align:middle line:84%
if we visit the web
application on port 80,

00:03:05.690 --> 00:03:08.840 align:middle line:84%
we can see that it's a very
simple web application that's

00:03:08.840 --> 00:03:10.250 align:middle line:90%
just hosting an image.

00:03:10.250 --> 00:03:15.020 align:middle line:84%
And we can perform a directory
brute force on the web server

00:03:15.020 --> 00:03:18.800 align:middle line:84%
or in order to identify
hidden directories and files.

00:03:18.800 --> 00:03:21.320 align:middle line:84%
But before we do that,
it'd be much better

00:03:21.320 --> 00:03:24.710 align:middle line:84%
if we can try and
target the ftp server.

00:03:24.710 --> 00:03:28.370 align:middle line:84%
But where do we start in
regards to exploiting ftp?

00:03:28.370 --> 00:03:32.600 align:middle line:84%
Well, we can start off by
identifying or performing

00:03:32.600 --> 00:03:34.400 align:middle line:84%
some basic
vulnerability detection.

00:03:34.400 --> 00:03:37.820 align:middle line:84%
And the first vulnerability I
want to check in regards to ftp

00:03:37.820 --> 00:03:41.090 align:middle line:84%
is whether anonymous ftp
access has been enabled.

00:03:41.090 --> 00:03:43.460 align:middle line:84%
Anonymous ftp access
is a configuration

00:03:43.460 --> 00:03:48.080 align:middle line:84%
that allows anyone to access
the ftp server without providing

00:03:48.080 --> 00:03:49.400 align:middle line:90%
legitimate credentials.

00:03:49.400 --> 00:03:52.430 align:middle line:84%
And the way you can test this is
either through an Nmap script.

00:03:52.430 --> 00:03:59.180 align:middle line:84%
So if I say an ls -al under
usr/share/nmap/scripts.

00:03:59.180 --> 00:04:01.190 align:middle line:84%
And let me make sure I
type that in incorrectly.

00:04:01.190 --> 00:04:02.330 align:middle line:90%
There were are, scripts.

00:04:02.330 --> 00:04:07.250 align:middle line:84%
And I can then grep and
look for ftp scripts here.

00:04:07.250 --> 00:04:08.690 align:middle line:90%
So let me just hit Enter.

00:04:08.690 --> 00:04:10.190 align:middle line:90%
That is a hyphen there.

00:04:10.190 --> 00:04:12.960 align:middle line:84%
You can see that we have
the ftp-anon script.

00:04:12.960 --> 00:04:16.327 align:middle line:84%
So in order to test this
particular ftp server

00:04:16.327 --> 00:04:18.410 align:middle line:84%
and see whether anonymous
access has been enabled,

00:04:18.410 --> 00:04:20.690 align:middle line:90%
we can say nmap -sV.

00:04:20.690 --> 00:04:22.250 align:middle line:90%
The port is 21.

00:04:22.250 --> 00:04:26.090 align:middle line:84%
And the script that we want
to use is going to be equal to

00:04:26.090 --> 00:04:28.880 align:middle line:90%
or is called ftp-anon.

00:04:28.880 --> 00:04:30.500 align:middle line:84%
And we can paste
in the target IP.

00:04:30.500 --> 00:04:32.990 align:middle line:84%
And let's see whether
anonymous access is enabled.

00:04:32.990 --> 00:04:36.140 align:middle line:84%
In this case, the script
doesn't return any results.

00:04:36.140 --> 00:04:39.830 align:middle line:84%
So we can also test it manually
by saying ftp or using the ftp

00:04:39.830 --> 00:04:43.760 align:middle line:84%
client, specifying the
target IP and the port

00:04:43.760 --> 00:04:45.020 align:middle line:90%
on which FTP is running.

00:04:45.020 --> 00:04:45.740 align:middle line:90%
We hit Enter.

00:04:45.740 --> 00:04:48.157 align:middle line:84%
You can see it's going to
prompt you to enter credentials.

00:04:48.157 --> 00:04:50.930 align:middle line:84%
So we can say anonymous
or just hit Enter.

00:04:50.930 --> 00:04:54.290 align:middle line:84%
And in this case, you can see
it says, Password required.

00:04:54.290 --> 00:04:54.980 align:middle line:90%
Hit anonymous.

00:04:54.980 --> 00:04:55.730 align:middle line:90%
Login failed.

00:04:55.730 --> 00:04:59.840 align:middle line:84%
So that means anonymous
ftp access is not

00:04:59.840 --> 00:05:01.890 align:middle line:90%
enabled, which is a good thing.

00:05:01.890 --> 00:05:04.520 align:middle line:84%
It looks like the administrator
has been doing his job.

00:05:04.520 --> 00:05:06.050 align:middle line:90%
So that's a very good thing.

00:05:06.050 --> 00:05:08.750 align:middle line:84%
Well, the next attack
that we can perform

00:05:08.750 --> 00:05:12.060 align:middle line:84%
is your typical SSH, or
rather, FTP brute force.

00:05:12.060 --> 00:05:13.970 align:middle line:84%
So again, performing
a brute force

00:05:13.970 --> 00:05:16.430 align:middle line:84%
can be done through the use
of the Metasploit framework.

00:05:16.430 --> 00:05:20.240 align:middle line:84%
Or you can do it with the holy
grail of brute forcing tools,

00:05:20.240 --> 00:05:21.410 align:middle line:90%
which is Hydra.

00:05:21.410 --> 00:05:24.410 align:middle line:84%
So we can utilize Hydra
to perform a brute force

00:05:24.410 --> 00:05:26.540 align:middle line:84%
on the FTP server
in order to identify

00:05:26.540 --> 00:05:29.780 align:middle line:84%
legitimate credentials that we
can then use to authenticate.

00:05:29.780 --> 00:05:32.330 align:middle line:90%
So we can say hydra.

00:05:32.330 --> 00:05:34.880 align:middle line:84%
And because we don't know
the username or the password,

00:05:34.880 --> 00:05:37.070 align:middle line:84%
we'll specify the word
list that contains

00:05:37.070 --> 00:05:39.230 align:middle line:84%
the usernames that we
would like to perform

00:05:39.230 --> 00:05:40.430 align:middle line:90%
the brute force with.

00:05:40.430 --> 00:05:42.470 align:middle line:84%
And the word list
that I'm going to use

00:05:42.470 --> 00:05:44.810 align:middle line:90%
is under usr/share/wordlists.

00:05:44.810 --> 00:05:47.570 align:middle line:84%
And under the
metasploit directory,

00:05:47.570 --> 00:05:49.340 align:middle line:84%
we are going to use
a word list called

00:05:49.340 --> 00:05:51.780 align:middle line:90%
unix_users for the users.

00:05:51.780 --> 00:05:55.160 align:middle line:84%
And then for the passwords
or the password list,

00:05:55.160 --> 00:05:57.770 align:middle line:84%
we are going to again
use the same directory.

00:05:57.770 --> 00:05:59.750 align:middle line:90%
So usr/share/wordlists.

00:05:59.750 --> 00:06:02.180 align:middle line:84%
And under metasploit,
we are going to use

00:06:02.180 --> 00:06:05.510 align:middle line:90%
unix_passwords.txt.

00:06:05.510 --> 00:06:08.720 align:middle line:84%
We then need to provide the
target IP address as well

00:06:08.720 --> 00:06:12.150 align:middle line:84%
as the protocol that we are
performing the brute force on,

00:06:12.150 --> 00:06:13.640 align:middle line:90%
which in this case is ftp.

00:06:13.640 --> 00:06:14.917 align:middle line:90%
And we can hit Enter.

00:06:14.917 --> 00:06:17.000 align:middle line:84%
And that's going to begin
performing a brute force

00:06:17.000 --> 00:06:18.660 align:middle line:90%
attack on the ftp server.

00:06:18.660 --> 00:06:20.510 align:middle line:84%
So let's see whether
we're able to identify

00:06:20.510 --> 00:06:23.990 align:middle line:84%
any legitimate credentials
that we can use to gain access

00:06:23.990 --> 00:06:25.100 align:middle line:90%
to the ftp server.

00:06:25.100 --> 00:06:26.855 align:middle line:84%
So I'll give this a
couple of seconds.

00:06:26.855 --> 00:06:29.320 align:middle line:90%


00:06:29.320 --> 00:06:29.820 align:middle line:90%
All right.

00:06:29.820 --> 00:06:31.195 align:middle line:84%
So after are a
couple of minutes,

00:06:31.195 --> 00:06:32.940 align:middle line:84%
it looks like we've
been able to identify

00:06:32.940 --> 00:06:34.680 align:middle line:90%
some legitimate credentials.

00:06:34.680 --> 00:06:36.900 align:middle line:84%
We have the username
administrator.

00:06:36.900 --> 00:06:38.560 align:middle line:90%
And the password is vagrant.

00:06:38.560 --> 00:06:39.060 align:middle line:90%
All right.

00:06:39.060 --> 00:06:42.660 align:middle line:84%
So again, that means,
and in the case of ftp

00:06:42.660 --> 00:06:45.480 align:middle line:84%
on Windows and, of
course, on Linux,

00:06:45.480 --> 00:06:49.090 align:middle line:84%
the credentials are actually
user accounts on the system.

00:06:49.090 --> 00:06:53.820 align:middle line:84%
So that means if we've been able
to identify the administrator,

00:06:53.820 --> 00:06:56.400 align:middle line:84%
the administrator password,
then this is pretty much,

00:06:56.400 --> 00:06:58.740 align:middle line:84%
I believe, the
password-- the username,

00:06:58.740 --> 00:07:01.710 align:middle line:84%
or rather the user account
on the Windows system.

00:07:01.710 --> 00:07:05.490 align:middle line:84%
Now the password might be
different in certain cases

00:07:05.490 --> 00:07:07.710 align:middle line:84%
unless the password
has been reused.

00:07:07.710 --> 00:07:09.720 align:middle line:84%
Now we can see that the
password is vagrant.

00:07:09.720 --> 00:07:12.540 align:middle line:84%
And from the previous
video from the Nmap scan,

00:07:12.540 --> 00:07:16.650 align:middle line:84%
we were able to identify that
the host name is also vagrant.

00:07:16.650 --> 00:07:19.080 align:middle line:84%
So we can also try
and see whether there

00:07:19.080 --> 00:07:20.850 align:middle line:84%
is a user account
called vagrant,

00:07:20.850 --> 00:07:23.050 align:middle line:84%
as it's being
reused quite a bit.

00:07:23.050 --> 00:07:25.530 align:middle line:84%
So I'll just terminate
the current brute force.

00:07:25.530 --> 00:07:28.470 align:middle line:84%
And we can get rid of
the usr wordlist here.

00:07:28.470 --> 00:07:32.830 align:middle line:84%
And let's see whether
there is any password

00:07:32.830 --> 00:07:34.920 align:middle line:90%
or any account called vagrant.

00:07:34.920 --> 00:07:38.340 align:middle line:84%
And if so, can we identify
some legitimate credentials

00:07:38.340 --> 00:07:39.730 align:middle line:90%
for that account?

00:07:39.730 --> 00:07:43.497 align:middle line:84%
So yeah, instead of
specifying the list there,

00:07:43.497 --> 00:07:45.580 align:middle line:84%
we're just going to say
that this is the username.

00:07:45.580 --> 00:07:48.390 align:middle line:84%
So instead of a
capital L, lowercase l,

00:07:48.390 --> 00:07:52.560 align:middle line:84%
That's going to start up
the brute force again.

00:07:52.560 --> 00:07:55.560 align:middle line:84%
Now do store these
credentials as, again, we'll

00:07:55.560 --> 00:07:57.660 align:middle line:84%
be testing them and
seeing whether they

00:07:57.660 --> 00:08:01.660 align:middle line:84%
can be used to essentially
login into other services.

00:08:01.660 --> 00:08:04.500 align:middle line:84%
The reason for that
is it all comes down

00:08:04.500 --> 00:08:08.040 align:middle line:84%
to the password reuse
vulnerability within companies,

00:08:08.040 --> 00:08:12.240 align:middle line:84%
where employees and individuals
tend to reuse passwords

00:08:12.240 --> 00:08:14.940 align:middle line:84%
for multiple services,
primarily because remembering

00:08:14.940 --> 00:08:17.040 align:middle line:84%
passwords is very
difficult. So make

00:08:17.040 --> 00:08:21.400 align:middle line:84%
sure to actually store
that information.

00:08:21.400 --> 00:08:24.420 align:middle line:84%
So it looks like no
valid passwords were

00:08:24.420 --> 00:08:26.100 align:middle line:90%
found for the user vagrant.

00:08:26.100 --> 00:08:30.330 align:middle line:84%
So let's see whether we
can change anything here,

00:08:30.330 --> 00:08:33.720 align:middle line:84%
because we currently have
the previous brute force that

00:08:33.720 --> 00:08:35.340 align:middle line:90%
has the Hydra restore files.

00:08:35.340 --> 00:08:36.960 align:middle line:90%
So I'll just hit Enter.

00:08:36.960 --> 00:08:41.340 align:middle line:84%
And we can also use the
option I to skip waiting.

00:08:41.340 --> 00:08:43.169 align:middle line:84%
So I'm just going to
do that right now.

00:08:43.169 --> 00:08:46.990 align:middle line:84%
That'll begin the brute
force attack there.

00:08:46.990 --> 00:08:49.660 align:middle line:84%
And we can also
utilize the unix_users

00:08:49.660 --> 00:08:54.430 align:middle line:84%
to see whether any of the
actual usernames are part

00:08:54.430 --> 00:08:56.080 align:middle line:90%
or can be password.

00:08:56.080 --> 00:08:59.890 align:middle line:84%
So again, this will all come
down to the various wordlists

00:08:59.890 --> 00:09:02.870 align:middle line:84%
that you actually
tend or choose to use.

00:09:02.870 --> 00:09:05.540 align:middle line:84%
So for example, for the
password list, we can say,

00:09:05.540 --> 00:09:09.760 align:middle line:84%
I want you to use unix_users
instead of passwords.

00:09:09.760 --> 00:09:13.553 align:middle line:84%
And let's see whether
the use of vagrant

00:09:13.553 --> 00:09:14.845 align:middle line:90%
has any legitimate credentials.

00:09:14.845 --> 00:09:15.730 align:middle line:90%
So I'll hit Enter.

00:09:15.730 --> 00:09:18.560 align:middle line:90%


00:09:18.560 --> 00:09:21.470 align:middle line:84%
And indeed, it looks like
there is a user called vagrant.

00:09:21.470 --> 00:09:24.200 align:middle line:84%
And we also get the password
for the user, which is vagrant.

00:09:24.200 --> 00:09:28.130 align:middle line:84%
So this administrator has been
quite lazy in that regard.

00:09:28.130 --> 00:09:31.400 align:middle line:84%
And this is something
that's not good.

00:09:31.400 --> 00:09:33.110 align:middle line:84%
So we'll save those
two credentials.

00:09:33.110 --> 00:09:35.060 align:middle line:84%
And again, I recommend
keeping these

00:09:35.060 --> 00:09:37.700 align:middle line:84%
within your note taking
application offline,

00:09:37.700 --> 00:09:39.680 align:middle line:84%
not within the lab
environment, as

00:09:39.680 --> 00:09:41.360 align:middle line:84%
if you terminate
the lab environment,

00:09:41.360 --> 00:09:42.810 align:middle line:90%
then you'll lose all the data.

00:09:42.810 --> 00:09:45.170 align:middle line:84%
So make sure you
keep note of these.

00:09:45.170 --> 00:09:49.430 align:middle line:84%
So we've identified
two user accounts,

00:09:49.430 --> 00:09:51.870 align:middle line:84%
administrator and vagrant,
and their password.

00:09:51.870 --> 00:09:54.410 align:middle line:84%
So we can actually log
in to the ftp server.

00:09:54.410 --> 00:09:58.010 align:middle line:84%
So I can say ftp and then
specify the target IP,

00:09:58.010 --> 00:10:00.470 align:middle line:84%
which, again, I
believe I had obtained

00:10:00.470 --> 00:10:04.520 align:middle line:84%
previously right over here when
performing the brute force.

00:10:04.520 --> 00:10:07.278 align:middle line:84%
If I can just find the
actual command here.

00:10:07.278 --> 00:10:07.820 align:middle line:90%
There we are.

00:10:07.820 --> 00:10:09.380 align:middle line:90%
That's the target IP.

00:10:09.380 --> 00:10:13.400 align:middle line:84%
So ftp, target IP,
the port, which is 21.

00:10:13.400 --> 00:10:15.830 align:middle line:84%
And we can try and log in
with administrator first.

00:10:15.830 --> 00:10:17.870 align:middle line:90%
So administrator.

00:10:17.870 --> 00:10:20.060 align:middle line:90%
And the password is vagrant.

00:10:20.060 --> 00:10:21.510 align:middle line:84%
And we've logged
in successfully.

00:10:21.510 --> 00:10:22.010 align:middle line:90%
All right.

00:10:22.010 --> 00:10:24.860 align:middle line:84%
So we are currently
utilizing the ftp client.

00:10:24.860 --> 00:10:27.900 align:middle line:84%
And the syntax for the
ftp client is very simple.

00:10:27.900 --> 00:10:33.080 align:middle line:84%
We can use the standard Unix
or Linux directory commands

00:10:33.080 --> 00:10:34.230 align:middle line:90%
or file system commands.

00:10:34.230 --> 00:10:36.140 align:middle line:84%
So for example,
if we say ls, you

00:10:36.140 --> 00:10:39.950 align:middle line:84%
can see that will list out the
contents of the ftp server.

00:10:39.950 --> 00:10:41.930 align:middle line:84%
So it looks like we
have a directory called

00:10:41.930 --> 00:10:44.930 align:middle line:90%
aspnet_client caidao.asp.

00:10:44.930 --> 00:10:47.070 align:middle line:84%
So it looks like there's
an asp file there,

00:10:47.070 --> 00:10:48.450 align:middle line:90%
which is very interesting.

00:10:48.450 --> 00:10:52.130 align:middle line:84%
We have the image
hahaha.jpg and index.html.

00:10:52.130 --> 00:10:54.090 align:middle line:90%
So I was right.

00:10:54.090 --> 00:10:57.920 align:middle line:84%
What this means is that the
ftp server directly takes us

00:10:57.920 --> 00:10:59.780 align:middle line:84%
to the directory
of the web server

00:10:59.780 --> 00:11:02.160 align:middle line:84%
or where the web
application is stored.

00:11:02.160 --> 00:11:03.710 align:middle line:84%
So if we go back
to the browser, you

00:11:03.710 --> 00:11:06.830 align:middle line:84%
can see that we have the
hahahah image right over here.

00:11:06.830 --> 00:11:08.570 align:middle line:84%
And that means
that we pretty much

00:11:08.570 --> 00:11:11.930 align:middle line:84%
can deface the web application
or modify the contents

00:11:11.930 --> 00:11:13.440 align:middle line:90%
of the web application.

00:11:13.440 --> 00:11:15.680 align:middle line:84%
Now in this case, the web
application being hosted

00:11:15.680 --> 00:11:16.620 align:middle line:90%
is very simple.

00:11:16.620 --> 00:11:20.090 align:middle line:84%
It doesn't have any data or
any configuration files that

00:11:20.090 --> 00:11:22.760 align:middle line:84%
could give us additional
information regarding what

00:11:22.760 --> 00:11:24.710 align:middle line:84%
we could do to
exploit the system

00:11:24.710 --> 00:11:28.490 align:middle line:84%
or to essentially gain
access to the system

00:11:28.490 --> 00:11:30.680 align:middle line:90%
and obtain a system shell.

00:11:30.680 --> 00:11:34.350 align:middle line:84%
But what we can do, we can see
that we have an asp file here.

00:11:34.350 --> 00:11:38.600 align:middle line:84%
Now Microsoft IIS supports
various file extensions.

00:11:38.600 --> 00:11:40.280 align:middle line:90%
And one of them is asp.

00:11:40.280 --> 00:11:43.620 align:middle line:84%
And that means that it can
actually execute asp files.

00:11:43.620 --> 00:11:45.870 align:middle line:84%
So let's see whether
that is indeed the case.

00:11:45.870 --> 00:11:49.370 align:middle line:90%
So we'll say caidao.asp.

00:11:49.370 --> 00:11:53.460 align:middle line:84%
And it looks like that
was executed successfully.

00:11:53.460 --> 00:11:57.140 align:middle line:84%
And again, the ftp client allows
us to download or upload files

00:11:57.140 --> 00:11:58.830 align:middle line:90%
to and from the ftp server.

00:11:58.830 --> 00:12:01.430 align:middle line:84%
So what we could do
now is try and generate

00:12:01.430 --> 00:12:04.130 align:middle line:84%
an asp reverse
shell with msfvenom

00:12:04.130 --> 00:12:07.220 align:middle line:84%
and then upload the
asp file or aspx

00:12:07.220 --> 00:12:11.003 align:middle line:84%
file onto the ftp server,
consequently the web server,

00:12:11.003 --> 00:12:12.920 align:middle line:84%
and then try and execute
it and see whether we

00:12:12.920 --> 00:12:14.500 align:middle line:90%
can obtain a reverse shell.

00:12:14.500 --> 00:12:17.660 align:middle line:84%
Now again, this might not
work or probably will not

00:12:17.660 --> 00:12:21.830 align:middle line:84%
work in most cases because
in certain cases, asp code,

00:12:21.830 --> 00:12:25.640 align:middle line:84%
is, again, confined
to execution,

00:12:25.640 --> 00:12:27.350 align:middle line:90%
to very simple execution.

00:12:27.350 --> 00:12:30.060 align:middle line:84%
And in the context of a reverse
shell, it might not work.

00:12:30.060 --> 00:12:32.510 align:middle line:84%
So what I'm going to do
here now is we'll just

00:12:32.510 --> 00:12:34.580 align:middle line:90%
exit from the ftp server.

00:12:34.580 --> 00:12:36.680 align:middle line:84%
And we can also test
and see whether we can

00:12:36.680 --> 00:12:38.060 align:middle line:90%
log in with the use of vagrant.

00:12:38.060 --> 00:12:40.010 align:middle line:90%
So vagrant vagrant.

00:12:40.010 --> 00:12:41.240 align:middle line:90%
And indeed, we can.

00:12:41.240 --> 00:12:42.930 align:middle line:90%
So we're verified that.

00:12:42.930 --> 00:12:45.200 align:middle line:84%
So what we can do
now is use msfvenom

00:12:45.200 --> 00:12:46.820 align:middle line:90%
to generate the asp payload.

00:12:46.820 --> 00:12:47.990 align:middle line:90%
So we'll say payload.

00:12:47.990 --> 00:12:50.750 align:middle line:84%
And we'll not use [INAUDIBLE]
payload because, again, that

00:12:50.750 --> 00:12:53.310 align:middle line:84%
will probably will
not get executed.

00:12:53.310 --> 00:12:58.400 align:middle line:84%
So we'll say, we'll just use a
simple windows/shell payload.

00:12:58.400 --> 00:13:01.880 align:middle line:84%
And this is going
to be reverse_tcp.

00:13:01.880 --> 00:13:04.160 align:middle line:84%
We then need to
specify our IP address.

00:13:04.160 --> 00:13:05.960 align:middle line:84%
This is going to be
your Kali Linux IP.

00:13:05.960 --> 00:13:08.690 align:middle line:84%
So I'll just open up
a new terminal here.

00:13:08.690 --> 00:13:11.510 align:middle line:84%
And it looks like
we have one opened.

00:13:11.510 --> 00:13:12.330 align:middle line:90%
That is Shell No.

00:13:12.330 --> 00:13:12.830 align:middle line:90%
1.

00:13:12.830 --> 00:13:13.380 align:middle line:90%
There we are.

00:13:13.380 --> 00:13:15.240 align:middle line:90%
So ifconfig.

00:13:15.240 --> 00:13:20.595 align:middle line:84%
And your IP address is going
to be the interface ethernet 1.

00:13:20.595 --> 00:13:22.080 align:middle line:90%
So I'll copy my IP.

00:13:22.080 --> 00:13:24.040 align:middle line:84%
Or in your case,
it'll be different.

00:13:24.040 --> 00:13:26.875 align:middle line:84%
And for the LPORT, I'll
just paste that in there.

00:13:26.875 --> 00:13:28.500 align:middle line:84%
For some reason, it
didn't paste there.

00:13:28.500 --> 00:13:31.560 align:middle line:84%
So I'll just split
this vertically here.

00:13:31.560 --> 00:13:32.580 align:middle line:90%
Let me get that again.

00:13:32.580 --> 00:13:33.990 align:middle line:90%
So I have config.

00:13:33.990 --> 00:13:35.430 align:middle line:90%
And I'll copy that there.

00:13:35.430 --> 00:13:37.590 align:middle line:90%
So LHOST is there.

00:13:37.590 --> 00:13:40.110 align:middle line:84%
And then LPORT, we'll
set that to 1234

00:13:40.110 --> 00:13:42.510 align:middle line:90%
for the purpose of simplicity.

00:13:42.510 --> 00:13:46.060 align:middle line:84%
And we'll leave this
terminal open here.

00:13:46.060 --> 00:13:48.690 align:middle line:84%
So the output format
is going to be asp.

00:13:48.690 --> 00:13:51.180 align:middle line:84%
And of course, I cover this
within the Metasploit Framework

00:13:51.180 --> 00:13:51.810 align:middle line:90%
course.

00:13:51.810 --> 00:13:54.990 align:middle line:84%
And we can now put
this into asp or aspx.

00:13:54.990 --> 00:13:58.290 align:middle line:84%
So let's do aspx because
that works better

00:13:58.290 --> 00:13:59.740 align:middle line:90%
in terms of execution.

00:13:59.740 --> 00:14:03.030 align:middle line:84%
So we'll generate
the aspx payload.

00:14:03.030 --> 00:14:05.970 align:middle line:84%
And we can then upload
it to the ftp server,

00:14:05.970 --> 00:14:07.980 align:middle line:84%
which, again, will just
be in the web server

00:14:07.980 --> 00:14:09.490 align:middle line:90%
directory itself.

00:14:09.490 --> 00:14:12.000 align:middle line:90%
So we can now log in via ftp.

00:14:12.000 --> 00:14:13.500 align:middle line:90%
And I'll use the vagrant user.

00:14:13.500 --> 00:14:16.600 align:middle line:90%


00:14:16.600 --> 00:14:18.400 align:middle line:90%
And let me just try that again.

00:14:18.400 --> 00:14:20.630 align:middle line:84%
I think I specified the
incorrect password there.

00:14:20.630 --> 00:14:23.920 align:middle line:90%
So vagrant and vagrant.

00:14:23.920 --> 00:14:24.650 align:middle line:90%
There we go.

00:14:24.650 --> 00:14:28.270 align:middle line:84%
And to upload a file to an
ftp server, we simply say put.

00:14:28.270 --> 00:14:30.190 align:middle line:84%
You then specify the
path to the file.

00:14:30.190 --> 00:14:32.900 align:middle line:84%
In this case, it's within my
current working directory.

00:14:32.900 --> 00:14:36.370 align:middle line:90%
So put shell.aspx.

00:14:36.370 --> 00:14:37.970 align:middle line:90%
It looks like that is done.

00:14:37.970 --> 00:14:41.680 align:middle line:84%
So if I say dir, you can
see we have shell.aspx.

00:14:41.680 --> 00:14:44.230 align:middle line:84%
So we can start up
msfconsole and set

00:14:44.230 --> 00:14:46.550 align:middle line:84%
up the handler, or the
listener, if you will,

00:14:46.550 --> 00:14:50.200 align:middle line:84%
that will receive the connection
if the aspx file is executed.

00:14:50.200 --> 00:14:54.900 align:middle line:84%
So we'll say use
and multi/handler.

00:14:54.900 --> 00:14:57.900 align:middle line:84%
We'll set the payload to the
one that we set when generating

00:14:57.900 --> 00:14:59.220 align:middle line:90%
the payload with msfvenom.

00:14:59.220 --> 00:15:03.570 align:middle line:84%
So that is
windows/shellmreverse_tcp.

00:15:03.570 --> 00:15:07.050 align:middle line:84%
And we then need to set the
LHOST to our IP address, which

00:15:07.050 --> 00:15:10.560 align:middle line:84%
I believe I copied, there we
are, and set the LPORT option

00:15:10.560 --> 00:15:14.330 align:middle line:90%
to 1234, what we did.

00:15:14.330 --> 00:15:15.350 align:middle line:90%
And we can hit Run.

00:15:15.350 --> 00:15:18.097 align:middle line:84%
And we can now try and
execute this via the browser.

00:15:18.097 --> 00:15:19.430 align:middle line:90%
So I'll navigate to the browser.

00:15:19.430 --> 00:15:22.800 align:middle line:84%
And we should be able
to access shell.aspx.

00:15:22.800 --> 00:15:24.590 align:middle line:84%
And if it's executed
successfully,

00:15:24.590 --> 00:15:27.980 align:middle line:84%
we should receive a reverse
shell on our handler.

00:15:27.980 --> 00:15:28.940 align:middle line:90%
So I'll hit Enter.

00:15:28.940 --> 00:15:30.920 align:middle line:84%
It looks like it's
being executed.

00:15:30.920 --> 00:15:33.510 align:middle line:84%
Although, I'm not really
sure whether it will be.

00:15:33.510 --> 00:15:35.990 align:middle line:84%
And in that case, it doesn't
mean that this is a dead end.

00:15:35.990 --> 00:15:38.220 align:middle line:84%
Yeah, you can see that
we have an error here.

00:15:38.220 --> 00:15:39.480 align:middle line:90%
And it's a runtime error.

00:15:39.480 --> 00:15:42.650 align:middle line:84%
So it says, An application
error occurred on the server.

00:15:42.650 --> 00:15:46.220 align:middle line:84%
The current custom error
settings for this application

00:15:46.220 --> 00:15:48.110 align:middle line:84%
prevent the details of
the application error

00:15:48.110 --> 00:15:49.500 align:middle line:90%
from being viewed remotely.

00:15:49.500 --> 00:15:51.770 align:middle line:84%
So we really can't
tell what's wrong.

00:15:51.770 --> 00:15:54.260 align:middle line:84%
You can also try and
generate an asp file itself.

00:15:54.260 --> 00:15:55.670 align:middle line:84%
But of course, as
I've said, I've

00:15:55.670 --> 00:15:58.570 align:middle line:84%
already tried that, given the
fact that I have experience

00:15:58.570 --> 00:15:59.570 align:middle line:90%
with this target system.

00:15:59.570 --> 00:16:01.010 align:middle line:90%
But that will not work.

00:16:01.010 --> 00:16:02.840 align:middle line:84%
All I'm trying to
highlight here is

00:16:02.840 --> 00:16:06.180 align:middle line:84%
that there are various attack
vectors that you can utilize.

00:16:06.180 --> 00:16:09.270 align:middle line:84%
So we have not been able
to get a reverse shell yet.

00:16:09.270 --> 00:16:11.270 align:middle line:84%
So let's just terminate
the handler there.

00:16:11.270 --> 00:16:14.420 align:middle line:84%
And I'm just going to exit
from msfconsole and exit

00:16:14.420 --> 00:16:15.470 align:middle line:90%
from that terminal.

00:16:15.470 --> 00:16:16.890 align:middle line:90%
So what else can we do?

00:16:16.890 --> 00:16:19.370 align:middle line:84%
Well, from the perspective
of a penetration test

00:16:19.370 --> 00:16:22.460 align:middle line:84%
and the company that we are
performing the pen test for,

00:16:22.460 --> 00:16:24.830 align:middle line:84%
this is already a
security vulnerability

00:16:24.830 --> 00:16:27.590 align:middle line:84%
and a breach of
the actual system

00:16:27.590 --> 00:16:30.920 align:middle line:84%
security in that if an attacker
would have gained access

00:16:30.920 --> 00:16:33.590 align:middle line:84%
to the ftp server,
and of course,

00:16:33.590 --> 00:16:36.890 align:middle line:84%
they have not been able
to gain a reverse shell,

00:16:36.890 --> 00:16:38.840 align:middle line:84%
they can-- the
next step for them

00:16:38.840 --> 00:16:40.940 align:middle line:90%
would be to deface the website.

00:16:40.940 --> 00:16:42.860 align:middle line:84%
So defacing the
website just means

00:16:42.860 --> 00:16:46.460 align:middle line:84%
modifying the web
application or downloading

00:16:46.460 --> 00:16:48.590 align:middle line:84%
client data or
information that's

00:16:48.590 --> 00:16:50.150 align:middle line:90%
stored within this directory.

00:16:50.150 --> 00:16:53.000 align:middle line:84%
And in the case of
defacing a website,

00:16:53.000 --> 00:16:58.310 align:middle line:84%
we can essentially just
modify index.html to highlight

00:16:58.310 --> 00:17:00.380 align:middle line:84%
the fact that the web
server has been hacked.

00:17:00.380 --> 00:17:03.560 align:middle line:84%
So in order to do that, I'll
say download index.html.

00:17:03.560 --> 00:17:06.160 align:middle line:90%


00:17:06.160 --> 00:17:07.150 align:middle line:90%
Oh, sorry.

00:17:07.150 --> 00:17:07.720 align:middle line:90%
Not download.

00:17:07.720 --> 00:17:08.680 align:middle line:90%
We need to say get.

00:17:08.680 --> 00:17:11.560 align:middle line:90%
So get index.html.

00:17:11.560 --> 00:17:14.869 align:middle line:84%
And it looks like the ftp
servers closed the connection.

00:17:14.869 --> 00:17:16.060 align:middle line:90%
So let's log in again.

00:17:16.060 --> 00:17:19.359 align:middle line:90%
We can say vagrant and vagrant.

00:17:19.359 --> 00:17:24.640 align:middle line:84%
And we can then
say get index.html.

00:17:24.640 --> 00:17:27.560 align:middle line:90%
And that is done.

00:17:27.560 --> 00:17:31.040 align:middle line:84%
And we can now open up a new
tab here or a new terminal.

00:17:31.040 --> 00:17:33.822 align:middle line:84%
So I'll just split
this vertically.

00:17:33.822 --> 00:17:35.780 align:middle line:84%
If you don't have access
to that functionality,

00:17:35.780 --> 00:17:37.560 align:middle line:90%
you can just create a new tab.

00:17:37.560 --> 00:17:40.670 align:middle line:84%
So this is stored
on our desktop.

00:17:40.670 --> 00:17:44.400 align:middle line:84%
The files will be stored under
the current working directory.

00:17:44.400 --> 00:17:47.600 align:middle line:84%
And in my case, it's under the
Win2k8 folder on my desktop.

00:17:47.600 --> 00:17:48.950 align:middle line:90%
So we have index.html.

00:17:48.950 --> 00:17:51.870 align:middle line:84%
So we can use vim to modify
it and say, for example,

00:17:51.870 --> 00:17:53.090 align:middle line:90%
you have been hacked.

00:17:53.090 --> 00:17:56.120 align:middle line:84%
And for example, under the
head or under the body,

00:17:56.120 --> 00:17:57.890 align:middle line:84%
we can just add that
message there just

00:17:57.890 --> 00:18:00.620 align:middle line:84%
to show you how that would
typically work or look like.

00:18:00.620 --> 00:18:02.540 align:middle line:84%
Now of course, in a
real penetration test,

00:18:02.540 --> 00:18:04.250 align:middle line:84%
you're obviously not
allowed to do that,

00:18:04.250 --> 00:18:08.570 align:middle line:84%
to actually modify
the actual application

00:18:08.570 --> 00:18:10.770 align:middle line:84%
or play around
with customer data.

00:18:10.770 --> 00:18:12.380 align:middle line:90%
So we can say h1.

00:18:12.380 --> 00:18:16.260 align:middle line:90%
And we can say Website Hacked.

00:18:16.260 --> 00:18:18.570 align:middle line:84%
And this is typically what
malicious attackers do.

00:18:18.570 --> 00:18:22.230 align:middle line:84%
So we can close the h1 tag
there because it's HTML.

00:18:22.230 --> 00:18:23.370 align:middle line:90%
Write and quit.

00:18:23.370 --> 00:18:27.958 align:middle line:84%
And we can then
say put index.html.

00:18:27.958 --> 00:18:28.500 align:middle line:90%
There we are.

00:18:28.500 --> 00:18:30.540 align:middle line:84%
If we list out the
contents of this directory,

00:18:30.540 --> 00:18:32.335 align:middle line:90%
that should be updated.

00:18:32.335 --> 00:18:33.210 align:middle line:90%
And we can test that.

00:18:33.210 --> 00:18:36.540 align:middle line:84%
Also, we can say reverse
there or reload the page.

00:18:36.540 --> 00:18:38.820 align:middle line:84%
And you can see that's
highlighted there, Hacked!!!

00:18:38.820 --> 00:18:41.730 align:middle line:84%
And we can, of course,
modify that further so

00:18:41.730 --> 00:18:43.320 align:middle line:90%
that it's much clearer.

00:18:43.320 --> 00:18:47.400 align:middle line:84%
And we can set the
background color to white.

00:18:47.400 --> 00:18:49.620 align:middle line:84%
And we can probably also
get rid of the image.

00:18:49.620 --> 00:18:50.970 align:middle line:90%
So I'll set that to--

00:18:50.970 --> 00:18:52.920 align:middle line:84%
we can set it to white
or red, something

00:18:52.920 --> 00:18:54.630 align:middle line:90%
that's more malicious.

00:18:54.630 --> 00:18:55.560 align:middle line:90%
Write and quit.

00:18:55.560 --> 00:18:57.160 align:middle line:90%
And again, just repeat that.

00:18:57.160 --> 00:18:58.950 align:middle line:90%
So put index.html.

00:18:58.950 --> 00:19:01.710 align:middle line:84%
So this is typically what a
web developer would be doing.

00:19:01.710 --> 00:19:02.940 align:middle line:90%
They have the website files.

00:19:02.940 --> 00:19:04.710 align:middle line:84%
And they can push
changes like so.

00:19:04.710 --> 00:19:06.580 align:middle line:84%
However, in this case,
we're the attacker.

00:19:06.580 --> 00:19:07.247 align:middle line:90%
So there we are.

00:19:07.247 --> 00:19:08.730 align:middle line:90%
You can see Website Hacked!!!

00:19:08.730 --> 00:19:11.490 align:middle line:84%
And what we can do as
a final thing is just

00:19:11.490 --> 00:19:15.610 align:middle line:84%
get rid of the actual image
itself, which is quite a lot.

00:19:15.610 --> 00:19:19.710 align:middle line:84%
So I'm just going to
highlight this and get rid

00:19:19.710 --> 00:19:20.710 align:middle line:90%
of the actual image.

00:19:20.710 --> 00:19:22.850 align:middle line:84%
So let me just do
that right now.

00:19:22.850 --> 00:19:23.350 align:middle line:90%
All right.

00:19:23.350 --> 00:19:26.470 align:middle line:84%
So I've modified or
edited out the image.

00:19:26.470 --> 00:19:28.920 align:middle line:84%
So if I reload the web page,
that should be gone now.

00:19:28.920 --> 00:19:32.580 align:middle line:84%
It looks like it's still
there for some reason.

00:19:32.580 --> 00:19:35.450 align:middle line:84%
Yeah, but again,
you get the idea.

00:19:35.450 --> 00:19:38.370 align:middle line:84%
An attacker would typically
be able to modify the web

00:19:38.370 --> 00:19:39.060 align:middle line:90%
application.

00:19:39.060 --> 00:19:42.780 align:middle line:84%
And of course, if it stores
customer data locally,

00:19:42.780 --> 00:19:45.640 align:middle line:84%
then that information
can also be obtained.

00:19:45.640 --> 00:19:46.140 align:middle line:90%
All right?

00:19:46.140 --> 00:19:49.480 align:middle line:84%
So that is how to
target the ftp service.

00:19:49.480 --> 00:19:52.860 align:middle line:84%
As I said, we have not really
got any other information apart

00:19:52.860 --> 00:19:55.470 align:middle line:84%
from the credentials
we were able to gather.

00:19:55.470 --> 00:19:58.890 align:middle line:84%
And these, of course, are
pertinent to local accounts

00:19:58.890 --> 00:19:59.980 align:middle line:90%
on the Windows system.

00:19:59.980 --> 00:20:01.860 align:middle line:84%
So we've identified
two user accounts

00:20:01.860 --> 00:20:04.440 align:middle line:84%
on the system, one of
which is the administrator

00:20:04.440 --> 00:20:06.720 align:middle line:84%
and the other one
is the user vagrant.

00:20:06.720 --> 00:20:09.690 align:middle line:84%
And these credentials,
again, can be very useful

00:20:09.690 --> 00:20:12.060 align:middle line:84%
in terms of password
reuse tests,

00:20:12.060 --> 00:20:14.100 align:middle line:84%
where we can test
other services and see

00:20:14.100 --> 00:20:15.630 align:middle line:90%
whether these passwords work.

00:20:15.630 --> 00:20:18.420 align:middle line:84%
So that is going to conclude
the practical demonstration

00:20:18.420 --> 00:20:20.600 align:middle line:90%
side of this video.

00:20:20.600 --> 00:20:21.100 align:middle line:90%
All right.

00:20:21.100 --> 00:20:24.760 align:middle line:84%
So we've taken a look at how
to target the ftp server,

00:20:24.760 --> 00:20:28.360 align:middle line:84%
more specifically the
Microsoft IIS FTP server.

00:20:28.360 --> 00:20:30.940 align:middle line:84%
And we really didn't get
anything useful apart

00:20:30.940 --> 00:20:32.200 align:middle line:90%
from credentials.

00:20:32.200 --> 00:20:35.710 align:middle line:84%
And of course, from a
pen tester's perspective,

00:20:35.710 --> 00:20:38.710 align:middle line:84%
we have already compromised
the system to an extent.

00:20:38.710 --> 00:20:43.270 align:middle line:84%
And that particular
access gave us

00:20:43.270 --> 00:20:46.570 align:middle line:84%
the ability to
modify the actual web

00:20:46.570 --> 00:20:50.450 align:middle line:84%
application that's being hosted
on the web server on port 80.

00:20:50.450 --> 00:20:50.950 align:middle line:90%
All right.

00:20:50.950 --> 00:20:52.325 align:middle line:84%
So in the next
video, we're going

00:20:52.325 --> 00:20:54.750 align:middle line:84%
to be taking a look at how to
target the open SSH service.

00:20:54.750 --> 00:20:56.500 align:middle line:84%
And we'll see whether
this will provide us

00:20:56.500 --> 00:20:59.750 align:middle line:84%
with any form of access
on the target system.

00:20:59.750 --> 00:21:02.190 align:middle line:90%
So I'll see you there.

00:21:02.190 --> 00:21:03.000 align:middle line:90%