WEBVTT

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


00:00:03.388 --> 00:00:06.776 align:middle line:90%
[MUSIC PLAYING]

00:00:06.776 --> 00:00:09.690 align:middle line:90%


00:00:09.690 --> 00:00:11.910 align:middle line:90%
Exploiting RDP.

00:00:11.910 --> 00:00:13.920 align:middle line:84%
Now that we've
taken a look at how

00:00:13.920 --> 00:00:17.130 align:middle line:84%
to exploit some of the
most frequently exploited

00:00:17.130 --> 00:00:21.630 align:middle line:84%
Windows services like IaaS
and WebDAV as well as SMB,

00:00:21.630 --> 00:00:25.360 align:middle line:84%
we can now turn our attention
to the RDP protocol.

00:00:25.360 --> 00:00:27.270 align:middle line:84%
However, before we
actually get started

00:00:27.270 --> 00:00:30.690 align:middle line:84%
with taking a look at how we can
attack or exploit the protocol,

00:00:30.690 --> 00:00:33.720 align:middle line:84%
let's get an understanding of
what it is and how it works.

00:00:33.720 --> 00:00:38.040 align:middle line:84%
So RDP stands for the
Remote Desktop Protocol.

00:00:38.040 --> 00:00:42.030 align:middle line:84%
It is a proprietary graphical
user interface remote access

00:00:42.030 --> 00:00:45.870 align:middle line:84%
protocol that is developed
or was developed by Microsoft

00:00:45.870 --> 00:00:49.050 align:middle line:84%
and is used to remotely connect
and interact with a Windows

00:00:49.050 --> 00:00:50.430 align:middle line:90%
system.

00:00:50.430 --> 00:00:55.560 align:middle line:84%
RDP uses TCP port 3389
default. However, it can also

00:00:55.560 --> 00:00:57.930 align:middle line:84%
be configured to run
on any other TCP port,

00:00:57.930 --> 00:01:01.350 align:middle line:84%
and that's something that you
want to be acutely aware of.

00:01:01.350 --> 00:01:05.550 align:middle line:84%
The reason for this is because
exploiting the RDP protocol

00:01:05.550 --> 00:01:07.360 align:middle line:90%
is relatively straightforward.

00:01:07.360 --> 00:01:09.000 align:middle line:84%
The typical attack
would essentially

00:01:09.000 --> 00:01:11.790 align:middle line:84%
involve performing a brute
force against the protocol

00:01:11.790 --> 00:01:14.040 align:middle line:84%
in order to identify
a user accounts

00:01:14.040 --> 00:01:15.990 align:middle line:90%
and their respective passwords.

00:01:15.990 --> 00:01:18.690 align:middle line:84%
And for that reasons,
many system administrators

00:01:18.690 --> 00:01:20.670 align:middle line:84%
have actually been
switching the default

00:01:20.670 --> 00:01:24.360 align:middle line:84%
or have been using another
port for the RDP protocol,

00:01:24.360 --> 00:01:26.340 align:middle line:84%
and they've been
switching it around.

00:01:26.340 --> 00:01:30.150 align:middle line:84%
So as a penetration
tester or as an attacker,

00:01:30.150 --> 00:01:31.560 align:middle line:90%
you must be aware of this.

00:01:31.560 --> 00:01:35.490 align:middle line:84%
And when performing your port
scanning and enumeration,

00:01:35.490 --> 00:01:37.290 align:middle line:84%
you should be
extremely comprehensive

00:01:37.290 --> 00:01:40.410 align:middle line:84%
because RDP could be running
on another port, not just

00:01:40.410 --> 00:01:43.500 align:middle line:90%
the default port, which is 3389.

00:01:43.500 --> 00:01:46.230 align:middle line:84%
All right, so in terms
of RDP authentication,

00:01:46.230 --> 00:01:49.450 align:middle line:84%
RDP authentication essentially
requires a legitimate user

00:01:49.450 --> 00:01:52.980 align:middle line:84%
account on the Windows target
as well as the user's password

