WEBVTT

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


00:00:04.473 --> 00:00:07.952 align:middle line:90%
[MUSIC PLAYING]

00:00:07.952 --> 00:00:10.440 align:middle line:90%


00:00:10.440 --> 00:00:13.110 align:middle line:84%
Welcome to the Windows
Privilege Escalation

00:00:13.110 --> 00:00:14.790 align:middle line:90%
section of this course.

00:00:14.790 --> 00:00:17.220 align:middle line:84%
In this section, we are
going to be exploring

00:00:17.220 --> 00:00:20.550 align:middle line:84%
the process of identifying
Windows privilege escalation

00:00:20.550 --> 00:00:22.770 align:middle line:84%
vulnerabilities, as
well as exploring

00:00:22.770 --> 00:00:25.590 align:middle line:84%
an example, or a
couple of examples,

00:00:25.590 --> 00:00:30.030 align:middle line:84%
as to how we can elevate our
privileges on a Windows system

00:00:30.030 --> 00:00:32.610 align:middle line:90%
after we've gained access to it.

00:00:32.610 --> 00:00:36.900 align:middle line:84%
And of course, I've already
gone over the post-exploitation

00:00:36.900 --> 00:00:40.860 align:middle line:84%
methodology and where and
if privilege escalation

00:00:40.860 --> 00:00:41.740 align:middle line:90%
fits into it.

00:00:41.740 --> 00:00:46.860 align:middle line:84%
So just to run over that again,
if you gain access to a Windows

00:00:46.860 --> 00:00:50.430 align:middle line:84%
system and you're provided
with elevated privileges

00:00:50.430 --> 00:00:52.770 align:middle line:84%
or anti-authority
system privileges,

00:00:52.770 --> 00:00:56.220 align:middle line:84%
then you can skip over
the privilege escalation

00:00:56.220 --> 00:00:59.430 align:middle line:90%
phase of post-exploitation.

00:00:59.430 --> 00:01:01.650 align:middle line:84%
However, you may need
to go through that phase

00:01:01.650 --> 00:01:06.690 align:middle line:84%
again once you exploit another
system on the target network.

00:01:06.690 --> 00:01:09.180 align:middle line:84%
But we are going to be
running under the assumption

00:01:09.180 --> 00:01:11.220 align:middle line:84%
that you've gained access
to a Windows system

00:01:11.220 --> 00:01:13.570 align:middle line:90%
without elevated privileges.

00:01:13.570 --> 00:01:15.780 align:middle line:84%
And we are starting
off in this video

00:01:15.780 --> 00:01:18.810 align:middle line:84%
with the process of how to
identify Windows privilege

00:01:18.810 --> 00:01:21.160 align:middle line:90%
escalation vulnerabilities.

00:01:21.160 --> 00:01:23.620 align:middle line:90%
So why do we need to do this?

00:01:23.620 --> 00:01:25.950 align:middle line:84%
Well, firstly,
privilege escalation

00:01:25.950 --> 00:01:31.080 align:middle line:84%
is a very complicated step
or phase of post-exploitation

00:01:31.080 --> 00:01:32.650 align:middle line:90%
and for various reasons.

00:01:32.650 --> 00:01:35.790 align:middle line:84%
And again, these are not
just limited to the operating

00:01:35.790 --> 00:01:36.792 align:middle line:90%
systems themselves.

00:01:36.792 --> 00:01:38.250 align:middle line:84%
So it doesn't matter
whether you're

00:01:38.250 --> 00:01:40.410 align:middle line:90%
targeting Windows or Linux.

00:01:40.410 --> 00:01:43.710 align:middle line:84%
There's a plethora of
privilege escalation techniques

00:01:43.710 --> 00:01:46.540 align:middle line:84%
that you can utilize to
elevate your privileges.

00:01:46.540 --> 00:01:49.590 align:middle line:84%
Now, in order to elevate
your privileges on Windows,

00:01:49.590 --> 00:01:52.620 align:middle line:84%
you must first identify
privilege escalation

00:01:52.620 --> 00:01:55.980 align:middle line:84%
vulnerabilities that exist
on the system you have just

00:01:55.980 --> 00:01:56.850 align:middle line:90%
compromised.

00:01:56.850 --> 00:01:59.640 align:middle line:84%
You cannot generalize
privilege escalation.

00:01:59.640 --> 00:02:02.880 align:middle line:84%
The only section or phase
of privilege escalation

00:02:02.880 --> 00:02:05.700 align:middle line:84%
that remains fixed
or is a constant

00:02:05.700 --> 00:02:08.639 align:middle line:84%
is the process of identifying
privilege escalation

00:02:08.639 --> 00:02:09.720 align:middle line:90%
vulnerabilities.

00:02:09.720 --> 00:02:12.840 align:middle line:84%
After that, the techniques,
or the techniques and tools,

00:02:12.840 --> 00:02:15.630 align:middle line:84%
that you will use to
elevate your privileges

00:02:15.630 --> 00:02:19.630 align:middle line:84%
will depend on a few factors,
one of which is, in this case,

00:02:19.630 --> 00:02:22.380 align:middle line:84%
the version of Windows,
as well as the system's

00:02:22.380 --> 00:02:23.820 align:middle line:90%
unique configuration.

00:02:23.820 --> 00:02:26.400 align:middle line:84%
Because Windows systems
are configured differently,

00:02:26.400 --> 00:02:28.500 align:middle line:84%
and based on that
configuration, there

00:02:28.500 --> 00:02:31.110 align:middle line:84%
could be a few
vulnerabilities that

00:02:31.110 --> 00:02:33.780 align:middle line:84%
can be exploited to
elevate your privileges.

00:02:33.780 --> 00:02:37.350 align:middle line:84%
And the same goes for the
various versions or editions

00:02:37.350 --> 00:02:41.100 align:middle line:84%
of Windows and the fact that
there's multiple privilege

00:02:41.100 --> 00:02:42.990 align:middle line:84%
escalation vulnerabilities
that affect

00:02:42.990 --> 00:02:46.710 align:middle line:84%
specific versions of Windows
over a different version

00:02:46.710 --> 00:02:48.120 align:middle line:90%
of Windows.

00:02:48.120 --> 00:02:51.480 align:middle line:84%
Now, it's important, also, to
note that within this section

00:02:51.480 --> 00:02:54.720 align:middle line:84%
I'm not going to be covering
all of the privilege escalation

00:02:54.720 --> 00:02:56.880 align:middle line:84%
vulnerabilities or
techniques that you

00:02:56.880 --> 00:02:58.200 align:middle line:90%
can utilize on Windows.

00:02:58.200 --> 00:03:00.510 align:middle line:84%
I'm simply going through
this and giving you

00:03:00.510 --> 00:03:03.930 align:middle line:84%
an idea of how you can, firstly,
identify privilege escalation

00:03:03.930 --> 00:03:06.330 align:middle line:84%
vulnerabilities on
a Windows system,

00:03:06.330 --> 00:03:09.000 align:middle line:84%
and then, how to
use that information

00:03:09.000 --> 00:03:11.460 align:middle line:84%
to exploit these
vulnerabilities in order

