WEBVTT

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


00:00:10.050 --> 00:00:11.592 align:middle line:90%
Targeting OpenSSH.

00:00:11.592 --> 00:00:13.800 align:middle line:84%
In this video, we're going
to be taking a look at how

00:00:13.800 --> 00:00:17.250 align:middle line:84%
to target the OpenSSH
server or service that's

00:00:17.250 --> 00:00:18.700 align:middle line:90%
running on the target system.

00:00:18.700 --> 00:00:22.350 align:middle line:84%
So we'll be taking a look at
the various tools and techniques

00:00:22.350 --> 00:00:25.260 align:middle line:84%
that can be used to
essentially gain access

00:00:25.260 --> 00:00:27.630 align:middle line:90%
to the target system via SSH.

00:00:27.630 --> 00:00:28.590 align:middle line:90%
And yeah.

00:00:28.590 --> 00:00:30.830 align:middle line:84%
So again, we're using
the same lab environment.

00:00:30.830 --> 00:00:33.580 align:middle line:84%
And remember, if you terminated
your lab environment,

00:00:33.580 --> 00:00:36.840 align:middle line:84%
then you need to obtain the
target IP address again,

00:00:36.840 --> 00:00:40.020 align:middle line:84%
which I've already highlighted
during the port scanning

00:00:40.020 --> 00:00:41.320 align:middle line:90%
and enumeration video.

00:00:41.320 --> 00:00:44.010 align:middle line:84%
So do check that out if you're
having issues with that.

00:00:44.010 --> 00:00:45.510 align:middle line:84%
With that being
said, I'm just going

00:00:45.510 --> 00:00:47.880 align:middle line:84%
to switch over to
my lab environment,

00:00:47.880 --> 00:00:49.710 align:middle line:84%
and we can go
through the process

00:00:49.710 --> 00:00:53.340 align:middle line:84%
of targeting the OpenSSH
service and consequently

00:00:53.340 --> 00:00:56.140 align:middle line:84%
gaining remote access
to the target system.

00:00:56.140 --> 00:00:57.480 align:middle line:90%
So I'll see you then.

00:00:57.480 --> 00:01:00.800 align:middle line:90%


00:01:00.800 --> 00:01:01.300 align:middle line:90%
All right?

00:01:01.300 --> 00:01:03.350 align:middle line:84%
So I'm back within
my lab environment.

00:01:03.350 --> 00:01:05.680 align:middle line:84%
And again, as I said,
we're targeting OpenSSH,

00:01:05.680 --> 00:01:08.960 align:middle line:84%
so that was running on the
default SSH port on the target.

00:01:08.960 --> 00:01:11.860 align:middle line:84%
So I've just performed a
service version detection

00:01:11.860 --> 00:01:14.410 align:middle line:84%
scan and the default
script scan just

00:01:14.410 --> 00:01:17.710 align:middle line:84%
to highlight the exact
version of OpenSSH that's

00:01:17.710 --> 00:01:18.710 align:middle line:90%
running on the target.

00:01:18.710 --> 00:01:19.210 align:middle line:90%
So

00:01:19.210 --> 00:01:22.420 align:middle line:84%
In terms of targeting
SSH, it doesn't really

00:01:22.420 --> 00:01:24.400 align:middle line:84%
matter what product
or what service.

00:01:24.400 --> 00:01:25.720 align:middle line:90%
It could be OpenSSH.

00:01:25.720 --> 00:01:28.120 align:middle line:90%
It could be libssh, et cetera.

00:01:28.120 --> 00:01:31.150 align:middle line:84%
What's important to consider
is the operating system

00:01:31.150 --> 00:01:32.650 align:middle line:90%
that it is running on.

00:01:32.650 --> 00:01:35.180 align:middle line:84%
And in this case, we know it's
running on a Windows system.

00:01:35.180 --> 00:01:38.560 align:middle line:84%
So just keep that in mind in
regards to the type of access

00:01:38.560 --> 00:01:43.010 align:middle line:84%
that you will get once we
obtain legitimate credentials.

00:01:43.010 --> 00:01:45.310 align:middle line:84%
Now, another thing to
take into consideration