00:01:52.980 --> 00:01:53.940 align:middle line:90%
in cleartext.

00:01:53.940 --> 00:01:56.490 align:middle line:84%
So this is something that's
very, very important.

00:01:56.490 --> 00:01:59.760 align:middle line:84%
In order to remotely
authenticate with RDP

00:01:59.760 --> 00:02:03.780 align:middle line:84%
on the target system, you
need to have a user account,

00:02:03.780 --> 00:02:08.280 align:middle line:84%
username, and password on that
system in order to gain access.

00:02:08.280 --> 00:02:10.289 align:middle line:84%
And the first
attack that we'll be

00:02:10.289 --> 00:02:12.720 align:middle line:84%
taking a look at in this
video is the process

00:02:12.720 --> 00:02:15.540 align:middle line:84%
of performing in RDP
brute-force attack

00:02:15.540 --> 00:02:18.510 align:middle line:84%
in order to identify legitimate
user credentials that we

00:02:18.510 --> 00:02:21.990 align:middle line:84%
can use to gain remote
access to the target system.

00:02:21.990 --> 00:02:24.540 align:middle line:84%
Now, most of you should
be familiar with RDP.

00:02:24.540 --> 00:02:26.280 align:middle line:84%
It's a very, very
simple protocol

00:02:26.280 --> 00:02:28.110 align:middle line:90%
in regards to how it works.

00:02:28.110 --> 00:02:30.300 align:middle line:84%
You essentially
utilize an RDP client

00:02:30.300 --> 00:02:32.550 align:middle line:84%
whether you're on
Windows or on Linux,

00:02:32.550 --> 00:02:35.730 align:middle line:84%
and you connect to the
target via the specified RDP

00:02:35.730 --> 00:02:37.770 align:middle line:90%
port or any other port.

00:02:37.770 --> 00:02:42.360 align:middle line:84%
And once you essentially
initiate the connection,

00:02:42.360 --> 00:02:46.530 align:middle line:84%
you'll essentially be provided
with a graphical user interface

00:02:46.530 --> 00:02:49.950 align:middle line:84%
of the target system, so a
standard Windows desktop,

00:02:49.950 --> 00:02:52.800 align:middle line:84%
after which you will be required
to authenticate with a username

00:02:52.800 --> 00:02:53.640 align:middle line:90%
and password.

00:02:53.640 --> 00:02:56.790 align:middle line:84%
So again, we can
always connect to RDP.

00:02:56.790 --> 00:02:58.770 align:middle line:84%
However, we'll need
legitimate credentials

00:02:58.770 --> 00:03:01.800 align:middle line:84%
in order to essentially
authenticate and gain access

00:03:01.800 --> 00:03:03.600 align:middle line:90%
to the target system.

00:03:03.600 --> 00:03:07.780 align:middle line:84%
And similarly to the
RDP exploitation videos,

00:03:07.780 --> 00:03:10.020 align:middle line:84%
we are going to be
limiting our attack

00:03:10.020 --> 00:03:11.850 align:middle line:84%
scope to the
administrator account

00:03:11.850 --> 00:03:14.580 align:middle line:84%
as the administrator account
has the highest privileges,

00:03:14.580 --> 00:03:17.100 align:middle line:84%
and gaining access to the
administrator's account

00:03:17.100 --> 00:03:19.260 align:middle line:84%
is pretty much
what we're looking

00:03:19.260 --> 00:03:21.600 align:middle line:84%
for because we don't have
to go through the process

00:03:21.600 --> 00:03:23.880 align:middle line:90%
of elevating our privileges.

00:03:23.880 --> 00:03:26.910 align:middle line:84%
So now that we have an
understanding of what RDP is

00:03:26.910 --> 00:03:29.610 align:middle line:84%
and the exploitation
technique that we'll

00:03:29.610 --> 00:03:32.100 align:middle line:84%
be exploring in this
video, we can get started

00:03:32.100 --> 00:03:33.370 align:middle line:90%
with the lab environment.