00:03:11.460 --> 00:03:13.830 align:middle line:90%
to elevate your privileges.

00:03:13.830 --> 00:03:16.680 align:middle line:84%
So this process, as
you can already tell,

00:03:16.680 --> 00:03:19.530 align:middle line:84%
can be quite tedious
and time-consuming.

00:03:19.530 --> 00:03:21.630 align:middle line:84%
And as a result,
it is recommended

00:03:21.630 --> 00:03:24.810 align:middle line:84%
to automate the process
of identifying privilege

00:03:24.810 --> 00:03:27.960 align:middle line:90%
escalation vulnerabilities.

00:03:27.960 --> 00:03:29.790 align:middle line:84%
This can obviously be
done through the use

00:03:29.790 --> 00:03:31.770 align:middle line:90%
of various automation scripts.

00:03:31.770 --> 00:03:35.010 align:middle line:84%
Now, we're not really talking
about local enumeration

00:03:35.010 --> 00:03:37.830 align:middle line:84%
anymore or how to automate
local enumeration.

00:03:37.830 --> 00:03:41.100 align:middle line:84%
We're specifically interested
in privilege escalation

00:03:41.100 --> 00:03:42.120 align:middle line:90%
vulnerabilities.

00:03:42.120 --> 00:03:45.240 align:middle line:84%
And in regards to privilege
escalation vulnerability

00:03:45.240 --> 00:03:48.450 align:middle line:84%
scripts that you can
use, one of the best ones

00:03:48.450 --> 00:03:51.120 align:middle line:84%
available that I personally
use and have been using

00:03:51.120 --> 00:03:53.370 align:middle line:90%
for a couple of years now--

00:03:53.370 --> 00:03:57.960 align:middle line:84%
or rather recently-- is
the PrivescCheck script.

00:03:57.960 --> 00:03:59.820 align:middle line:90%
So this is a PowerShell script.

00:03:59.820 --> 00:04:03.060 align:middle line:84%
And it aims to enumerate
common Windows configuration

00:04:03.060 --> 00:04:06.420 align:middle line:84%
issues that can be leveraged
for local privilege escalation.

00:04:06.420 --> 00:04:09.600 align:middle line:84%
It also gathers various
information or various bits

00:04:09.600 --> 00:04:12.810 align:middle line:84%
of information that might
be useful for exploitation

00:04:12.810 --> 00:04:15.340 align:middle line:90%
and/or post exploitation.

00:04:15.340 --> 00:04:17.579 align:middle line:84%
So I've linked the
GitHub repository

00:04:17.579 --> 00:04:20.630 align:middle line:84%
to this particular script,
and you can check it out for

00:04:20.630 --> 00:04:21.130 align:middle line:90%
yourself.

00:04:21.130 --> 00:04:23.430 align:middle line:84%
I'll be navigating
or I'll be taking you

00:04:23.430 --> 00:04:25.110 align:middle line:84%
through the GitHub
repository and how

00:04:25.110 --> 00:04:28.120 align:middle line:90%
to use this particular script.

00:04:28.120 --> 00:04:30.270 align:middle line:84%
And the way it works
is that you gain access

00:04:30.270 --> 00:04:31.750 align:middle line:90%
to a Windows system.

00:04:31.750 --> 00:04:35.130 align:middle line:84%
You then transfer this script
onto the target system,

00:04:35.130 --> 00:04:37.180 align:middle line:84%
and you execute it
with PowerShell.

00:04:37.180 --> 00:04:39.450 align:middle line:84%
It'll then perform
a series of checks

00:04:39.450 --> 00:04:43.500 align:middle line:84%
and identify privilege
escalation vulnerabilities

00:04:43.500 --> 00:04:46.770 align:middle line:84%
that you can exploit to
elevate your privileges.

00:04:46.770 --> 00:04:51.270 align:middle line:84%
Now, this video has a lab
environment attached to it.

00:04:51.270 --> 00:04:54.930 align:middle line:84%
And the lab environment is
set up in a really cool way

00:04:54.930 --> 00:04:56.400 align:middle line:90%
where the target system--

00:04:56.400 --> 00:04:57.960 align:middle line:90%
the target Windows system--

00:04:57.960 --> 00:05:02.160 align:middle line:84%
already has the PrivescCheck
script downloaded

00:05:02.160 --> 00:05:04.120 align:middle line:90%
and set up on the target system.

00:05:04.120 --> 00:05:06.840 align:middle line:84%
So you don't actually have
to go through the process

00:05:06.840 --> 00:05:09.090 align:middle line:84%
of transferring it
from the internet

00:05:09.090 --> 00:05:10.500 align:middle line:90%
onto the lab environment.

00:05:10.500 --> 00:05:12.310 align:middle line:90%
It's already done for you.

00:05:12.310 --> 00:05:14.760 align:middle line:84%
So the first step
in this process,

00:05:14.760 --> 00:05:17.610 align:middle line:84%
or in the practical section,
will involve gaining access

00:05:17.610 --> 00:05:21.420 align:middle line:84%
to the Windows target system,
after which we can then,

00:05:21.420 --> 00:05:24.390 align:middle line:84%
again, take a look at how
to utilize the PrivescCheck

00:05:24.390 --> 00:05:27.630 align:middle line:84%
script to identify a privilege
escalation vulnerability.

00:05:27.630 --> 00:05:30.390 align:middle line:84%
And then, we'll exploit
that vulnerability in order

00:05:30.390 --> 00:05:31.950 align:middle line:90%
to elevate our privileges.

00:05:31.950 --> 00:05:37.990 align:middle line:84%
So without further ado, I'll
see you in the lab environment.

00:05:37.990 --> 00:05:41.350 align:middle line:84%
All right, so I'm back
within the lab environment.

00:05:41.350 --> 00:05:44.650 align:middle line:84%
And you'll be provided
with the target IP address.

00:05:44.650 --> 00:05:46.990 align:middle line:84%
And of course, in your case,
it's going to be different.

00:05:46.990 --> 00:05:49.390 align:middle line:84%
But the really cool thing
with this lab environment

00:05:49.390 --> 00:05:52.690 align:middle line:84%
is that you're not only provided
with access to your Kali

00:05:52.690 --> 00:05:56.260 align:middle line:84%
machine, you're also provide it
with access to your Windows--

00:05:56.260 --> 00:05:59.380 align:middle line:84%
or to the Windows target
system or the victim machine.

00:05:59.380 --> 00:06:02.230 align:middle line:84%
So you can see that the target
system is running Windows.

00:06:02.230 --> 00:06:05.530 align:middle line:84%
And the PrivescCheck
GitHub repository

00:06:05.530 --> 00:06:08.070 align:middle line:84%
has already been saved
onto the desktop here.

00:06:08.070 --> 00:06:09.460 align:middle line:90%
So we're going to be using it.

00:06:09.460 --> 00:06:12.130 align:middle line:84%
Now, the reason you have been
provided with access to both

00:06:12.130 --> 00:06:14.350 align:middle line:84%
is so that in the
event you don't