00:01:45.310 --> 00:01:49.360 align:middle line:84%
is the fact that we were able
to obtain legitimate credentials

00:01:49.360 --> 00:01:50.600 align:middle line:90%
in the previous video.

00:01:50.600 --> 00:01:54.370 align:middle line:84%
Now, as I said in the context
of services like FTP and SSH,

00:01:54.370 --> 00:01:59.830 align:middle line:84%
they utilize user accounts on
the Windows or Linux systems

00:01:59.830 --> 00:02:01.160 align:middle line:90%
for authentication.

00:02:01.160 --> 00:02:04.030 align:middle line:84%
So the only thing that might
change in certain cases

00:02:04.030 --> 00:02:05.710 align:middle line:84%
is the actual
password, but we were

00:02:05.710 --> 00:02:08.139 align:middle line:84%
able to identify in
the previous video--

00:02:08.139 --> 00:02:10.690 align:middle line:84%
that we were able to identify
the following accounts.

00:02:10.690 --> 00:02:13.330 align:middle line:84%
So we identified a
account called vagrant.

00:02:13.330 --> 00:02:15.220 align:middle line:84%
And of course, the
administrator account

00:02:15.220 --> 00:02:18.760 align:middle line:84%
on Windows, which as we know
is very, very important,

00:02:18.760 --> 00:02:21.610 align:middle line:84%
and it is really the
most privileged account

00:02:21.610 --> 00:02:23.120 align:middle line:90%
on a Windows system.

00:02:23.120 --> 00:02:26.120 align:middle line:84%
And of course, we were able to
identify the password for both.

00:02:26.120 --> 00:02:28.600 align:middle line:84%
For both of them, the
password was vagrant.

00:02:28.600 --> 00:02:33.260 align:middle line:84%
So again, we can perform a brute
force attack on the SSH server.

00:02:33.260 --> 00:02:36.670 align:middle line:84%
However, we also need to
be efficient with that.

00:02:36.670 --> 00:02:40.090 align:middle line:84%
And given the fact that we have
identified two user accounts,

00:02:40.090 --> 00:02:41.680 align:middle line:84%
then we can perform
the brute force

00:02:41.680 --> 00:02:43.660 align:middle line:84%
to identify whether
the passwords are

00:02:43.660 --> 00:02:47.630 align:middle line:84%
different for the SSH service
for these two user accounts.

00:02:47.630 --> 00:02:51.880 align:middle line:84%
Now, before we do that, OpenSSH
has a few vulnerabilities.

00:02:51.880 --> 00:02:57.190 align:middle line:84%
However, most of them really
affect OpenSSH version 7.2.

00:02:57.190 --> 00:02:59.800 align:middle line:84%
So if we perform a
query with searchsploit,

00:02:59.800 --> 00:03:04.520 align:middle line:84%
and we say OpenSSH
7.1, for example.

00:03:04.520 --> 00:03:07.690 align:middle line:84%
You can see that
really the only two

00:03:07.690 --> 00:03:10.870 align:middle line:84%
exploit or the
exploit files that

00:03:10.870 --> 00:03:15.250 align:middle line:84%
are available for this specific
version of OpenSSH running

00:03:15.250 --> 00:03:18.940 align:middle line:84%
on the target is the username
enumeration Python script that

00:03:18.940 --> 00:03:21.100 align:middle line:84%
allows you to perform
user enumeration, which

00:03:21.100 --> 00:03:23.230 align:middle line:84%
in this case, we
really don't need.

00:03:23.230 --> 00:03:25.450 align:middle line:84%
Apart from that, we don't
have any other exploit

00:03:25.450 --> 00:03:28.750 align:middle line:84%
that can, again, provide us with
anything that we don't already

00:03:28.750 --> 00:03:29.510 align:middle line:90%
have.

00:03:29.510 --> 00:03:32.770 align:middle line:84%
So again, to perform the
brute force with hydra,

00:03:32.770 --> 00:03:33.740 align:middle line:90%
it's very, very simple.

00:03:33.740 --> 00:03:34.870 align:middle line:90%
We simply say hydra.

00:03:34.870 --> 00:03:37.460 align:middle line:84%
We're not going to perform a
brute force on the username.

00:03:37.460 --> 00:03:40.120 align:middle line:84%
So we'll just say the
username will start off