00:03:33.370 --> 00:03:35.860 align:middle line:84%
So all you need to do is just
fire up your lab environment,

00:03:35.860 --> 00:03:37.560 align:middle line:84%
and you can follow along
with the techniques

00:03:37.560 --> 00:03:38.730 align:middle line:90%
that I'll be highlighting.

00:03:38.730 --> 00:03:43.620 align:middle line:84%
So I'll be seeing you
in the lab environment.

00:03:43.620 --> 00:03:46.750 align:middle line:84%
All right, so I'm back
within the lab environment.

00:03:46.750 --> 00:03:49.590 align:middle line:84%
And as you can see, you will
be provided with the target IP

00:03:49.590 --> 00:03:50.820 align:middle line:90%
address.

00:03:50.820 --> 00:03:52.800 align:middle line:84%
And in your case, it's
going to be different.

00:03:52.800 --> 00:03:55.300 align:middle line:84%
All you need to do is just copy
it because, of course, we'll

00:03:55.300 --> 00:03:56.980 align:middle line:90%
be needing it in a few seconds.

00:03:56.980 --> 00:04:00.090 align:middle line:84%
So the first step, like
any penetration test,

00:04:00.090 --> 00:04:01.620 align:middle line:84%
will essentially
involve performing

00:04:01.620 --> 00:04:04.200 align:middle line:84%
a port scan on the
target to identify what

00:04:04.200 --> 00:04:06.750 align:middle line:90%
ports and services are running.

00:04:06.750 --> 00:04:08.850 align:middle line:84%
And we can do this
by saying Nmap,

00:04:08.850 --> 00:04:11.520 align:middle line:84%
and we can say we want to
perform service version

00:04:11.520 --> 00:04:16.079 align:middle line:84%
detection, maybe even operating
system detection if we want to.

00:04:16.079 --> 00:04:19.470 align:middle line:84%
And of course, if you've
learned about how to use Nmap,

00:04:19.470 --> 00:04:23.070 align:middle line:84%
we can also use a SYN
scan or a ping-only scan

00:04:23.070 --> 00:04:27.488 align:middle line:84%
and essentially to be
stealthy if we want to.

00:04:27.488 --> 00:04:30.030 align:middle line:84%
And in this case, I'm just going
to perform a service version

00:04:30.030 --> 00:04:30.810 align:middle line:90%
detection scan.

00:04:30.810 --> 00:04:34.150 align:middle line:84%
I would recommend scanning
all the ports on the target.

00:04:34.150 --> 00:04:36.460 align:middle line:84%
And in this case, you will
see why I'm saying that.

00:04:36.460 --> 00:04:39.420 align:middle line:84%
However, in this case,
I'll just say sV,

00:04:39.420 --> 00:04:42.465 align:middle line:84%
and I'll paste in the target
IP, and I'll hit Enter.

00:04:42.465 --> 00:04:44.340 align:middle line:84%
So I'm going to give
this a couple of seconds

00:04:44.340 --> 00:04:47.330 align:middle line:84%
to a couple of
minutes to complete.

00:04:47.330 --> 00:04:50.180 align:middle line:84%
All right, so the
Nmap scan is complete.

00:04:50.180 --> 00:04:52.960 align:middle line:84%
And as you can see,
we have the services

00:04:52.960 --> 00:04:55.810 align:middle line:84%
that you would typically
associate with a Windows

00:04:55.810 --> 00:04:56.500 align:middle line:90%
system.

00:04:56.500 --> 00:04:57.490 align:middle line:90%
We have RPC.

00:04:57.490 --> 00:04:58.540 align:middle line:90%
We have NetBIOS.

00:04:58.540 --> 00:05:00.970 align:middle line:84%
We have SMB, and that
tells us that it's either

00:05:00.970 --> 00:05:05.253 align:middle line:84%
running Windows Server 2008
or Windows Server 2012.

00:05:05.253 --> 00:05:06.670 align:middle line:84%
And of course, if
we had performed