00:06:14.350 --> 00:06:18.550 align:middle line:84%
want to simulate a real pen
test and the post-exploitation

00:06:18.550 --> 00:06:21.850 align:middle line:84%
phase, you can simply
execute this script directly

00:06:21.850 --> 00:06:25.150 align:middle line:84%
on the victim machine and
take a look at the output

00:06:25.150 --> 00:06:26.720 align:middle line:90%
that it provides for you.

00:06:26.720 --> 00:06:29.230 align:middle line:84%
However, given the
fact that this--

00:06:29.230 --> 00:06:31.840 align:middle line:84%
we are essentially training
to become pen testers,

00:06:31.840 --> 00:06:35.440 align:middle line:84%
we are going to go through this
as if it were a simulated pen

00:06:35.440 --> 00:06:36.280 align:middle line:90%
test.

00:06:36.280 --> 00:06:40.210 align:middle line:84%
So we are going to copy
over this target IP.

00:06:40.210 --> 00:06:43.510 align:middle line:84%
Now, the target system doesn't
have any vulnerable services

00:06:43.510 --> 00:06:44.360 align:middle line:90%
running on it.

00:06:44.360 --> 00:06:47.050 align:middle line:84%
So the way we are going to
gain access to the system

00:06:47.050 --> 00:06:49.870 align:middle line:84%
is by utilizing a
Metasploit framework

00:06:49.870 --> 00:06:52.360 align:middle line:90%
module called web delivery.

00:06:52.360 --> 00:06:55.370 align:middle line:84%
And I'll just open up a new
terminal and I'll zoom in here.

00:06:55.370 --> 00:06:58.540 align:middle line:90%
So I'll say msfconsole.

00:06:58.540 --> 00:07:00.025 align:middle line:84%
Let me make sure
that is visible.

00:07:00.025 --> 00:07:03.650 align:middle line:90%


00:07:03.650 --> 00:07:04.650 align:middle line:90%
All right, there we are.

00:07:04.650 --> 00:07:06.050 align:middle line:90%
It looks like it's started.

00:07:06.050 --> 00:07:07.910 align:middle line:84%
And I'm going to
search for the modules.

00:07:07.910 --> 00:07:10.550 align:middle line:84%
I'm going to say search
for web delivery--

00:07:10.550 --> 00:07:12.470 align:middle line:90%
so web underscore delivery.

00:07:12.470 --> 00:07:15.690 align:middle line:84%
And we are going to use the
following exploit modules.

00:07:15.690 --> 00:07:18.890 align:middle line:84%
So it is exploit, multi
script, web delivery.

00:07:18.890 --> 00:07:21.530 align:middle line:84%
And I'll explain what it's used
for in a couple of seconds.

00:07:21.530 --> 00:07:23.300 align:middle line:90%
So I'll say use 1.

00:07:23.300 --> 00:07:23.960 align:middle line:90%
There we are.

00:07:23.960 --> 00:07:26.570 align:middle line:84%
And don't worry about
it automatically

00:07:26.570 --> 00:07:27.650 align:middle line:90%
specifying the payload.

00:07:27.650 --> 00:07:30.450 align:middle line:84%
We'll actually set all of
these options as required.

00:07:30.450 --> 00:07:33.210 align:middle line:90%
So I'll say show options.

00:07:33.210 --> 00:07:36.150 align:middle line:84%
And we can show the info here
really quickly so that you

00:07:36.150 --> 00:07:38.010 align:middle line:90%
understand what it does.

00:07:38.010 --> 00:07:40.230 align:middle line:84%
All right, so if
we show the info

00:07:40.230 --> 00:07:42.540 align:middle line:84%
for this particular
module, you can

00:07:42.540 --> 00:07:45.180 align:middle line:84%
see that it says right
over here under Description

00:07:45.180 --> 00:07:47.490 align:middle line:84%
that this module
quickly fires up a web

00:07:47.490 --> 00:07:49.770 align:middle line:90%
server that serves a payload.

00:07:49.770 --> 00:07:54.180 align:middle line:84%
The provided command, which will
allow for a payload to download

00:07:54.180 --> 00:07:57.240 align:middle line:84%
and execute-- and that's the
command will be copying over

00:07:57.240 --> 00:08:00.210 align:middle line:84%
to the victim machine and
executing it within a command

00:08:00.210 --> 00:08:01.200 align:middle line:90%
prompt--

00:08:01.200 --> 00:08:04.950 align:middle line:84%
it'll either do a specific--
or it will do it in either

00:08:04.950 --> 00:08:10.470 align:middle line:84%
a specified scripting language
interpreter or it will use

00:08:10.470 --> 00:08:15.390 align:middle line:84%
the squiblydoo via the
regsvr32 or Reg Server 32 .exe

00:08:15.390 --> 00:08:17.700 align:middle line:84%
for bypassing the
application whitelisting.

00:08:17.700 --> 00:08:19.650 align:middle line:84%
Essentially, what's
happening here

00:08:19.650 --> 00:08:22.680 align:middle line:84%
is this particular
exploit module

00:08:22.680 --> 00:08:26.070 align:middle line:84%
sets up a web server that hosts
a payload based on the target

00:08:26.070 --> 00:08:28.470 align:middle line:90%
operating system.

00:08:28.470 --> 00:08:32.460 align:middle line:84%
Once you hit Exploit, it then
generates some PowerShell code,

00:08:32.460 --> 00:08:34.770 align:middle line:84%
because in this case,
we're targeting Windows.

00:08:34.770 --> 00:08:38.100 align:middle line:84%
And this particular module
supports Python PHP Windows

00:08:38.100 --> 00:08:38.820 align:middle line:90%
Linux.

00:08:38.820 --> 00:08:40.559 align:middle line:84%
We'll then copy
that PowerShell code

00:08:40.559 --> 00:08:44.460 align:middle line:84%
and execute it on the target
system, which will consequently

00:08:44.460 --> 00:08:47.430 align:middle line:84%
download the payload that is
being hosted on the web server

00:08:47.430 --> 00:08:48.690 align:middle line:90%
and execute it.

00:08:48.690 --> 00:08:50.670 align:middle line:84%
That will consequently
provide us

00:08:50.670 --> 00:08:53.860 align:middle line:84%
with a standard
Command Shell session,

00:08:53.860 --> 00:08:56.698 align:middle line:84%
which we can then upgrade
to a Meterpreter session.

00:08:56.698 --> 00:08:58.740 align:middle line:84%
All right, so let me just
clear out the terminal.

00:08:58.740 --> 00:09:01.290 align:middle line:84%
And if I show the
options here, you

00:09:01.290 --> 00:09:04.140 align:middle line:84%
can see that the option that
we are really interested in

00:09:04.140 --> 00:09:06.750 align:middle line:84%
is the target and
the actual payload.

00:09:06.750 --> 00:09:08.940 align:middle line:84%
So for the target, we're
going to set the target

00:09:08.940 --> 00:09:09.870 align:middle line:90%
to PowerShell.

00:09:09.870 --> 00:09:12.330 align:middle line:84%
So I'll say, set
target to PowerShell,

00:09:12.330 --> 00:09:14.220 align:middle line:84%
and we're going to
use the binary option.