00:03:40.120 --> 00:03:42.550 align:middle line:84%
with the user vagrant, and
we'll see whether there's

00:03:42.550 --> 00:03:43.760 align:middle line:90%
been any change there.

00:03:43.760 --> 00:03:47.530 align:middle line:84%
And then of course, the password
list, we can say user, share.

00:03:47.530 --> 00:03:52.270 align:middle line:84%
And in this case, we'll use
the actual metasploit wordlists

00:03:52.270 --> 00:03:54.040 align:middle line:90%
under the wordlists directory.

00:03:54.040 --> 00:03:58.960 align:middle line:84%
And we can say
unix_users.txt or password.

00:03:58.960 --> 00:04:02.240 align:middle line:84%
And then we specify the
target IP, which in my case,

00:04:02.240 --> 00:04:04.270 align:middle line:84%
I've already
identified and copied.

00:04:04.270 --> 00:04:09.030 align:middle line:84%
And we know that the
protocol in this case is SSH.

00:04:09.030 --> 00:04:11.380 align:middle line:84%
And we can hit Enter, and
let's see what we get.

00:04:11.380 --> 00:04:14.710 align:middle line:84%
So that's going to begin
the brute force there.

00:04:14.710 --> 00:04:17.200 align:middle line:84%
And let's see whether
we're able to identify

00:04:17.200 --> 00:04:20.300 align:middle line:84%
whether the password is
different or the SSH service.

00:04:20.300 --> 00:04:22.360 align:middle line:84%
So we'll give this
a couple of seconds,

00:04:22.360 --> 00:04:26.290 align:middle line:84%
and then we can also do this
for the administrator account.

00:04:26.290 --> 00:04:28.540 align:middle line:84%
So I'm just going to
let this complete.

00:04:28.540 --> 00:04:29.040 align:middle line:90%
All right?

00:04:29.040 --> 00:04:30.630 align:middle line:84%
So after a couple
of seconds, we can

00:04:30.630 --> 00:04:33.660 align:middle line:84%
see that the password for
the user account vagrant

00:04:33.660 --> 00:04:36.810 align:middle line:84%
is just vagrant, so that's a
really bad thing from the point

00:04:36.810 --> 00:04:38.760 align:middle line:84%
of view of the
administrator that's

00:04:38.760 --> 00:04:42.580 align:middle line:84%
responsible for managing the
security of the target system.

00:04:42.580 --> 00:04:46.890 align:middle line:84%
So that means we can gain access
to the target system via SSH

00:04:46.890 --> 00:04:48.810 align:middle line:84%
as we have obtained
legitimate credentials.

00:04:48.810 --> 00:04:52.050 align:middle line:84%
However, given the fact that
we're a penetration tester,

00:04:52.050 --> 00:04:54.450 align:middle line:84%
we really want the
prized asset, which

00:04:54.450 --> 00:04:56.820 align:middle line:84%
is accessed via the
administrator account that

00:04:56.820 --> 00:05:00.060 align:middle line:84%
will then provide us with
elevated privileges right out

00:05:00.060 --> 00:05:01.380 align:middle line:90%
of the box.

00:05:01.380 --> 00:05:03.870 align:middle line:84%
So instead of saying vagrant,
we can perform a brute force

00:05:03.870 --> 00:05:06.270 align:middle line:90%
for the user administrator.

00:05:06.270 --> 00:05:09.450 align:middle line:84%
And of course, make sure to
save these credentials offline.

00:05:09.450 --> 00:05:11.970 align:middle line:84%
And again, I'm just going to
give this a couple of seconds.

00:05:11.970 --> 00:05:15.280 align:middle line:90%
It shouldn't take too much time.

00:05:15.280 --> 00:05:15.780 align:middle line:90%
All right?

00:05:15.780 --> 00:05:17.550 align:middle line:84%
So the brute force
is complete, and it

00:05:17.550 --> 00:05:19.680 align:middle line:84%
looks like for the
administrator account,

00:05:19.680 --> 00:05:23.370 align:middle line:84%
there aren't any valid password,
which is, again, slightly weird

00:05:23.370 --> 00:05:27.870 align:middle line:84%
because for the FTP service,
the administrator account