00:05:06.670 --> 00:05:08.410 align:middle line:84%
operating system
detection, we might

00:05:08.410 --> 00:05:11.860 align:middle line:84%
have got a more solid
prediction as to what

00:05:11.860 --> 00:05:14.470 align:middle line:84%
operating system or
what version of Windows

00:05:14.470 --> 00:05:16.160 align:middle line:90%
is running on the target.

00:05:16.160 --> 00:05:19.940 align:middle line:84%
However, we don't see
any port 3389 open.

00:05:19.940 --> 00:05:23.830 align:middle line:84%
We do see that we
have port 3333 open,

00:05:23.830 --> 00:05:25.990 align:middle line:84%
but it doesn't tell us
what service that is.

00:05:25.990 --> 00:05:30.460 align:middle line:84%
And this is primarily because,
again, this particular port

00:05:30.460 --> 00:05:35.350 align:middle line:84%
is not really assigned to any
service, and in this case,

00:05:35.350 --> 00:05:38.590 align:middle line:84%
this is what I wanted to
highlight in this video,

00:05:38.590 --> 00:05:40.780 align:middle line:84%
and that, of course,
is the fact that RDP

00:05:40.780 --> 00:05:43.450 align:middle line:84%
can be configured to run
on another port instead

00:05:43.450 --> 00:05:44.800 align:middle line:90%
of the default port.

00:05:44.800 --> 00:05:48.100 align:middle line:84%
And in this case, this
particular port is running RDP.

00:05:48.100 --> 00:05:50.920 align:middle line:84%
But if you were performing
a Black box penetration

00:05:50.920 --> 00:05:55.420 align:middle line:84%
test, how would you be
able to verify this,

00:05:55.420 --> 00:05:57.400 align:middle line:84%
or how can you
actually check a port

00:05:57.400 --> 00:05:59.740 align:middle line:84%
and determine whether
or not it's running RDP?

00:05:59.740 --> 00:06:02.950 align:middle line:84%
Well, one of the techniques
is to actually connect

00:06:02.950 --> 00:06:06.970 align:middle line:84%
to the target system and specify
this particular port as the RDP

00:06:06.970 --> 00:06:10.630 align:middle line:84%
port, and in that case, you'd be
able to verify really quickly.

00:06:10.630 --> 00:06:13.690 align:middle line:84%
But another really
helpful tool or module

00:06:13.690 --> 00:06:16.720 align:middle line:84%
is the Metasploit
module RDP scanner.

00:06:16.720 --> 00:06:18.980 align:middle line:84%
So we're just going
to use it here.

00:06:18.980 --> 00:06:21.160 align:middle line:84%
So I'll just open up
a new tab, and I'll

00:06:21.160 --> 00:06:23.260 align:middle line:84%
start up the
PostgreSQL database,

00:06:23.260 --> 00:06:29.240 align:middle line:84%
so service postgresql start
and msfconsole like so.

00:06:29.240 --> 00:06:33.460 align:middle line:84%
And we'll give this a couple
of seconds to start up.

00:06:33.460 --> 00:06:34.990 align:middle line:90%
So MSF console is started up.

00:06:34.990 --> 00:06:41.080 align:middle line:84%
And we can search for the module
by saying search RDP_scanner,

00:06:41.080 --> 00:06:43.060 align:middle line:84%
and you can see it's an
auxiliary module here.

00:06:43.060 --> 00:06:45.520 align:middle line:84%
This will essentially
identify endpoints speaking

00:06:45.520 --> 00:06:46.750 align:middle line:90%
the remote desktop protocol.

00:06:46.750 --> 00:06:49.120 align:middle line:84%
What that means is that
it will essentially

00:06:49.120 --> 00:06:53.020 align:middle line:84%
tell you whether that particular
port is indeed running RDP.

00:06:53.020 --> 00:06:56.120 align:middle line:84%
So we can just copy the
actual module name here.

00:06:56.120 --> 00:06:57.340 align:middle line:90%
I'm going to say use.