00:09:14.220 --> 00:09:17.130 align:middle line:84%
So set target,
PowerShell, binary.

00:09:17.130 --> 00:09:20.280 align:middle line:84%
We are then going
to set the payload.

00:09:20.280 --> 00:09:23.290 align:middle line:84%
We're going to obtain a simple
command PowerShell session.

00:09:23.290 --> 00:09:28.410 align:middle line:84%
So we're going to say,
Windows, shell, reverse tcp.

00:09:28.410 --> 00:09:30.840 align:middle line:90%
All right, so we'll hit Enter.

00:09:30.840 --> 00:09:33.120 align:middle line:84%
We also want to
disable PowerShell--

00:09:33.120 --> 00:09:34.920 align:middle line:84%
we also want to
disable the PowerShell

00:09:34.920 --> 00:09:37.350 align:middle line:90%
code from being encoded Base64.

00:09:37.350 --> 00:09:41.400 align:middle line:84%
So we'll say, set
PowerShell encoded.

00:09:41.400 --> 00:09:42.900 align:middle line:84%
Let me just type
that in correctly

00:09:42.900 --> 00:09:47.340 align:middle line:84%
with the correct case-- so
encoded command-- to false.

00:09:47.340 --> 00:09:49.200 align:middle line:84%
And if we show the
options, now, we still

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

00:09:50.850 --> 00:09:54.390 align:middle line:84%
So we need to set up the LHOST
value, which is the Kali Linux

00:09:54.390 --> 00:09:55.230 align:middle line:90%
IP.

00:09:55.230 --> 00:09:58.410 align:middle line:84%
So the Kali Linux IP
we can easily set that

00:09:58.410 --> 00:10:02.580 align:middle line:84%
by saying set LHOST, and we can
set it to the value associated

00:10:02.580 --> 00:10:05.040 align:middle line:90%
with the interface ethernet 1.

00:10:05.040 --> 00:10:07.530 align:middle line:84%
You can see that's going to
set your Kali Linux IP address.

00:10:07.530 --> 00:10:11.850 align:middle line:84%
And we can leave
the LPORT as 4444.

00:10:11.850 --> 00:10:15.150 align:middle line:84%
Once we hit Exploit,
you'll see that it'll

00:10:15.150 --> 00:10:16.620 align:middle line:90%
generate some PowerShell code.

00:10:16.620 --> 00:10:19.980 align:middle line:84%
So I want you to copy all of
this PowerShell code right

00:10:19.980 --> 00:10:20.910 align:middle line:90%
over here.

00:10:20.910 --> 00:10:25.890 align:middle line:84%
And just don't worry about
this not displaying any output.

00:10:25.890 --> 00:10:28.230 align:middle line:84%
And head over to
the victim system,

00:10:28.230 --> 00:10:31.830 align:middle line:84%
and we'll open up the search
menu here and open up a command

00:10:31.830 --> 00:10:32.520 align:middle line:90%
prompt session.

00:10:32.520 --> 00:10:34.122 align:middle line:90%
So we'll say cmd.

00:10:34.122 --> 00:10:35.580 align:middle line:84%
All right, we'll
give this a couple

00:10:35.580 --> 00:10:39.750 align:middle line:84%
of seconds, as this, of course,
is running in the cloud.

00:10:39.750 --> 00:10:40.860 align:middle line:90%
So there we are-- cmd.

00:10:40.860 --> 00:10:44.140 align:middle line:90%


00:10:44.140 --> 00:10:45.880 align:middle line:84%
And we'll open up
the command prompt.

00:10:45.880 --> 00:10:48.190 align:middle line:84%
And just right click
within the command

00:10:48.190 --> 00:10:51.040 align:middle line:84%
prompt, and that will paste in
the command that you copied.

00:10:51.040 --> 00:10:52.540 align:middle line:90%
We then hit Enter.

00:10:52.540 --> 00:10:54.910 align:middle line:84%
Don't worry if the
window disappears.

00:10:54.910 --> 00:10:57.010 align:middle line:84%
If you take a look
at the Kali system,

00:10:57.010 --> 00:10:59.840 align:middle line:84%
you can see that it's going
to say Command Shell Session 1

00:10:59.840 --> 00:11:00.340 align:middle line:90%
open.

00:11:00.340 --> 00:11:03.800 align:middle line:84%
So we have obtained access
to the target system.

00:11:03.800 --> 00:11:06.520 align:middle line:84%
So if I hit Enter
and type in sessions,

00:11:06.520 --> 00:11:08.120 align:middle line:90%
you can see we have access.

00:11:08.120 --> 00:11:10.090 align:middle line:90%
So I can say, sessions 1.

00:11:10.090 --> 00:11:12.550 align:middle line:84%
And we currently have
access to the target system

00:11:12.550 --> 00:11:15.370 align:middle line:84%
through a simple
Command Shell Session.

00:11:15.370 --> 00:11:17.560 align:middle line:84%
And of course, we are
currently we currently

00:11:17.560 --> 00:11:20.960 align:middle line:84%
have access as the user student,
which we can confirm by saying,

00:11:20.960 --> 00:11:22.950 align:middle line:90%
who am I?

00:11:22.950 --> 00:11:25.830 align:middle line:84%
And you can see, we're
currently the student user.

00:11:25.830 --> 00:11:28.920 align:middle line:84%
And the host name
is attack defense.

00:11:28.920 --> 00:11:31.230 align:middle line:84%
You can also verify
that by saying hostname.

00:11:31.230 --> 00:11:35.550 align:middle line:84%
We've already gone over this,
so you can see how that is done.

00:11:35.550 --> 00:11:38.370 align:middle line:84%
All right, so before we
actually move forward,

00:11:38.370 --> 00:11:41.550 align:middle line:84%
I want to migrate this command
session to a Meterpreter

00:11:41.550 --> 00:11:42.240 align:middle line:90%
session.

00:11:42.240 --> 00:11:45.928 align:middle line:84%
So I'll use the key
combination Control and Z

00:11:45.928 --> 00:11:47.220 align:middle line:90%
and put this in the background.

00:11:47.220 --> 00:11:49.380 align:middle line:84%
Or you can simply
type in background.

00:11:49.380 --> 00:11:52.680 align:middle line:84%
I'm then going to search
for the module Shell 2.

00:11:52.680 --> 00:11:55.500 align:middle line:84%
So shell underscore 2, and
we're looking for the Shell 2

00:11:55.500 --> 00:11:56.550 align:middle line:90%
Meterpreter module.

00:11:56.550 --> 00:11:58.448 align:middle line:90%
So I'll say use 0.

00:11:58.448 --> 00:12:00.490 align:middle line:84%
And there's a few things
that we need to do here.

00:12:00.490 --> 00:12:03.250 align:middle line:84%
So because this is a
post-exploitation module,

00:12:03.250 --> 00:12:06.592 align:middle line:84%
we need to set the LHOST
option, because it's

00:12:06.592 --> 00:12:08.550 align:middle line:84%
going to provide us with
a Meterpreter session.