00:05:27.870 --> 00:05:29.040 align:middle line:90%
password was vagrant.

00:05:29.040 --> 00:05:31.050 align:middle line:84%
So again, now that
we've identified

00:05:31.050 --> 00:05:34.740 align:middle line:84%
that we can log in with the use
of vagrant or the user account

00:05:34.740 --> 00:05:36.870 align:middle line:90%
vagrant, we can actually log in.

00:05:36.870 --> 00:05:40.090 align:middle line:84%
And to do that, we can say
ssh, and then specify the user.

00:05:40.090 --> 00:05:43.050 align:middle line:90%
So vagrant@ the target IP.

00:05:43.050 --> 00:05:46.615 align:middle line:84%
And this will provide us with
initial access on the target

00:05:46.615 --> 00:05:48.240 align:middle line:84%
system, and that's
what we were looking

00:05:48.240 --> 00:05:50.130 align:middle line:90%
for as a penetration tester.

00:05:50.130 --> 00:05:51.180 align:middle line:90%
So I'll hit Enter.

00:05:51.180 --> 00:05:54.540 align:middle line:84%
It's going to ask us whether
we want to continue connecting,

00:05:54.540 --> 00:05:55.890 align:middle line:90%
so I'll say yes.

00:05:55.890 --> 00:05:58.950 align:middle line:84%
It's going to ask us for the
password, so we'll say vagrant.

00:05:58.950 --> 00:06:01.590 align:middle line:84%
And if correct, this
should provide us

00:06:01.590 --> 00:06:05.348 align:middle line:84%
with a bash session or a
Bourne shell session, which

00:06:05.348 --> 00:06:07.890 align:middle line:84%
is slightly weird because we
are working on a Windows system,

00:06:07.890 --> 00:06:11.100 align:middle line:84%
but that's what I had wanted
to highlight early on.

00:06:11.100 --> 00:06:13.810 align:middle line:84%
Indeed, you can see we get
a Bourne shell session.

00:06:13.810 --> 00:06:17.880 align:middle line:84%
So if we say ls -al, you can
see we're currently within--

00:06:17.880 --> 00:06:18.930 align:middle line:90%
let's see pwd.

00:06:18.930 --> 00:06:22.170 align:middle line:84%
We're currently within
the C drive on the users,

00:06:22.170 --> 00:06:24.370 align:middle line:84%
vagrant, which is
exactly what we want.

00:06:24.370 --> 00:06:26.070 align:middle line:90%
And of course whoami.

00:06:26.070 --> 00:06:28.170 align:middle line:84%
We can see that we're
currently the user vagrant.

00:06:28.170 --> 00:06:33.030 align:middle line:84%
And then of course, we can say
net localgroup administrators,

00:06:33.030 --> 00:06:35.820 align:middle line:84%
which is a Windows account,
so we probably cannot do that,

00:06:35.820 --> 00:06:39.220 align:middle line:84%
and there might be a few
compatibility issues there.

00:06:39.220 --> 00:06:41.850 align:middle line:84%
But the main thing is
that we've obtained access

00:06:41.850 --> 00:06:43.120 align:middle line:90%
to the target system.

00:06:43.120 --> 00:06:47.040 align:middle line:84%
So you can see if you type in
any Windows native commands

00:06:47.040 --> 00:06:49.030 align:middle line:84%
like dir, that will
probably not work,

00:06:49.030 --> 00:06:51.180 align:middle line:84%
which is why I did not
type in the net localgroup

00:06:51.180 --> 00:06:53.110 align:middle line:90%
administrators command.

00:06:53.110 --> 00:06:56.430 align:middle line:84%
So we've got access
to the target via SSH,

00:06:56.430 --> 00:06:57.960 align:middle line:84%
which means we've
pretty much owned

00:06:57.960 --> 00:06:59.460 align:middle line:90%
this system at this point.

00:06:59.460 --> 00:07:01.380 align:middle line:84%
However, I also
want to try and see

00:07:01.380 --> 00:07:04.920 align:middle line:84%
whether we can gain access
with the administrator account

00:07:04.920 --> 00:07:08.940 align:middle line:84%
because that really is
what we're interested in.