00:06:57.340 --> 00:06:58.900 align:middle line:90%
Paste that in there.

00:06:58.900 --> 00:07:02.380 align:middle line:84%
And we can then show the options
for this particular module.

00:07:02.380 --> 00:07:05.620 align:middle line:84%
And you can see the options
we need to specify here

00:07:05.620 --> 00:07:10.180 align:middle line:84%
are going to be the target IP,
as well as the target port.

00:07:10.180 --> 00:07:13.210 align:middle line:84%
And in this case, we want
to change the RPORT option

00:07:13.210 --> 00:07:17.300 align:middle line:84%
to 3333 instead of
the default RDP port.

00:07:17.300 --> 00:07:19.060 align:middle line:84%
So we'll start off
with the target IP.

00:07:19.060 --> 00:07:22.060 align:middle line:84%
I'm just going to copy it
from this little document

00:07:22.060 --> 00:07:23.200 align:middle line:90%
here or that text file.

00:07:23.200 --> 00:07:27.520 align:middle line:84%
So I'll say set RHOSTS,
paste that in there,

00:07:27.520 --> 00:07:32.050 align:middle line:90%
and then set our RPORT to 3333.

00:07:32.050 --> 00:07:33.550 align:middle line:84%
And of course, in
your case, if it's

00:07:33.550 --> 00:07:35.530 align:middle line:84%
configured on a
different port, make

00:07:35.530 --> 00:07:38.080 align:middle line:84%
sure to accurately
change the RPORT value

00:07:38.080 --> 00:07:39.970 align:middle line:90%
to match that particular port.

00:07:39.970 --> 00:07:44.860 align:middle line:84%
You can also set the RDP client
name and the or rather the RDP

00:07:44.860 --> 00:07:47.710 align:middle line:84%
client IP and the
RDP client name,

00:07:47.710 --> 00:07:50.090 align:middle line:84%
but that really is not
required in this instance.

00:07:50.090 --> 00:07:52.160 align:middle line:90%
So we'll just hit Run.

00:07:52.160 --> 00:07:54.410 align:middle line:84%
And you can see it's going
to tell you right over here

00:07:54.410 --> 00:07:56.960 align:middle line:84%
detected RDP on that
particular port,

00:07:56.960 --> 00:07:59.960 align:middle line:84%
and it tells us the actual
version of the Build version.

00:07:59.960 --> 00:08:02.662 align:middle line:84%
In this case, it doesn't tell
us the exact version of Windows

00:08:02.662 --> 00:08:04.370 align:middle line:84%
that's running, but
it tells us the build

00:08:04.370 --> 00:08:06.530 align:middle line:90%
version, which is 9600 here.

00:08:06.530 --> 00:08:10.280 align:middle line:84%
So we know that RDP is
running on the target

00:08:10.280 --> 00:08:13.850 align:middle line:84%
however we really can't
authenticate with the target

00:08:13.850 --> 00:08:17.090 align:middle line:84%
system via RDP because we
don't have any credentials.

00:08:17.090 --> 00:08:19.188 align:middle line:84%
Well, how would we
obtain these credentials?

00:08:19.188 --> 00:08:21.230 align:middle line:84%
Well, the technique that
I'm going to be covering

00:08:21.230 --> 00:08:24.770 align:middle line:84%
is the process of performing
a brute force on RDP.

00:08:24.770 --> 00:08:27.530 align:middle line:84%
And the tool we can use
to do this is hydra.

00:08:27.530 --> 00:08:29.360 align:middle line:84%
And of course, you
can now start to see

00:08:29.360 --> 00:08:32.480 align:middle line:84%
why hydra is so powerful
because we can essentially

00:08:32.480 --> 00:08:34.880 align:middle line:84%
perform a brute force
on multiple protocols,

00:08:34.880 --> 00:08:40.620 align:middle line:84%
not just SSH, FTP, or
SMB, for that matter.

00:08:40.620 --> 00:08:42.020 align:middle line:90%
So we can say hydra.