00:12:08.550 --> 00:12:11.121 align:middle line:90%
So we'll set that to ethernet 1.

00:12:11.121 --> 00:12:14.360 align:middle line:84%
We then need to set the
session option to session 1.

00:12:14.360 --> 00:12:18.630 align:middle line:84%
That's the actual ID of
the Command Shell session.

00:12:18.630 --> 00:12:22.580 align:middle line:84%
And if we show advanced, we
need to set an additional option

00:12:22.580 --> 00:12:24.410 align:middle line:90%
that is on the WIN TRANSFER.

00:12:24.410 --> 00:12:27.410 align:middle line:84%
So instead of setting the
transfer method to PowerShell,

00:12:27.410 --> 00:12:30.650 align:middle line:84%
we want to set that
to Visual Basic.

00:12:30.650 --> 00:12:35.465 align:middle line:84%
So we'll say, set WIN
underscore TRANSFER to VBS.

00:12:35.465 --> 00:12:38.505 align:middle line:90%


00:12:38.505 --> 00:12:40.380 align:middle line:84%
And if we show the
options one more time just

00:12:40.380 --> 00:12:42.640 align:middle line:84%
to confirm that everything
is set correctly,

00:12:42.640 --> 00:12:44.880 align:middle line:84%
make sure the LPORT
is not in conflict

00:12:44.880 --> 00:12:47.160 align:middle line:84%
with your current
Command Shell session.

00:12:47.160 --> 00:12:49.440 align:middle line:84%
You can see that the
Command Shell session

00:12:49.440 --> 00:12:51.870 align:middle line:90%
is running on Port 4444.

00:12:51.870 --> 00:12:55.360 align:middle line:84%
And make sure that it doesn't
conflict with this option here.

00:12:55.360 --> 00:12:57.630 align:middle line:84%
Once that is done,
we can hit Exploit.

00:12:57.630 --> 00:12:59.970 align:middle line:84%
And we should receive
a Meterpreter session.

00:12:59.970 --> 00:13:01.800 align:middle line:84%
So we'll give this
a couple of seconds.

00:13:01.800 --> 00:13:05.040 align:middle line:84%
It should send the
actual command stager.

00:13:05.040 --> 00:13:07.275 align:middle line:84%
So we'll just give this
a couple of seconds.

00:13:07.275 --> 00:13:14.050 align:middle line:90%


00:13:14.050 --> 00:13:16.030 align:middle line:84%
All right, so after
a couple of seconds,

00:13:16.030 --> 00:13:18.430 align:middle line:84%
you can see that it
will send the command

00:13:18.430 --> 00:13:21.760 align:middle line:84%
stager, after which you will
receive a Meterpreter session.

00:13:21.760 --> 00:13:22.510 align:middle line:90%
There we are.

00:13:22.510 --> 00:13:24.670 align:middle line:84%
So it's going to stop the
exploit multi-handler.

00:13:24.670 --> 00:13:27.850 align:middle line:84%
And if I type in sessions,
you can see we have session 2,

00:13:27.850 --> 00:13:29.620 align:middle line:84%
and that is the
Meterpreter session.

00:13:29.620 --> 00:13:32.080 align:middle line:90%
So I'll say sessions 2.

00:13:32.080 --> 00:13:34.000 align:middle line:84%
And we'll just clear
out the terminals.

00:13:34.000 --> 00:13:37.510 align:middle line:84%
So I can say, sysinfo to learn
more about the target system.

00:13:37.510 --> 00:13:39.970 align:middle line:84%
You can see that the
hostname is ATTACKDEFENSE.

00:13:39.970 --> 00:13:46.180 align:middle line:84%
The target is running a Windows
Server 2016, build 17763.

00:13:46.180 --> 00:13:49.060 align:middle line:84%
The operating system
architecture is 64-bit,

00:13:49.060 --> 00:13:51.040 align:middle line:84%
and our Meterpreter
session is 32-bit.

00:13:51.040 --> 00:13:53.890 align:middle line:90%


00:13:53.890 --> 00:13:56.310 align:middle line:84%
We can migrate to
a 64-bit process.

00:13:56.310 --> 00:14:00.340 align:middle line:84%
So I'm going to say, ps, and
we can migrate to explorer.exe.

00:14:00.340 --> 00:14:01.840 align:middle line:84%
So let's see if we
can identify it.

00:14:01.840 --> 00:14:04.060 align:middle line:84%
You can see that
it's only displaying

00:14:04.060 --> 00:14:07.360 align:middle line:84%
the actual privileges
associated with the user

00:14:07.360 --> 00:14:11.050 align:middle line:84%
that we currently have access
to for specific processes.

00:14:11.050 --> 00:14:13.300 align:middle line:84%
And the rest of the
processes-- that means

00:14:13.300 --> 00:14:15.550 align:middle line:84%
are currently running
with privileges

00:14:15.550 --> 00:14:19.450 align:middle line:84%
of other users or authority
system or service privileges.

00:14:19.450 --> 00:14:22.010 align:middle line:84%
And that means we
cannot migrate to them.

00:14:22.010 --> 00:14:24.760 align:middle line:84%
So let's see if I can
identify Explorer here.

00:14:24.760 --> 00:14:27.640 align:middle line:90%


00:14:27.640 --> 00:14:30.170 align:middle line:84%
We should be able to
find it around here.

00:14:30.170 --> 00:14:34.110 align:middle line:84%
Let's see if I can find
it right over here.

00:14:34.110 --> 00:14:35.060 align:middle line:90%
So we have Explorer.

00:14:35.060 --> 00:14:38.550 align:middle line:84%
So we want to target
this one here.

00:14:38.550 --> 00:14:41.600 align:middle line:90%
So the process ID is 3624.

00:14:41.600 --> 00:14:47.850 align:middle line:84%
So I'm going to
say, migrate 3624.

00:14:47.850 --> 00:14:51.210 align:middle line:84%
And it's going to migrate
into the explorer.exe process

00:14:51.210 --> 00:14:52.620 align:middle line:90%
for stability.

00:14:52.620 --> 00:14:55.860 align:middle line:84%
All right, so if I say, get user
ID, you can see it's student.

00:14:55.860 --> 00:14:58.950 align:middle line:84%
And we can now confirm that
this user is unprivileged.

00:14:58.950 --> 00:15:01.980 align:middle line:84%
So if I say, getprivs, you
can see that this user only

00:15:01.980 --> 00:15:03.400 align:middle line:90%
has two privileges.

00:15:03.400 --> 00:15:06.400 align:middle line:84%
And we now need to
elevate our privileges.

00:15:06.400 --> 00:15:09.210 align:middle line:84%
So what we can do now,
is let's open up--

00:15:09.210 --> 00:15:12.180 align:middle line:84%
or let's navigate to
the root of the C Drive

00:15:12.180 --> 00:15:14.500 align:middle line:90%
and then to the Users Directory.

00:15:14.500 --> 00:15:17.490 align:middle line:84%
So I'll say, cd
Users and cd Student.

00:15:17.490 --> 00:15:21.820 align:middle line:84%
And on the desktop, we're
going to have the PrivescCheck