00:07:08.940 --> 00:07:09.440 align:middle line:90%
All right?

00:07:09.440 --> 00:07:11.240 align:middle line:90%
So we can see administrator.

00:07:11.240 --> 00:07:14.600 align:middle line:84%
Let's try vagrant--
permission denied.

00:07:14.600 --> 00:07:17.330 align:middle line:84%
OK, so that's what I
wanted to highlight here--

00:07:17.330 --> 00:07:22.520 align:middle line:84%
is that even though we
were able to identify

00:07:22.520 --> 00:07:25.610 align:middle line:84%
the password for the
administrator account

00:07:25.610 --> 00:07:29.360 align:middle line:84%
for FTP, in certain cases--
and this is good security

00:07:29.360 --> 00:07:32.360 align:middle line:84%
practice on the side of the
administrator, is they've

00:07:32.360 --> 00:07:36.360 align:middle line:84%
disabled access SSH logins
into the administrator account,

00:07:36.360 --> 00:07:39.590 align:middle line:84%
which is, as I said,
something that's very good.

00:07:39.590 --> 00:07:44.720 align:middle line:84%
Now, we can continue with access
via the standard Bourne shell,

00:07:44.720 --> 00:07:47.720 align:middle line:84%
or we can obtain a
Meterpreter session

00:07:47.720 --> 00:07:50.030 align:middle line:84%
with the already obtained
credentials here.

00:07:50.030 --> 00:07:53.090 align:middle line:84%
And all we need to do
is open up MSFconsole.

00:07:53.090 --> 00:07:56.390 align:middle line:84%
So I'll split this vertically
here or just open up a new tab,

00:07:56.390 --> 00:07:57.800 align:middle line:90%
and I'll say msfconsole.

00:07:57.800 --> 00:08:00.790 align:middle line:90%


00:08:00.790 --> 00:08:03.290 align:middle line:84%
And we can use the
SSH login module.

00:08:03.290 --> 00:08:05.950 align:middle line:84%
And once we get a
standard session

00:08:05.950 --> 00:08:08.410 align:middle line:84%
or a standard reverse
shell, we can upgrade that

00:08:08.410 --> 00:08:10.060 align:middle line:90%
into a Meterpreter session.

00:08:10.060 --> 00:08:14.380 align:middle line:84%
So I'll search for
the module ssh login,

00:08:14.380 --> 00:08:17.763 align:middle line:90%
and we'll use the first one.

00:08:17.763 --> 00:08:19.180 align:middle line:84%
That's the auxiliary
module, so we

00:08:19.180 --> 00:08:24.358 align:middle line:90%
can say use 0 and show options.

00:08:24.358 --> 00:08:25.900 align:middle line:84%
So there's a few
options that we need

00:08:25.900 --> 00:08:27.820 align:middle line:84%
to set-- the username
and the password

00:08:27.820 --> 00:08:30.230 align:middle line:84%
because we're not
performing a brute force.

00:08:30.230 --> 00:08:32.890 align:middle line:84%
I'm going to say
username is vagrant,

00:08:32.890 --> 00:08:35.020 align:middle line:84%
as that's the only account
that we can log in with.

00:08:35.020 --> 00:08:39.640 align:middle line:84%
And the password
is also vagrant.

00:08:39.640 --> 00:08:41.740 align:middle line:84%
And then we need to
set up RHOSTS option.

00:08:41.740 --> 00:08:42.850 align:middle line:90%
That's the target IP.

00:08:42.850 --> 00:08:45.650 align:middle line:90%
So I'll say set RHOSTS.

00:08:45.650 --> 00:08:46.880 align:middle line:90%
Paste in the target IP.

00:08:46.880 --> 00:08:49.670 align:middle line:84%
And then we have a few other
options that we can configure.

00:08:49.670 --> 00:08:52.490 align:middle line:84%
And of course, we're not
performing a brute force.

00:08:52.490 --> 00:08:56.660 align:middle line:84%
What we can do is, do we have
the password file and the user

00:08:56.660 --> 00:08:57.620 align:middle line:90%
files set?

00:08:57.620 --> 00:08:59.870 align:middle line:84%
No, those are all on
set, so that's good.