00:08:42.020 --> 00:08:44.910 align:middle line:84%
And because we don't know
the username or the password,

00:08:44.910 --> 00:08:48.860 align:middle line:84%
we'll need to specify a
wordlist or essentially

00:08:48.860 --> 00:08:50.720 align:middle line:90%
a list that contains users.

00:08:50.720 --> 00:08:53.570 align:middle line:90%
In this case, we'll say user.

00:08:53.570 --> 00:08:56.471 align:middle line:84%
The wordlist will be using for
the usernames is under user,

00:08:56.471 --> 00:09:02.900 align:middle line:84%
share, Metasploit
framework, data, wordlists,

00:09:02.900 --> 00:09:09.110 align:middle line:84%
and we are going to be utilizing
the common_users.txt list.

00:09:09.110 --> 00:09:11.580 align:middle line:84%
We then need to specify
the password list.

00:09:11.580 --> 00:09:14.870 align:middle line:84%
In this case, we're just going
to use the same directory.

00:09:14.870 --> 00:09:20.280 align:middle line:84%
So that's under usher, share,
Metasploit framework, data,

00:09:20.280 --> 00:09:24.060 align:middle line:84%
wordlists, and in this
case, we will be using

00:09:24.060 --> 00:09:27.210 align:middle line:90%
unix_passwords.txt.

00:09:27.210 --> 00:09:29.310 align:middle line:84%
We then need to
specify the protocol.

00:09:29.310 --> 00:09:32.820 align:middle line:84%
In this case, it's RDP
and the target IP address.

00:09:32.820 --> 00:09:35.850 align:middle line:84%
And of course, remember, if we
just hit Enter at this point,

00:09:35.850 --> 00:09:38.190 align:middle line:84%
hydra will automatically
assume that you

00:09:38.190 --> 00:09:42.450 align:middle line:84%
want to connect to the default
RDP port, which is 3389.

00:09:42.450 --> 00:09:44.670 align:middle line:84%
In this case, we need to
specify the port, which

00:09:44.670 --> 00:09:47.940 align:middle line:84%
can be done by specifying
the hyphens option and then

00:09:47.940 --> 00:09:50.490 align:middle line:90%
the port 3333.

00:09:50.490 --> 00:09:52.020 align:middle line:90%
And we can then hit Enter.

00:09:52.020 --> 00:09:55.440 align:middle line:84%
Now, of course, in your case
or during a penetration test,

00:09:55.440 --> 00:09:58.080 align:middle line:84%
you want to be very cognizant
of the brute force speed

00:09:58.080 --> 00:10:00.540 align:middle line:84%
because you can essentially,
or you can really

00:10:00.540 --> 00:10:04.170 align:middle line:84%
cause a denial of service on
that particular RDP service

00:10:04.170 --> 00:10:08.340 align:middle line:84%
and cause it to go down, or you
could crash the Windows system,

00:10:08.340 --> 00:10:10.660 align:middle line:84%
and of course, that is
something that will be noticed.

00:10:10.660 --> 00:10:13.500 align:middle line:84%
So you also have the ability
to reduce the brute force

00:10:13.500 --> 00:10:14.850 align:middle line:90%
speed with hydra.

00:10:14.850 --> 00:10:18.630 align:middle line:84%
So, for example, let me just
exit out of MSF console here.

00:10:18.630 --> 00:10:22.020 align:middle line:84%
If I say hydra
and hit Enter, you

00:10:22.020 --> 00:10:24.550 align:middle line:84%
have the ability to limit
the amount of tasks.

00:10:24.550 --> 00:10:26.220 align:middle line:90%
So you can use the task option.

00:10:26.220 --> 00:10:29.100 align:middle line:84%
The default option
is set to 16, so you

00:10:29.100 --> 00:10:32.670 align:middle line:84%
can reduce that to two or three
depending on your requirements.

00:10:32.670 --> 00:10:35.160 align:middle line:84%
In this case, we'll just use
the default configuration,