00:15:21.820 --> 00:15:22.370 align:middle line:90%
directory.

00:15:22.370 --> 00:15:24.230 align:middle line:90%
So I'll navigate into that.

00:15:24.230 --> 00:15:27.290 align:middle line:84%
And if I list all the
content of this directory,

00:15:27.290 --> 00:15:29.890 align:middle line:84%
you can see we have the
PrivescCheck PowerShell script

00:15:29.890 --> 00:15:31.210 align:middle line:90%
right over here.

00:15:31.210 --> 00:15:34.390 align:middle line:84%
And we can open up a
Command Shell session, now.

00:15:34.390 --> 00:15:37.210 align:middle line:84%
And we can now head over
to the GitHub repository

00:15:37.210 --> 00:15:38.890 align:middle line:84%
to, essentially,
take a look at how

00:15:38.890 --> 00:15:40.790 align:middle line:90%
to run this particular script.

00:15:40.790 --> 00:15:43.468 align:middle line:84%
So let me just switch
over to my browser.

00:15:43.468 --> 00:15:45.010 align:middle line:84%
All right, so I'm
back in my browser,

00:15:45.010 --> 00:15:47.230 align:middle line:84%
and I'm currently on
the PrivescCheck GitHub

00:15:47.230 --> 00:15:48.970 align:middle line:90%
repository, as you can see.

00:15:48.970 --> 00:15:51.100 align:middle line:84%
And this GitHub
repository contains

00:15:51.100 --> 00:15:53.230 align:middle line:84%
the build PowerShell
script, as well as

00:15:53.230 --> 00:15:56.240 align:middle line:84%
the PrivescCheck PowerShell
script right over here.

00:15:56.240 --> 00:15:58.510 align:middle line:84%
And you can go through
the documentation.

00:15:58.510 --> 00:16:01.600 align:middle line:84%
For the usage, it
has various options

00:16:01.600 --> 00:16:05.620 align:middle line:84%
based on your current
level or type of access

00:16:05.620 --> 00:16:08.090 align:middle line:84%
that you have on
the target system.

00:16:08.090 --> 00:16:10.000 align:middle line:84%
So if you have access
to the target system

00:16:10.000 --> 00:16:12.700 align:middle line:84%
through a standard Command
Shell session, which

00:16:12.700 --> 00:16:16.270 align:middle line:84%
is what we have here, then
copy this command here,

00:16:16.270 --> 00:16:20.440 align:middle line:84%
as this is what will be
used to essentially execute

00:16:20.440 --> 00:16:24.160 align:middle line:84%
the Privesc PowerShell script,
or the PrivescCheck PowerShell

00:16:24.160 --> 00:16:24.880 align:middle line:90%
script.

00:16:24.880 --> 00:16:27.490 align:middle line:84%
And again, make sure
that you execute

00:16:27.490 --> 00:16:30.580 align:middle line:84%
this within the
PrivescCheck directory

00:16:30.580 --> 00:16:32.320 align:middle line:90%
on the student user's desktop.

00:16:32.320 --> 00:16:33.670 align:middle line:90%
So I'll copy this.

00:16:33.670 --> 00:16:36.410 align:middle line:84%
And again, you can take
a look at other options.

00:16:36.410 --> 00:16:38.500 align:middle line:84%
For example, if you have
a PowerShell session

00:16:38.500 --> 00:16:43.180 align:middle line:84%
on the target system, then you
can use the following commands

00:16:43.180 --> 00:16:44.860 align:middle line:90%
to execute it.

00:16:44.860 --> 00:16:47.620 align:middle line:84%
And right at the top here, this
is the command we're copying.

00:16:47.620 --> 00:16:49.540 align:middle line:84%
The way it works is
we essentially saying,

00:16:49.540 --> 00:16:51.760 align:middle line:90%
PowerShell--

00:16:51.760 --> 00:16:53.530 align:middle line:90%
the actual execution policy--

00:16:53.530 --> 00:16:57.260 align:middle line:84%
set to bypass for the execution
of this particular script.

00:16:57.260 --> 00:16:59.300 align:middle line:84%
And then, we specify
the script itself.

00:16:59.300 --> 00:17:01.360 align:middle line:84%
And then, we invoke
PrivescCheck.

00:17:01.360 --> 00:17:03.280 align:middle line:84%
And that should begin
performing the check.

00:17:03.280 --> 00:17:04.720 align:middle line:90%
So just make sure you copy that.

00:17:04.720 --> 00:17:07.977 align:middle line:84%
And let me switch over
to the lab environment.

00:17:07.977 --> 00:17:10.060 align:middle line:84%
All right, so I'm back
within the lab environment.

00:17:10.060 --> 00:17:12.329 align:middle line:84%
And again, you can
essentially paste that

00:17:12.329 --> 00:17:15.329 align:middle line:84%
into the lab
environment clipboard

00:17:15.329 --> 00:17:18.210 align:middle line:84%
by using the following keyboard
combination-- so Control,

00:17:18.210 --> 00:17:20.560 align:middle line:90%
Shift, and Alt all altogether.

00:17:20.560 --> 00:17:23.490 align:middle line:84%
And you can see, it's already
added to my clipboard.

00:17:23.490 --> 00:17:25.740 align:middle line:84%
So once you've
pasted it in there,

00:17:25.740 --> 00:17:28.710 align:middle line:84%
you can just close this by
saying Control, Shift, and Alt.

00:17:28.710 --> 00:17:31.620 align:middle line:84%
And now, if I say Control,
Shift, V to paste it

00:17:31.620 --> 00:17:36.180 align:middle line:84%
into my current session on the
target system and I hit Enter,

00:17:36.180 --> 00:17:38.153 align:middle line:84%
it is going to
execute the script.

00:17:38.153 --> 00:17:38.820 align:middle line:90%
So there we are.

00:17:38.820 --> 00:17:41.670 align:middle line:84%
It's beginning to
perform all the checks.

00:17:41.670 --> 00:17:45.120 align:middle line:84%
So give this a couple of
seconds to a couple of minutes

00:17:45.120 --> 00:17:45.840 align:middle line:90%
to complete it.

00:17:45.840 --> 00:17:48.720 align:middle line:84%
Shouldn't take too much time
at all, after which we'll

00:17:48.720 --> 00:17:51.900 align:middle line:84%
be able to, essentially, go
through all the vulnerabilities

00:17:51.900 --> 00:17:54.600 align:middle line:84%
that we've been able
to identify and explore

00:17:54.600 --> 00:17:56.230 align:middle line:90%
how they can be exploited.

00:17:56.230 --> 00:18:00.400 align:middle line:84%
So again, just give this
a couple of seconds.

00:18:00.400 --> 00:18:02.560 align:middle line:84%
All right, so once it's
done, at the bottom

00:18:02.560 --> 00:18:06.250 align:middle line:84%
it will give you a summary
or the PrivescCheck report,

00:18:06.250 --> 00:18:09.280 align:middle line:84%
which will essentially take
you through a list of checks

00:18:09.280 --> 00:18:11.800 align:middle line:84%
that it performed in regards
to privilege escalation