00:08:59.870 --> 00:09:03.490 align:middle line:90%
And we can just hit run.

00:09:03.490 --> 00:09:07.420 align:middle line:84%
And in this case, it looks
like we were able to log in.

00:09:07.420 --> 00:09:09.790 align:middle line:90%
And it opens up an SSH session.

00:09:09.790 --> 00:09:12.070 align:middle line:84%
So there we are,
SSH session 1 open.

00:09:12.070 --> 00:09:15.970 align:middle line:84%
So if I say sessions, you can
see we get a standard shell.

00:09:15.970 --> 00:09:20.950 align:middle line:84%
So I can say sessions 1, and
you can see that works out

00:09:20.950 --> 00:09:22.120 align:middle line:90%
I believe just fine.

00:09:22.120 --> 00:09:22.900 align:middle line:90%
Indeed it does.

00:09:22.900 --> 00:09:26.800 align:middle line:84%
So I'll put this in the
background using Control and Z.

00:09:26.800 --> 00:09:28.750 align:middle line:84%
And we still have
the session active,

00:09:28.750 --> 00:09:33.610 align:middle line:84%
so I can upgrade this possibly
to a Meterpreter session

00:09:33.610 --> 00:09:37.360 align:middle line:84%
by saying sessions upgrade
session ID, which is 1.

00:09:37.360 --> 00:09:38.890 align:middle line:90%
Hit Enter.

00:09:38.890 --> 00:09:41.020 align:middle line:84%
And it looks like it's
saying the target is

00:09:41.020 --> 00:09:44.380 align:middle line:84%
running on an unsupported
architecture such as Windows

00:09:44.380 --> 00:09:45.580 align:middle line:90%
ARM.

00:09:45.580 --> 00:09:48.850 align:middle line:84%
So again, that makes sense
because the actual shell

00:09:48.850 --> 00:09:52.700 align:middle line:84%
that we have access to right now
will not allow us to do that.

00:09:52.700 --> 00:09:54.880 align:middle line:84%
So another technique
that we can utilize

00:09:54.880 --> 00:09:58.780 align:middle line:84%
is, of course, the ability
to generate a payload

00:09:58.780 --> 00:10:01.150 align:middle line:84%
with MSFvenom-- a
Meterpreter payload,

00:10:01.150 --> 00:10:05.540 align:middle line:84%
and then transfer it over to
the target system via our SSH

00:10:05.540 --> 00:10:06.040 align:middle line:90%
access.

00:10:06.040 --> 00:10:08.260 align:middle line:90%
So I can say sessions 1.

00:10:08.260 --> 00:10:11.260 align:middle line:84%
And we can then download
it to the target system.

00:10:11.260 --> 00:10:12.430 align:middle line:90%
Execute it.

00:10:12.430 --> 00:10:14.320 align:middle line:84%
And that will
consequently provide us

00:10:14.320 --> 00:10:15.850 align:middle line:90%
with a Meterpreter session.

00:10:15.850 --> 00:10:18.490 align:middle line:84%
But as I said, that's not
really necessary at this step

00:10:18.490 --> 00:10:21.590 align:middle line:84%
because we've already gained
access to the target system.

00:10:21.590 --> 00:10:23.980 align:middle line:84%
So if we try and
log in again here,

00:10:23.980 --> 00:10:28.600 align:middle line:84%
I'm just going to say vagrant,
and that will give us access

00:10:28.600 --> 00:10:29.680 align:middle line:90%
to the target system.

00:10:29.680 --> 00:10:31.840 align:middle line:84%
And we can navigate
around the file system.

00:10:31.840 --> 00:10:33.597 align:middle line:84%
Although, we are
going to be limited in

00:10:33.597 --> 00:10:35.680 align:middle line:84%
regards to what we can do
because we are currently

00:10:35.680 --> 00:10:38.800 align:middle line:90%
using the vagrant user.

00:10:38.800 --> 00:10:41.300 align:middle line:84%
That is a non-privileged
user account.

00:10:41.300 --> 00:10:45.250 align:middle line:84%
So that is how to
gain access or how

00:10:45.250 --> 00:10:47.670 align:middle line:90%
to target the OpenSSH service.

00:10:47.670 --> 00:10:50.890 align:middle line:84%
Now, if you want to obtain
a standard Windows command