00:10:35.160 --> 00:10:36.430 align:middle line:90%
which is 16.

00:10:36.430 --> 00:10:39.720 align:middle line:84%
We can then hit Enter, and it's
going to begin the brute force.

00:10:39.720 --> 00:10:43.410 align:middle line:84%
And we already are able to
identify a user account called

00:10:43.410 --> 00:10:46.672 align:middle line:84%
sysadmin, and their password,
in this case, is Samantha.

00:10:46.672 --> 00:10:48.630 align:middle line:84%
So I'm just going to wait
for this to complete.

00:10:48.630 --> 00:10:51.240 align:middle line:84%
Hopefully, we'll be able to
identify an administrator

00:10:51.240 --> 00:10:52.590 align:middle line:90%
account and the password.

00:10:52.590 --> 00:10:55.940 align:middle line:84%
So I'll just give this
a couple of minutes.

00:10:55.940 --> 00:10:57.890 align:middle line:84%
All right, so it
looks like I've been

00:10:57.890 --> 00:10:59.810 align:middle line:84%
able to identify
the administrator

00:10:59.810 --> 00:11:03.710 align:middle line:84%
account and the password,
which is qwertyuiop,

00:11:03.710 --> 00:11:07.520 align:middle line:84%
as we had already experienced
during the SMB exploitation

00:11:07.520 --> 00:11:08.900 align:middle line:90%
lab.

00:11:08.900 --> 00:11:10.308 align:middle line:90%
So the brute force is complete.

00:11:10.308 --> 00:11:12.350 align:middle line:84%
Now don't worry if you
get this error telling you

00:11:12.350 --> 00:11:15.620 align:middle line:84%
that freerdp, the connection
failed to establish.

00:11:15.620 --> 00:11:17.570 align:middle line:84%
The reason this is
happening is because hydra,

00:11:17.570 --> 00:11:19.460 align:middle line:84%
after finding
legitimate credentials,

00:11:19.460 --> 00:11:22.160 align:middle line:84%
will try and connect
to the target via RDP

00:11:22.160 --> 00:11:25.280 align:middle line:84%
with the credentials it
was able to identify,

00:11:25.280 --> 00:11:29.420 align:middle line:84%
and the default RDP client
that it uses is freerdp.

00:11:29.420 --> 00:11:32.870 align:middle line:84%
Unfortunately, this lab
doesn't support free RDP.

00:11:32.870 --> 00:11:35.630 align:middle line:84%
The only RDP client
we can use is

00:11:35.630 --> 00:11:39.360 align:middle line:84%
xfreerdp, which will be taking a
look at how to use in a second.

00:11:39.360 --> 00:11:41.480 align:middle line:84%
So now that we've
identified the credentials,

00:11:41.480 --> 00:11:45.260 align:middle line:84%
we can essentially authenticate
with the target via RDP,

00:11:45.260 --> 00:11:47.210 align:middle line:84%
and we can specify
the credentials.

00:11:47.210 --> 00:11:49.340 align:middle line:90%
So we'll be using xfreerdp.

00:11:49.340 --> 00:11:54.290 align:middle line:84%
So to use xfreerdp, we
essentially just say xfreerdp,

00:11:54.290 --> 00:11:56.130 align:middle line:84%
and then we specify
the username,

00:11:56.130 --> 00:11:59.690 align:middle line:84%
which can be done by specifying
the forwardslash then

00:11:59.690 --> 00:12:01.580 align:middle line:84%
the parameter that
you want to pass.

00:12:01.580 --> 00:12:06.020 align:middle line:84%
In this case, the username
is going to be administrator.

00:12:06.020 --> 00:12:07.920 align:middle line:84%
And we then specify
the password.

00:12:07.920 --> 00:12:09.860 align:middle line:84%
So the same thing
goes for password.

00:12:09.860 --> 00:12:14.030 align:middle line:84%
And the password, in
this case, is qwertyuiop.

00:12:14.030 --> 00:12:16.830 align:middle line:84%
We then need to specify
the target IP address,