00:18:11.800 --> 00:18:13.000 align:middle line:90%
vulnerabilities.

00:18:13.000 --> 00:18:15.910 align:middle line:84%
And if it identified
a specific result,

00:18:15.910 --> 00:18:19.270 align:middle line:84%
it would highlight that next
to the particular check.

00:18:19.270 --> 00:18:21.790 align:middle line:84%
And they are based on
different types of checks.

00:18:21.790 --> 00:18:24.910 align:middle line:84%
So for example,
privilege escalation

00:18:24.910 --> 00:18:27.820 align:middle line:84%
via poor configurations
or by Windows features

00:18:27.820 --> 00:18:32.080 align:middle line:84%
that have been enabled, these
are highlighted as CONFIG.

00:18:32.080 --> 00:18:35.530 align:middle line:84%
It'll then check for privilege
escalation vulnerabilities

00:18:35.530 --> 00:18:38.710 align:middle line:84%
that fall into credentials
and credential management.

00:18:38.710 --> 00:18:41.500 align:middle line:84%
So it'll check for
WinLogon credentials.

00:18:41.500 --> 00:18:44.110 align:middle line:84%
It'll also check for
SAM and system backup

00:18:44.110 --> 00:18:48.790 align:middle line:84%
files, unattended installation
files, GPP passwords.

00:18:48.790 --> 00:18:50.080 align:middle line:90%
By the way, I already--

00:18:50.080 --> 00:18:53.080 align:middle line:84%
I have covered how to elevate
your privileges on a Windows

00:18:53.080 --> 00:18:55.900 align:middle line:84%
system through the unattended
installation files.

00:18:55.900 --> 00:18:59.160 align:middle line:84%
And I cover that in the system
and host-based attacks course.

00:18:59.160 --> 00:19:01.370 align:middle line:84%
So if you'd like to
learn more about that,

00:19:01.370 --> 00:19:02.470 align:middle line:90%
you can check it there.

00:19:02.470 --> 00:19:05.530 align:middle line:84%
And then, of course, it'll
also essentially perform

00:19:05.530 --> 00:19:07.510 align:middle line:90%
checks on the hardening.

00:19:07.510 --> 00:19:09.510 align:middle line:84%
So it'll tell you
whether BitLocker-- there

00:19:09.510 --> 00:19:12.370 align:middle line:84%
are any vulnerabilities
within BitLocker.

00:19:12.370 --> 00:19:16.630 align:middle line:84%
The Credential Guard, LSA
protection, Hijackable DLLs,

00:19:16.630 --> 00:19:21.430 align:middle line:84%
under Scheduled Tasks, if
there are any services that

00:19:21.430 --> 00:19:25.270 align:middle line:84%
have misconfigured binary
permissions or unquoted parts,

00:19:25.270 --> 00:19:26.410 align:middle line:90%
it'll tell you that there.

00:19:26.410 --> 00:19:28.810 align:middle line:84%
Under SERVICES,
it'll essentially

00:19:28.810 --> 00:19:33.130 align:middle line:84%
check for non-default services,
for misconfigured binary

00:19:33.130 --> 00:19:36.580 align:middle line:84%
permissions, for unquoted
parts, for service permissions,

00:19:36.580 --> 00:19:39.970 align:middle line:84%
for weak service permissions,
and for misconfigured registry

00:19:39.970 --> 00:19:41.140 align:middle line:90%
permissions.

00:19:41.140 --> 00:19:43.360 align:middle line:84%
It'll also perform--
check on UPDATES

00:19:43.360 --> 00:19:46.630 align:middle line:84%
to essentially verify or to
check whether your system is

00:19:46.630 --> 00:19:47.260 align:middle line:90%
up to date.

00:19:47.260 --> 00:19:50.620 align:middle line:84%
It'll also enumerate
the hotfixes installed.

00:19:50.620 --> 00:19:52.840 align:middle line:84%
It'll then perform
your standard user--

00:19:52.840 --> 00:19:56.980 align:middle line:84%
your user checks, so users and
groups, identity, environment,

00:19:56.980 --> 00:19:58.750 align:middle line:90%
privileges, et cetera.

00:19:58.750 --> 00:20:00.808 align:middle line:84%
So let's scroll to the
top of the results,

00:20:00.808 --> 00:20:02.350 align:middle line:84%
because there are
quite a few results

00:20:02.350 --> 00:20:04.070 align:middle line:90%
that we need to explore here.

00:20:04.070 --> 00:20:06.220 align:middle line:84%
So I'll just navigate
all the way to the top

00:20:06.220 --> 00:20:09.430 align:middle line:90%
here where it actually began.

00:20:09.430 --> 00:20:10.130 align:middle line:90%
So there we are.

00:20:10.130 --> 00:20:11.420 align:middle line:90%
That's where we executed it.

00:20:11.420 --> 00:20:15.790 align:middle line:84%
So firstly, you can see
that it is essentially

00:20:15.790 --> 00:20:19.100 align:middle line:84%
going to start off with
USER and Groups here.

00:20:19.100 --> 00:20:21.760 align:middle line:84%
So it will display
a list of all users

00:20:21.760 --> 00:20:24.340 align:middle line:84%
on the system, as
well as groups.

00:20:24.340 --> 00:20:28.360 align:middle line:84%
So you can see that right over
here, these are all the Groups.

00:20:28.360 --> 00:20:30.380 align:middle line:84%
So you have your
standard users group.

00:20:30.380 --> 00:20:33.430 align:middle line:84%
And we should have the
local administrators group.

00:20:33.430 --> 00:20:36.490 align:middle line:84%
That should be displayed
somewhere over here.

00:20:36.490 --> 00:20:39.530 align:middle line:84%
If it's not displayed,
that's perfectly fine.

00:20:39.530 --> 00:20:42.400 align:middle line:84%
And then, right over here,
it'll display your current user

00:20:42.400 --> 00:20:44.500 align:middle line:84%
privileges, which
we already did,

00:20:44.500 --> 00:20:46.810 align:middle line:84%
the current user environment
variables-- remember,

00:20:46.810 --> 00:20:49.000 align:middle line:84%
it's performing these
checks and identifying

00:20:49.000 --> 00:20:51.190 align:middle line:84%
whether there are
any vulnerabilities

00:20:51.190 --> 00:20:54.820 align:middle line:84%
within these particular
files or configurations that

00:20:54.820 --> 00:20:55.790 align:middle line:90%
can be exploited.

00:20:55.790 --> 00:20:58.832 align:middle line:84%
So for example, in the case
of environment variables,

00:20:58.832 --> 00:21:00.790 align:middle line:84%
you can see that this
will list the environment

00:21:00.790 --> 00:21:03.190 align:middle line:84%
variables of the
current process and try

00:21:03.190 --> 00:21:06.040 align:middle line:84%
to identify any potentially
sensitive information,

00:21:06.040 --> 00:21:08.530 align:middle line:84%
such as passwords
or API secrets.

00:21:08.530 --> 00:21:11.260 align:middle line:84%
This check is simply
based on keyword matching

00:21:11.260 --> 00:21:13.870 align:middle line:84%
and might not
entirely be reliable.