00:10:50.890 --> 00:10:52.915 align:middle line:90%
session or command shell--

00:10:52.915 --> 00:10:55.990 align:middle line:84%
your typical Windows
CMD session, that

00:10:55.990 --> 00:10:59.688 align:middle line:84%
can easily be done by saying
bash, and you hit Enter.

00:10:59.688 --> 00:11:00.230 align:middle line:90%
There we are.

00:11:00.230 --> 00:11:03.070 align:middle line:84%
So that will open up
your CMD, and you can now

00:11:03.070 --> 00:11:03.940 align:middle line:90%
run Windows command.

00:11:03.940 --> 00:11:07.660 align:middle line:84%
So net localgroup
administrators, just

00:11:07.660 --> 00:11:11.710 align:middle line:84%
to verify that this
user is not a part of--

00:11:11.710 --> 00:11:14.470 align:middle line:84%
or is actually a part of
the local administrators

00:11:14.470 --> 00:11:17.410 align:middle line:84%
group, which means
that at this point,

00:11:17.410 --> 00:11:21.700 align:middle line:90%
if I say whoami and privs--

00:11:21.700 --> 00:11:23.560 align:middle line:90%
sorry, that is whoami.

00:11:23.560 --> 00:11:26.200 align:middle line:84%
Let me just type that
in correctly-- whoami

00:11:26.200 --> 00:11:28.238 align:middle line:90%
privs or priv.

00:11:28.238 --> 00:11:28.780 align:middle line:90%
There we are.

00:11:28.780 --> 00:11:32.210 align:middle line:84%
So it looks like we have
the following privileges,

00:11:32.210 --> 00:11:35.080 align:middle line:84%
but they are all disabled
apart from a couple of them.

00:11:35.080 --> 00:11:37.300 align:middle line:84%
And in terms of
elevating our privileges,

00:11:37.300 --> 00:11:41.380 align:middle line:84%
we would typically need
to bypass UAC or utilize

00:11:41.380 --> 00:11:44.350 align:middle line:84%
another privilege
escalation technique.

00:11:44.350 --> 00:11:46.870 align:middle line:84%
And this is something
that we'll be

00:11:46.870 --> 00:11:50.420 align:middle line:84%
exploring within the
post-exploitation course.

00:11:50.420 --> 00:11:52.570 align:middle line:84%
But for now, you can see
that the current user is

00:11:52.570 --> 00:11:55.660 align:middle line:84%
unprivileged, but we're
still been able to get access

00:11:55.660 --> 00:11:58.540 align:middle line:84%
to the target system
and even though this

00:11:58.540 --> 00:12:02.110 align:middle line:84%
is to an unprivileged
user at this point.

00:12:02.110 --> 00:12:03.940 align:middle line:84%
With that being
said, that is going

00:12:03.940 --> 00:12:07.120 align:middle line:84%
to conclude the practical
section or demonstration

00:12:07.120 --> 00:12:10.490 align:middle line:90%
side of this video.

00:12:10.490 --> 00:12:11.140 align:middle line:90%
All right.

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

00:12:14.020 --> 00:12:17.590 align:middle line:84%
to target the SMB service
or SMB server that's

00:12:17.590 --> 00:12:18.920 align:middle line:90%
running on the target.

00:12:18.920 --> 00:12:21.760 align:middle line:84%
So we're going to be exploring
multiple techniques, not just

00:12:21.760 --> 00:12:26.380 align:middle line:84%
limited to your standard
authenticated command

00:12:26.380 --> 00:12:29.440 align:middle line:84%
execution techniques
that involve already

00:12:29.440 --> 00:12:30.730 align:middle line:90%
obtained credentials.

00:12:30.730 --> 00:12:32.830 align:middle line:84%
We'll explore a few
other techniques

00:12:32.830 --> 00:12:35.920 align:middle line:84%
that can be used to
exploit the target via SMB

00:12:35.920 --> 00:12:38.420 align:middle line:84%
and consequently
gain remote access.

00:12:38.420 --> 00:12:41.500 align:middle line:84%
So I'll see you
in the next video.

00:12:41.500 --> 00:12:42.000 align:middle line:90%