00:12:16.830 --> 00:12:21.900 align:middle line:84%
which is done by saying /v, and
then we can paste in the target

00:12:21.900 --> 00:12:22.400 align:middle line:90%
IP.

00:12:22.400 --> 00:12:25.140 align:middle line:84%
So I'm just going
to copy that there.

00:12:25.140 --> 00:12:25.800 align:middle line:90%
There we go.

00:12:25.800 --> 00:12:27.600 align:middle line:90%
And I can paste that in there.

00:12:27.600 --> 00:12:31.400 align:middle line:84%
And remember, we still need
to specify the actual RDP port

00:12:31.400 --> 00:12:33.960 align:middle line:84%
on the target
because, in this case,

00:12:33.960 --> 00:12:37.610 align:middle line:84%
xfreerdp will assume that you
want to connect to the default

00:12:37.610 --> 00:12:40.370 align:middle line:90%
RDP port so we can use.

00:12:40.370 --> 00:12:45.860 align:middle line:84%
We can use a colon there, and we
can say 3333, and we hit Enter.

00:12:45.860 --> 00:12:48.450 align:middle line:84%
So it's going to ask us whether
we trust the certificate.

00:12:48.450 --> 00:12:49.880 align:middle line:90%
I'm going to hit Yes.

00:12:49.880 --> 00:12:53.820 align:middle line:84%
And it's going to open up an
RDP session right over here.

00:12:53.820 --> 00:12:56.930 align:middle line:84%
And we now have access to
the target system via RDP.

00:12:56.930 --> 00:12:59.300 align:middle line:84%
And you can see this is the
complete Windows desktop

00:12:59.300 --> 00:13:02.930 align:middle line:84%
experience, and we're currently
logged in as the administrator

00:13:02.930 --> 00:13:04.020 align:middle line:90%
user right over here.

00:13:04.020 --> 00:13:06.630 align:middle line:84%
So we've pretty much gained
access to the target system.

00:13:06.630 --> 00:13:08.570 align:middle line:90%
And we can do whatever we like.

00:13:08.570 --> 00:13:11.330 align:middle line:84%
Now, you can also authenticate
with the target system

00:13:11.330 --> 00:13:14.510 align:middle line:84%
through the use of any of
the other user accounts

00:13:14.510 --> 00:13:17.960 align:middle line:84%
that we were able to identify
through the brute force

00:13:17.960 --> 00:13:18.620 align:middle line:90%
with hydra.

00:13:18.620 --> 00:13:22.580 align:middle line:84%
So we can log in as the
auditor, as the sysadmin et

00:13:22.580 --> 00:13:23.660 align:middle line:90%
cetera, et cetera.

00:13:23.660 --> 00:13:28.550 align:middle line:84%
All you have to do is just
substitute the actual username

00:13:28.550 --> 00:13:30.650 align:middle line:84%
option here and the
password option.

00:13:30.650 --> 00:13:33.590 align:middle line:84%
And of course, in your case,
you can also utilize other RDP

00:13:33.590 --> 00:13:35.210 align:middle line:90%
clients like Romania.

00:13:35.210 --> 00:13:37.520 align:middle line:84%
All right, so that
is going to conclude

00:13:37.520 --> 00:13:42.510 align:middle line:84%
the practical demonstration
side of this video.

00:13:42.510 --> 00:13:44.870 align:middle line:84%
In the next video,
we will be exploring

00:13:44.870 --> 00:13:47.900 align:middle line:84%
the process of exploiting
an inherent vulnerability

00:13:47.900 --> 00:13:50.450 align:middle line:84%
within the RDP
protocol on Windows,

00:13:50.450 --> 00:13:52.070 align:middle line:84%
and the name of
this vulnerability

00:13:52.070 --> 00:13:53.150 align:middle line:90%
is called bluekeep.

00:13:53.150 --> 00:13:56.710 align:middle line:84%
So I'll see you
in the next video.

00:13:56.710 --> 00:13:58.000 align:middle line:90%