00:21:13.870 --> 00:21:17.590 align:middle line:84%
It'll then perform checks
for the non-default services.

00:21:17.590 --> 00:21:19.660 align:middle line:84%
This will list all
registered services

00:21:19.660 --> 00:21:22.630 align:middle line:84%
and filter out the ones
that are built into Windows.

00:21:22.630 --> 00:21:26.300 align:middle line:84%
It does so by passing the
target executables metadata.

00:21:26.300 --> 00:21:30.270 align:middle line:84%
So these are all the
non-default services.

00:21:30.270 --> 00:21:32.400 align:middle line:84%
And then, of course, you
have service permissions.

00:21:32.400 --> 00:21:35.310 align:middle line:84%
And right at the bottom,
it'll tell you not vulnerable.

00:21:35.310 --> 00:21:37.410 align:middle line:84%
So that means that their
vulnerabilities do not

00:21:37.410 --> 00:21:41.970 align:middle line:84%
exist in regards to privilege
escalation vulnerabilities.

00:21:41.970 --> 00:21:45.660 align:middle line:84%
And of course, where
results are produced--

00:21:45.660 --> 00:21:48.390 align:middle line:84%
if we can actually
identify them here--

00:21:48.390 --> 00:21:50.910 align:middle line:84%
you can see under
Credentials, WinLogon.

00:21:50.910 --> 00:21:53.850 align:middle line:84%
You can see that this will parse
the Winlogon on registry keys

00:21:53.850 --> 00:21:57.000 align:middle line:84%
and check whether they contain
any clear text passwords.

00:21:57.000 --> 00:21:59.910 align:middle line:84%
Entries that have an
empty password field

00:21:59.910 --> 00:22:00.790 align:middle line:90%
are filtered out.

00:22:00.790 --> 00:22:02.730 align:middle line:84%
So it found one
result, and it actually

00:22:02.730 --> 00:22:07.060 align:middle line:84%
has provided us with the
administrator credentials.

00:22:07.060 --> 00:22:08.700 align:middle line:84%
So in the next
video, we'll actually

00:22:08.700 --> 00:22:10.560 align:middle line:84%
be taking a look at
how we can utilize

00:22:10.560 --> 00:22:13.440 align:middle line:84%
these credentials to
elevate our privileges

00:22:13.440 --> 00:22:17.170 align:middle line:84%
and how we can authenticate to
the target system with them.

00:22:17.170 --> 00:22:20.610 align:middle line:84%
So in terms of other results
that it was able to find,

00:22:20.610 --> 00:22:23.400 align:middle line:84%
we can see under
LSA Protection, it

00:22:23.400 --> 00:22:27.780 align:middle line:84%
tells us right away here that
RunAsPPL is not configured.

00:22:27.780 --> 00:22:30.450 align:middle line:84%
Under Hardening,
the Credential Guard

00:22:30.450 --> 00:22:31.900 align:middle line:90%
is not configured, as well.

00:22:31.900 --> 00:22:36.430 align:middle line:84%
So this system is actually
secured quite well.

00:22:36.430 --> 00:22:38.040 align:middle line:84%
And the only
vulnerability that we

00:22:38.040 --> 00:22:41.280 align:middle line:84%
were able to find that can
help us elevate our privileges

00:22:41.280 --> 00:22:44.330 align:middle line:90%
is through the WinLogon feature.

00:22:44.330 --> 00:22:46.730 align:middle line:84%
As for the
AlwaysInstallElevated feature,

00:22:46.730 --> 00:22:49.520 align:middle line:84%
you can see that it's
currently disabled,

00:22:49.520 --> 00:22:51.838 align:middle line:90%
and it's not vulnerable.

00:22:51.838 --> 00:22:53.630 align:middle line:84%
And you can scroll
through all the results.

00:22:53.630 --> 00:22:56.180 align:middle line:84%
So for example
under, UPDATES, it

00:22:56.180 --> 00:22:58.670 align:middle line:84%
will enumerate the install
updates and hotfixes

00:22:58.670 --> 00:23:02.850 align:middle line:84%
and check whether a patch was
applied in the last 31 days.

00:23:02.850 --> 00:23:06.050 align:middle line:84%
So you can see that this is the
hotfix ID that was installed.

00:23:06.050 --> 00:23:07.400 align:middle line:90%
The description is updated.

00:23:07.400 --> 00:23:09.020 align:middle line:84%
It was installed by
the administrator

00:23:09.020 --> 00:23:10.460 align:middle line:90%
on the following date.

00:23:10.460 --> 00:23:12.860 align:middle line:84%
And at the bottom, of course,
you have your summary.

00:23:12.860 --> 00:23:15.890 align:middle line:84%
Now, the great thing with
the PrivescCheck script

00:23:15.890 --> 00:23:19.430 align:middle line:84%
is that it also allows you to
perform an extended check using

00:23:19.430 --> 00:23:21.002 align:middle line:90%
the extended flag here.

00:23:21.002 --> 00:23:22.460 align:middle line:84%
But that's something
that we really

00:23:22.460 --> 00:23:26.030 align:middle line:84%
don't need at this
stage, and we'll probably

00:23:26.030 --> 00:23:30.140 align:middle line:84%
be exploring all of this
during another course.

00:23:30.140 --> 00:23:34.280 align:middle line:84%
All right, so that is how to
identify Windows privilege

00:23:34.280 --> 00:23:37.280 align:middle line:84%
escalation vulnerabilities
through the use of an automated

00:23:37.280 --> 00:23:37.970 align:middle line:90%
script.

00:23:37.970 --> 00:23:40.880 align:middle line:84%
And that is going to conclude
the practical demonstration

00:23:40.880 --> 00:23:44.295 align:middle line:90%
side of this video.

00:23:44.295 --> 00:23:45.670 align:middle line:84%
All right, so now
that we've been

00:23:45.670 --> 00:23:48.790 align:middle line:84%
able to identify a privilege
escalation vulnerability,

00:23:48.790 --> 00:23:52.540 align:middle line:84%
and in this case, we were
able to identify the WinLogon

00:23:52.540 --> 00:23:54.760 align:middle line:84%
credentials for the
administrator user,

00:23:54.760 --> 00:23:56.770 align:middle line:84%
in the next video,
we'll be exploring

00:23:56.770 --> 00:24:00.100 align:middle line:84%
the process of how to
utilize these credentials

00:24:00.100 --> 00:24:02.710 align:middle line:84%
to essentially obtain
an elevated session.

00:24:02.710 --> 00:24:07.300 align:middle line:84%
Because if you obtain Windows
credentials and you know

00:24:07.300 --> 00:24:11.410 align:middle line:84%
RDP is disabled, how can
you use these credentials

00:24:11.410 --> 00:24:13.000 align:middle line:90%
to obtain an elevated session?

00:24:13.000 --> 00:24:15.740 align:middle line:84%
So that's what we're
going to be exploring.

00:24:15.740 --> 00:24:19.110 align:middle line:84%
So I'll be seeing you
in the next video.

00:24:19.110 --> 00:24:20.000 align:middle line:90%