WEBVTT

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


00:00:03.402 --> 00:00:06.804 align:middle line:90%
[MUSIC PLAYING]

00:00:06.804 --> 00:00:09.720 align:middle line:90%


00:00:09.720 --> 00:00:12.872 align:middle line:90%
Bypassing UAC with UACMe.

00:00:12.872 --> 00:00:14.580 align:middle line:84%
All right, so now that
we've taken a look

00:00:14.580 --> 00:00:17.280 align:middle line:84%
at how we can exploit
vulnerabilities in the Windows

00:00:17.280 --> 00:00:19.830 align:middle line:84%
kernel in order to
elevate our privileges,

00:00:19.830 --> 00:00:23.220 align:middle line:84%
let's take a look at how we
can bypass UAC or User Account

00:00:23.220 --> 00:00:26.430 align:middle line:84%
Control with a
tool called UACMe.

00:00:26.430 --> 00:00:28.560 align:middle line:84%
And again, this is going
to be very interesting.

00:00:28.560 --> 00:00:30.730 align:middle line:84%
As I mentioned in
the previous video,

00:00:30.730 --> 00:00:33.330 align:middle line:84%
this is one of the
privilege escalation vectors

00:00:33.330 --> 00:00:36.630 align:middle line:84%
that I really like primarily
because of how efficient it is.

00:00:36.630 --> 00:00:40.710 align:middle line:84%
All right, so getting
started or before we actually

00:00:40.710 --> 00:00:43.200 align:middle line:84%
get started with the
practical side of this video,

00:00:43.200 --> 00:00:45.390 align:middle line:84%
let's get an
understanding of what UAC

00:00:45.390 --> 00:00:47.580 align:middle line:90%
is in the context of Windows.

00:00:47.580 --> 00:00:50.850 align:middle line:84%
UAC stands for User
Account Control.

00:00:50.850 --> 00:00:53.190 align:middle line:84%
It is essentially a
Windows security feature

00:00:53.190 --> 00:00:55.560 align:middle line:84%
that was introduced
in Windows Vista

00:00:55.560 --> 00:00:58.380 align:middle line:84%
and is used to prevent
unauthorized changes from being

00:00:58.380 --> 00:00:59.770 align:middle line:90%
made to the operating system.

00:00:59.770 --> 00:01:01.740 align:middle line:84%
So it was implemented
in Windows Vista

00:01:01.740 --> 00:01:05.820 align:middle line:84%
and is present in every version
of Windows since Windows Vista.

00:01:05.820 --> 00:01:10.740 align:middle line:84%
So from Windows Vista to Windows
7, to eight 8, 8.1, Windows 10,

00:01:10.740 --> 00:01:13.080 align:middle line:90%
and of course also Windows 11.

00:01:13.080 --> 00:01:15.570 align:middle line:84%
So again, it's a
feature that you

00:01:15.570 --> 00:01:18.150 align:middle line:84%
will find on modern
versions of Windows

00:01:18.150 --> 00:01:20.190 align:middle line:90%
or modern releases of Windows.

00:01:20.190 --> 00:01:23.640 align:middle line:84%
UAC is used to ensure that
changes to the operating system

00:01:23.640 --> 00:01:27.300 align:middle line:84%
require approval from the
administrator or a user

00:01:27.300 --> 00:01:30.210 align:middle line:84%
account that is part of the
local administrator's group.

00:01:30.210 --> 00:01:33.180 align:middle line:84%
A non privileged user
attempting to execute a program

00:01:33.180 --> 00:01:36.600 align:middle line:84%
with elevated privileges
will be prompted with the UAC

00:01:36.600 --> 00:01:39.750 align:middle line:84%
credential prompt, whereas
a privileged user will be

00:01:39.750 --> 00:01:42.330 align:middle line:90%
prompted with a consent prompt.

00:01:42.330 --> 00:01:44.010 align:middle line:84%
So if you've ever
used Windows, which

00:01:44.010 --> 00:01:45.900 align:middle line:84%
I'm guessing that
you have, and more

00:01:45.900 --> 00:01:48.060 align:middle line:84%
specifically a modern
version of Windows,

00:01:48.060 --> 00:01:51.630 align:middle line:84%
so anything newer than
Windows 7 or anything newer

00:01:51.630 --> 00:01:52.770 align:middle line:90%
than Windows Vista.

00:01:52.770 --> 00:01:56.650 align:middle line:84%
And if you have ever tried
to install a new program,

00:01:56.650 --> 00:01:59.730 align:middle line:84%
you will be prompted
with a screen or a dialog

00:01:59.730 --> 00:02:00.960 align:middle line:90%
box very similar to this.

00:02:00.960 --> 00:02:02.790 align:middle line:84%
You can see user
account control.

00:02:02.790 --> 00:02:06.720 align:middle line:84%
And what Windows is doing is
it's essentially asking you

00:02:06.720 --> 00:02:10.169 align:middle line:84%
whether you essentially
are sure of your decision

00:02:10.169 --> 00:02:14.190 align:middle line:84%
or whether or not you want to
execute this specific program

00:02:14.190 --> 00:02:16.380 align:middle line:90%
with elevated privileges.

00:02:16.380 --> 00:02:17.940 align:middle line:84%
And this is very,
very important.

00:02:17.940 --> 00:02:19.890 align:middle line:84%
As I said, it's a
security feature.

00:02:19.890 --> 00:02:21.990 align:middle line:84%
And the reason this
was implemented

00:02:21.990 --> 00:02:24.900 align:middle line:84%
is because before, that
you could essentially

00:02:24.900 --> 00:02:27.540 align:middle line:84%
execute a program with
elevated privileges

00:02:27.540 --> 00:02:30.420 align:middle line:84%
without having the user
account to actually confirm

00:02:30.420 --> 00:02:31.650 align:middle line:90%
that they want to do that.

00:02:31.650 --> 00:02:34.650 align:middle line:84%
So this informs them
of the potential risk.

00:02:34.650 --> 00:02:38.220 align:middle line:84%
And of course, it's a vital
part of modern Windows

00:02:38.220 --> 00:02:41.310 align:middle line:84%
or operating system
security right now.

00:02:41.310 --> 00:02:43.980 align:middle line:84%
Depending on the type
of privilege or access

00:02:43.980 --> 00:02:46.710 align:middle line:84%
you have to a target system
or the type of access

00:02:46.710 --> 00:02:51.510 align:middle line:84%
you have to a Windows system,
the actual user account control

00:02:51.510 --> 00:02:53.440 align:middle line:90%
prompt will actually change.

00:02:53.440 --> 00:02:58.170 align:middle line:84%
So, as I said, for example, if
I'm running a Windows system

00:02:58.170 --> 00:03:00.570 align:middle line:84%
or I currently have
access to a Windows system

00:03:00.570 --> 00:03:04.230 align:middle line:84%
with a user account that is part
of the local administrator's

00:03:04.230 --> 00:03:07.350 align:middle line:84%
group, and I execute a
program like the command

00:03:07.350 --> 00:03:09.180 align:middle line:84%
prompt with
administrative privileges

00:03:09.180 --> 00:03:13.140 align:middle line:84%
or if I right-click on CMD and
I say run as administrator,

00:03:13.140 --> 00:03:16.020 align:middle line:84%
I'll be prompted
with a consent form.

00:03:16.020 --> 00:03:21.360 align:middle line:84%
So a consent form is essentially
asking you, confirming,

00:03:21.360 --> 00:03:26.070 align:middle line:84%
or telling you that I'm going to
execute this particular program

00:03:26.070 --> 00:03:30.120 align:middle line:84%
with administrative privileges,
and I need your confirmation.

00:03:30.120 --> 00:03:34.770 align:middle line:84%
Now, if I was running or if I
had access to a Windows system

00:03:34.770 --> 00:03:37.770 align:middle line:84%
with a non-privileged account,
a standard account that's

00:03:37.770 --> 00:03:39.870 align:middle line:84%
not part of the local
administrator's group,

00:03:39.870 --> 00:03:43.450 align:middle line:84%
and I tried to execute
CMD as administrator,

00:03:43.450 --> 00:03:46.440 align:middle line:84%
I would be prompted with
a credential prompt.

00:03:46.440 --> 00:03:49.200 align:middle line:84%
So a credential prompt is
very similar to this box here

00:03:49.200 --> 00:03:50.890 align:middle line:90%
or this dialog box here.

00:03:50.890 --> 00:03:52.500 align:middle line:84%
However, the only
difference is that I

00:03:52.500 --> 00:03:55.500 align:middle line:84%
will be prompted to enter
the administrator's password.

00:03:55.500 --> 00:03:58.230 align:middle line:84%
And you should have
actually seen this

00:03:58.230 --> 00:04:01.260 align:middle line:84%
in computers or
Windows systems that

00:04:01.260 --> 00:04:05.430 align:middle line:84%
are used in an organization
or in a school environment,

00:04:05.430 --> 00:04:09.000 align:middle line:84%
whereby administrators or
system administrators don't want

00:04:09.000 --> 00:04:11.730 align:middle line:84%
students or
individuals to execute

00:04:11.730 --> 00:04:15.360 align:middle line:84%
any program, for that matter,
with elevated privileges,

00:04:15.360 --> 00:04:17.940 align:middle line:84%
and as a result, you would need
to enter the administrator's

00:04:17.940 --> 00:04:21.149 align:middle line:84%
password to execute
that particular program

00:04:21.149 --> 00:04:23.010 align:middle line:90%
with elevated privileges.

00:04:23.010 --> 00:04:27.300 align:middle line:84%
Now attackers can bypass
user account control features

00:04:27.300 --> 00:04:31.860 align:middle line:84%
or safeguards in order to
execute malicious executables

00:04:31.860 --> 00:04:33.540 align:middle line:90%
with elevated privileges.

00:04:33.540 --> 00:04:36.330 align:middle line:84%
And the typical
use case here would

00:04:36.330 --> 00:04:40.470 align:middle line:84%
be that I can bypass UAC
to essentially execute

00:04:40.470 --> 00:04:43.660 align:middle line:84%
an administrative
command, like for example,

00:04:43.660 --> 00:04:46.680 align:middle line:84%
if I wanted to change a
user's account password,

00:04:46.680 --> 00:04:51.210 align:middle line:84%
I can bypass UAC to change
that particular user

00:04:51.210 --> 00:04:54.630 align:middle line:84%
accounts password and not
have this dialog box show up

00:04:54.630 --> 00:04:57.570 align:middle line:84%
because if I have access
to a Windows system

00:04:57.570 --> 00:05:01.110 align:middle line:84%
through a Meterpreter session
or a command shell session

00:05:01.110 --> 00:05:03.120 align:middle line:84%
and I try and
execute any program

00:05:03.120 --> 00:05:07.820 align:middle line:84%
with elevated privileges,
this dialog box will actually

00:05:07.820 --> 00:05:08.570 align:middle line:90%
be brought up.

00:05:08.570 --> 00:05:12.170 align:middle line:84%
However, I don't have any
means of actually accepting

00:05:12.170 --> 00:05:15.290 align:middle line:84%
or verifying that
I want to make that

00:05:15.290 --> 00:05:17.660 align:middle line:84%
or I want to execute
that particular program

00:05:17.660 --> 00:05:20.120 align:middle line:84%
with administrative
privileges, and as a result,

00:05:20.120 --> 00:05:23.930 align:middle line:84%
I have to find a way of
bypassing UAC altogether

00:05:23.930 --> 00:05:26.660 align:middle line:84%
so that I don't need to go
through that entire process

00:05:26.660 --> 00:05:31.130 align:middle line:84%
of essentially
providing my consent.

00:05:31.130 --> 00:05:35.660 align:middle line:84%
Now in terms of bypassing UAC,
in order to successfully bypass

00:05:35.660 --> 00:05:38.540 align:middle line:84%
UAC, we will need to have
access to a user account that

00:05:38.540 --> 00:05:40.850 align:middle line:84%
is part of the local
administrator's group

00:05:40.850 --> 00:05:42.480 align:middle line:90%
on the Windows target system.

00:05:42.480 --> 00:05:44.160 align:middle line:84%
The reason for that
is fairly simple.

00:05:44.160 --> 00:05:47.660 align:middle line:84%
Remember, if we are part of
the local administrator's

00:05:47.660 --> 00:05:50.120 align:middle line:84%
group, that means that
we have the ability

00:05:50.120 --> 00:05:53.120 align:middle line:84%
to execute programs
or certain commands

00:05:53.120 --> 00:05:54.890 align:middle line:90%
with administrative privileges.

00:05:54.890 --> 00:05:58.640 align:middle line:84%
The only problem is that we need
to bypass that consent dialog

00:05:58.640 --> 00:05:59.420 align:middle line:90%
box.

00:05:59.420 --> 00:06:04.160 align:middle line:84%
So again, we really can't bypass
UAC if we don't have an account

00:06:04.160 --> 00:06:06.410 align:middle line:84%
or we don't have access
to an account that

00:06:06.410 --> 00:06:08.600 align:middle line:84%
is part of the local
administrator's group.

00:06:08.600 --> 00:06:10.910 align:middle line:84%
Now the local administrator's
group on Windows

00:06:10.910 --> 00:06:12.410 align:middle line:84%
is essentially a
group that's used

00:06:12.410 --> 00:06:16.963 align:middle line:84%
to assign administrative
privileges to user accounts.

00:06:16.963 --> 00:06:18.380 align:middle line:84%
And of course, the
only difference

00:06:18.380 --> 00:06:21.920 align:middle line:84%
being that they'll be able to
use it if they want to use it

00:06:21.920 --> 00:06:24.290 align:middle line:84%
or when they're performing
tasks that require

00:06:24.290 --> 00:06:26.420 align:middle line:84%
administrative
privileges, tasks like

00:06:26.420 --> 00:06:29.390 align:middle line:84%
installing new software,
et cetera, et cetera.

00:06:29.390 --> 00:06:32.210 align:middle line:84%
So UAC allows the
program to be executed

00:06:32.210 --> 00:06:35.690 align:middle line:84%
with administrative privileges,
consequently prompting

00:06:35.690 --> 00:06:37.290 align:middle line:90%
the user for confirmation.

00:06:37.290 --> 00:06:39.710 align:middle line:84%
So that's what we're going
to be bypassing here.

00:06:39.710 --> 00:06:42.950 align:middle line:84%
Now UAC has various
integrity levels,

00:06:42.950 --> 00:06:45.140 align:middle line:84%
and I'll showcase
this in a few seconds,

00:06:45.140 --> 00:06:47.060 align:middle line:90%
ranging from low to high.

00:06:47.060 --> 00:06:50.240 align:middle line:84%
If the UAC protection
level is set below high,

00:06:50.240 --> 00:06:53.810 align:middle line:84%
Windows programs can be executed
with elevated privileges

00:06:53.810 --> 00:06:56.400 align:middle line:84%
without prompting the
user for confirmation.

00:06:56.400 --> 00:06:58.790 align:middle line:84%
So again, a typical
use case for this

00:06:58.790 --> 00:07:02.630 align:middle line:84%
would be that if we created a
Meterpreter payload with MSF

00:07:02.630 --> 00:07:04.890 align:middle line:84%
venom and then uploaded
it to the target,

00:07:04.890 --> 00:07:08.720 align:middle line:84%
and if we wanted to execute it
with administrative privileges,

00:07:08.720 --> 00:07:12.710 align:middle line:84%
we can essentially bypass UAC
and get that payload executed

00:07:12.710 --> 00:07:15.380 align:middle line:84%
with administrative privileges
without having to go

00:07:15.380 --> 00:07:17.630 align:middle line:90%
through the consent process.

00:07:17.630 --> 00:07:20.030 align:middle line:84%
And of course, once that
payload is executed,

00:07:20.030 --> 00:07:23.030 align:middle line:84%
because it's being executed
with administrative privileges,

00:07:23.030 --> 00:07:26.040 align:middle line:84%
we will obtain an elevated
Meterpreter session,

00:07:26.040 --> 00:07:27.590 align:middle line:84%
which means we've
successfully been

00:07:27.590 --> 00:07:30.080 align:middle line:90%
able to elevate our privileges.

00:07:30.080 --> 00:07:33.260 align:middle line:84%
Now in terms of the tools and
techniques that we can use,

00:07:33.260 --> 00:07:35.570 align:middle line:84%
there really are plenty
of tools and techniques

00:07:35.570 --> 00:07:37.520 align:middle line:90%
that can be used to bypass UAC.

00:07:37.520 --> 00:07:39.500 align:middle line:84%
However, the key
thing to note here

00:07:39.500 --> 00:07:41.510 align:middle line:84%
is that the tool
and technique used

00:07:41.510 --> 00:07:44.510 align:middle line:84%
will depend on the version of
Windows running on the target

00:07:44.510 --> 00:07:48.050 align:middle line:84%
system and, of course,
the actual integrity

00:07:48.050 --> 00:07:51.650 align:middle line:84%
level or the actual UAC level
that has been configured

00:07:51.650 --> 00:07:53.810 align:middle line:90%
on that target system.

00:07:53.810 --> 00:07:56.960 align:middle line:84%
And of course, I'll highlight
this in a few seconds

00:07:56.960 --> 00:07:59.120 align:middle line:84%
when I'll be switching
over to a Windows system

00:07:59.120 --> 00:08:02.120 align:middle line:84%
and showing you how
all of this works.

00:08:02.120 --> 00:08:06.590 align:middle line:84%
So the tool that we're going to
be utilizing is called UACMe.

00:08:06.590 --> 00:08:09.740 align:middle line:84%
Now UACMe really
can't be considered

00:08:09.740 --> 00:08:13.340 align:middle line:84%
as a tool or a standalone
tool because really

00:08:13.340 --> 00:08:16.910 align:middle line:84%
what it is an open-source
robust privilege escalation

00:08:16.910 --> 00:08:20.720 align:middle line:84%
tool and guide
developed by hfiref0x.

00:08:20.720 --> 00:08:23.000 align:middle line:84%
And it essentially
can be used to bypass

00:08:23.000 --> 00:08:25.680 align:middle line:84%
Windows UAC by leveraging
various techniques.

00:08:25.680 --> 00:08:30.470 align:middle line:84%
So the UACMe GitHub
repository contains

00:08:30.470 --> 00:08:32.720 align:middle line:84%
a very, very
well-documented list

00:08:32.720 --> 00:08:35.030 align:middle line:84%
of methods that can
be used to bypass

00:08:35.030 --> 00:08:38.510 align:middle line:84%
UAC on multiple versions of
Windows ranging from Windows 7

00:08:38.510 --> 00:08:39.770 align:middle line:90%
to Windows 10.

00:08:39.770 --> 00:08:42.080 align:middle line:84%
And the way it does
this is it does this

00:08:42.080 --> 00:08:44.330 align:middle line:84%
by providing you with
an executable that

00:08:44.330 --> 00:08:47.330 align:middle line:84%
can be transferred
onto the target system,

00:08:47.330 --> 00:08:49.670 align:middle line:84%
and that executable
essentially can

00:08:49.670 --> 00:08:53.570 align:middle line:84%
be used to execute a payload
or any executable that you

00:08:53.570 --> 00:08:56.120 align:middle line:84%
want to execute with
administrative privileges.

00:08:56.120 --> 00:08:58.880 align:middle line:84%
And the actual
executable that I'm

00:08:58.880 --> 00:09:03.740 align:middle line:84%
referring to here that is
part of UACMe is called Akagi.

00:09:03.740 --> 00:09:06.540 align:middle line:84%
And I'll get to that
in a few seconds.

00:09:06.540 --> 00:09:09.080 align:middle line:84%
But the way this work
is it essentially

00:09:09.080 --> 00:09:11.420 align:middle line:84%
allows attackers to
execute malicious payloads

00:09:11.420 --> 00:09:14.480 align:middle line:84%
on their Windows target with
administrative or elevated

00:09:14.480 --> 00:09:18.050 align:middle line:84%
privileges by abusing the
in-built Windows auto elevate

00:09:18.050 --> 00:09:19.130 align:middle line:90%
tool.

00:09:19.130 --> 00:09:23.150 align:middle line:84%
So the UAC me GitHub repository
has more than 60 exploits

00:09:23.150 --> 00:09:25.280 align:middle line:84%
that can be used to
bypass UAC depending

00:09:25.280 --> 00:09:27.680 align:middle line:84%
on the version of Windows
running on the target.

00:09:27.680 --> 00:09:30.530 align:middle line:84%
And of course, I'll be
explaining how to use this tool

00:09:30.530 --> 00:09:32.772 align:middle line:84%
and will be exploring
the GitHub repository

00:09:32.772 --> 00:09:34.730 align:middle line:84%
so that you have an
understanding of what we're

00:09:34.730 --> 00:09:36.740 align:middle line:84%
going to be doing
before we actually

00:09:36.740 --> 00:09:39.860 align:middle line:84%
get to the actual
exploitation section.

00:09:39.860 --> 00:09:43.040 align:middle line:84%
So I'm just going to switch
over to a Windows system

00:09:43.040 --> 00:09:45.950 align:middle line:84%
before we begin with the
exploitation section.

00:09:45.950 --> 00:09:48.950 align:middle line:84%
This video has a lab environment
that we will be using,

00:09:48.950 --> 00:09:53.180 align:middle line:84%
and it will allow
me to showcase how

00:09:53.180 --> 00:09:57.770 align:middle line:84%
we can utilize UACMe me to
bypass user count controls.

00:09:57.770 --> 00:09:59.720 align:middle line:84%
So I'm just going to
quickly switch over

00:09:59.720 --> 00:10:03.100 align:middle line:84%
to my Windows system,
and I'll demonstrate

00:10:03.100 --> 00:10:07.480 align:middle line:84%
what UAC is, how it looks
when we essentially interact

00:10:07.480 --> 00:10:10.000 align:middle line:84%
with UAC, or we try
and execute a program

00:10:10.000 --> 00:10:12.490 align:middle line:84%
with elevated
privileges, and I'll also

00:10:12.490 --> 00:10:16.370 align:middle line:84%
showcase the various UAC
levels or security levels.

00:10:16.370 --> 00:10:18.370 align:middle line:84%
So let me just switch
over to the Windows system

00:10:18.370 --> 00:10:20.250 align:middle line:90%
really quickly.

00:10:20.250 --> 00:10:23.450 align:middle line:84%
All right, so this is
the actual Windows VM

00:10:23.450 --> 00:10:25.910 align:middle line:84%
that I'm going to be
using to just showcase

00:10:25.910 --> 00:10:28.520 align:middle line:84%
how UAC works on
a Windows system.

00:10:28.520 --> 00:10:31.880 align:middle line:84%
So I currently have access to
this system with a user account

00:10:31.880 --> 00:10:34.370 align:middle line:84%
that is part of the
local administrator's

00:10:34.370 --> 00:10:35.390 align:middle line:90%
group on Windows.

00:10:35.390 --> 00:10:38.070 align:middle line:84%
So again, if I open up
my command prompt here.

00:10:38.070 --> 00:10:40.980 align:middle line:84%
And I'm just going to zoom
in or increase my font size

00:10:40.980 --> 00:10:43.010 align:middle line:90%
so you can see what's going on.

00:10:43.010 --> 00:10:46.008 align:middle line:84%
I can type, for
example, net users.

00:10:46.008 --> 00:10:46.550 align:middle line:90%
There we are.

00:10:46.550 --> 00:10:49.550 align:middle line:84%
So you can see this
particular virtual machine

00:10:49.550 --> 00:10:51.320 align:middle line:90%
has various user accounts.

00:10:51.320 --> 00:10:53.420 align:middle line:84%
We have the standard
administrator account,

00:10:53.420 --> 00:10:55.940 align:middle line:84%
and then, of course,
we have IEUser,

00:10:55.940 --> 00:10:58.260 align:middle line:90%
which is this current user.

00:10:58.260 --> 00:11:03.050 align:middle line:84%
And again, if we take a
look at the actual members

00:11:03.050 --> 00:11:07.400 align:middle line:84%
of the Administrators group,
we can say net local group

00:11:07.400 --> 00:11:09.380 align:middle line:90%
administrators.

00:11:09.380 --> 00:11:11.810 align:middle line:84%
You will see that the
members of this group

00:11:11.810 --> 00:11:14.360 align:middle line:90%
are administrator and IEUser.

00:11:14.360 --> 00:11:16.880 align:middle line:84%
So that means that this
particular user account

00:11:16.880 --> 00:11:19.910 align:middle line:84%
can execute programs
or executables

00:11:19.910 --> 00:11:21.440 align:middle line:90%
with administrative privileges.

00:11:21.440 --> 00:11:25.610 align:middle line:84%
However, I will be prompted
with the UAC consent prompt.

00:11:25.610 --> 00:11:29.150 align:middle line:84%
So, for example, if I wanted
to execute the command prompt

00:11:29.150 --> 00:11:33.290 align:middle line:84%
as administrator, I could
right-click on Command prompt

00:11:33.290 --> 00:11:35.150 align:middle line:84%
and then say run
as administrator,

00:11:35.150 --> 00:11:38.630 align:middle line:84%
and you'll see I'll get
the user account control

00:11:38.630 --> 00:11:40.083 align:middle line:90%
consent prompt right over here.

00:11:40.083 --> 00:11:42.000 align:middle line:84%
So, of course, this is
just going to tell you,

00:11:42.000 --> 00:11:44.780 align:middle line:84%
do you want to allow this app
to make changes to your device?

00:11:44.780 --> 00:11:47.060 align:middle line:84%
And this is what we're
looking to bypass.

00:11:47.060 --> 00:11:48.890 align:middle line:90%
So I can either hit Yes or No.

00:11:48.890 --> 00:11:51.062 align:middle line:84%
And if I say Show
More Details, you

00:11:51.062 --> 00:11:52.520 align:middle line:84%
can see that it's
going to give you

00:11:52.520 --> 00:11:55.280 align:middle line:84%
information regarding that
particular executable et

00:11:55.280 --> 00:11:56.270 align:middle line:90%
cetera, et cetera.

00:11:56.270 --> 00:11:59.480 align:middle line:84%
I can then it Yes, and I
now have an elevated command

00:11:59.480 --> 00:12:01.880 align:middle line:84%
prompt, and that, of course,
is denoted by the fact

00:12:01.880 --> 00:12:04.280 align:middle line:84%
that I've been
automatically directed

00:12:04.280 --> 00:12:06.470 align:middle line:84%
or the default directory
I'm working from

00:12:06.470 --> 00:12:09.500 align:middle line:90%
is the system32 directory.

00:12:09.500 --> 00:12:12.630 align:middle line:84%
And, of course, that goes
just for any other program.

00:12:12.630 --> 00:12:14.960 align:middle line:84%
So, for example, I have
a test payload here.

00:12:14.960 --> 00:12:17.570 align:middle line:84%
I can right-click on it and
say run as administrator,

00:12:17.570 --> 00:12:18.650 align:middle line:90%
and there you go.

00:12:18.650 --> 00:12:21.680 align:middle line:84%
Now, if I currently had
access to this account

00:12:21.680 --> 00:12:27.590 align:middle line:84%
with a standard non-privileged
user account that was not

00:12:27.590 --> 00:12:30.380 align:middle line:84%
a part of the local
administrator's group,

00:12:30.380 --> 00:12:33.587 align:middle line:84%
I would essentially be prompted
with a credential prompt,

00:12:33.587 --> 00:12:35.420 align:middle line:84%
which is very similar
to the consent prompt.

00:12:35.420 --> 00:12:38.660 align:middle line:84%
The only difference is there's
a small dialog box asking

00:12:38.660 --> 00:12:40.130 align:middle line:84%
you to provide the
administrator's

00:12:40.130 --> 00:12:44.540 align:middle line:84%
password in order to execute
said program or payload

00:12:44.540 --> 00:12:49.010 align:middle line:84%
with executable or rather
with elevated privileges.

00:12:49.010 --> 00:12:51.380 align:middle line:84%
Now in terms of the
UAC security levels,

00:12:51.380 --> 00:12:54.800 align:middle line:84%
if I just open up the
Start menu and I say UAC,

00:12:54.800 --> 00:12:57.740 align:middle line:84%
I have the ability to change the
user account control settings.

00:12:57.740 --> 00:13:00.650 align:middle line:84%
And this allows me to change
the UAC security level.

00:13:00.650 --> 00:13:02.690 align:middle line:84%
So the default
configuration is never

00:13:02.690 --> 00:13:05.570 align:middle line:84%
set to high on a vanilla
installation of Windows.

00:13:05.570 --> 00:13:07.850 align:middle line:84%
And as you can see,
at this particular

00:13:07.850 --> 00:13:10.310 align:middle line:84%
or at this current
level, it will only

00:13:10.310 --> 00:13:13.400 align:middle line:84%
notify me when apps try to
make changes to my computer.

00:13:13.400 --> 00:13:15.300 align:middle line:84%
That's the default
configuration.

00:13:15.300 --> 00:13:17.660 align:middle line:84%
And it will not notify
me when I make changes

00:13:17.660 --> 00:13:18.900 align:middle line:90%
to Windows settings.

00:13:18.900 --> 00:13:21.080 align:middle line:84%
So if I set this to the
highest, you can now

00:13:21.080 --> 00:13:24.200 align:middle line:84%
see that it will notify
me or always notify me

00:13:24.200 --> 00:13:26.510 align:middle line:84%
when apps try to install
software or make changes

00:13:26.510 --> 00:13:30.170 align:middle line:84%
to my computer, and it will also
notify me when I make changes

00:13:30.170 --> 00:13:31.110 align:middle line:90%
to Windows settings.

00:13:31.110 --> 00:13:34.910 align:middle line:84%
So when it is currently
set to the highest level,

00:13:34.910 --> 00:13:37.490 align:middle line:84%
this can be very
difficult to bypass,

00:13:37.490 --> 00:13:40.100 align:middle line:84%
and that's something that you
always want to be aware of.

00:13:40.100 --> 00:13:43.280 align:middle line:84%
And of course, as I
said, if not configured

00:13:43.280 --> 00:13:44.960 align:middle line:84%
after installing
Windows, then it's

00:13:44.960 --> 00:13:47.390 align:middle line:84%
going to utilize the
default security level.

00:13:47.390 --> 00:13:49.550 align:middle line:90%
So that's really how UAC works.

00:13:49.550 --> 00:13:53.450 align:middle line:84%
You can see it's fairly
simple in regards to what's

00:13:53.450 --> 00:13:54.870 align:middle line:90%
happening in the background.

00:13:54.870 --> 00:13:56.720 align:middle line:84%
And if you have used
a Windows system,

00:13:56.720 --> 00:13:59.420 align:middle line:84%
then you should be
familiar with all of this.

00:13:59.420 --> 00:14:01.550 align:middle line:84%
So now that we've
taken a look at how

00:14:01.550 --> 00:14:05.600 align:middle line:84%
UAC works on a real
Windows system where

00:14:05.600 --> 00:14:08.160 align:middle line:84%
we have physical
access to the target

00:14:08.160 --> 00:14:12.840 align:middle line:84%
let's take a look at how we can
bypass UAC through our access,

00:14:12.840 --> 00:14:16.327 align:middle line:84%
whether it be a standard command
shell or a Meterpreter session.

00:14:16.327 --> 00:14:18.660 align:middle line:84%
So I'm just going to switch
over to the lab environment.

00:14:18.660 --> 00:14:22.620 align:middle line:84%
And of course, you can follow
along with the demonstration.

00:14:22.620 --> 00:14:25.020 align:middle line:84%
All right, so I'm currently
within the lab environment,

00:14:25.020 --> 00:14:27.517 align:middle line:84%
and you'll be provided
with the target IP.

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

00:14:29.850 --> 00:14:32.930 align:middle line:84%
So the first step will involve
identifying a vulnerability

00:14:32.930 --> 00:14:35.570 align:middle line:84%
running on the target
or a vulnerable service

00:14:35.570 --> 00:14:37.310 align:middle line:84%
running on the
target that we can

00:14:37.310 --> 00:14:39.120 align:middle line:90%
exploit to gain initial access.

00:14:39.120 --> 00:14:40.910 align:middle line:84%
So, in this case,
the exploitation

00:14:40.910 --> 00:14:42.600 align:middle line:90%
is going to be fairly trivial.

00:14:42.600 --> 00:14:45.290 align:middle line:84%
I'm just going to copy the
IP address there and open up

00:14:45.290 --> 00:14:48.770 align:middle line:84%
a terminal, after which I'm just
going to zoom in a little bit

00:14:48.770 --> 00:14:51.140 align:middle line:84%
here, and we can perform
an Nmap scan on the target.

00:14:51.140 --> 00:14:54.650 align:middle line:84%
So I'm just going to say Nmap
and paste in the target IP.

00:14:54.650 --> 00:14:57.350 align:middle line:84%
Of course, you're free to
customize the parameters

00:14:57.350 --> 00:14:58.920 align:middle line:90%
or the scan options.

00:14:58.920 --> 00:15:00.500 align:middle line:84%
In this case, I'll
just hit Enter.

00:15:00.500 --> 00:15:03.350 align:middle line:84%
And we should have a
vulnerable HTTP file

00:15:03.350 --> 00:15:04.910 align:middle line:90%
server running on port 80.

00:15:04.910 --> 00:15:07.490 align:middle line:84%
So if we open up
our browser and we

00:15:07.490 --> 00:15:10.820 align:middle line:84%
try and access the actual
web server on port 80 that's

00:15:10.820 --> 00:15:14.900 align:middle line:84%
running on the target, you'll
see that it's running the HFS

00:15:14.900 --> 00:15:18.860 align:middle line:84%
or rather the HTTP File
Server developed by rejetto.

00:15:18.860 --> 00:15:21.680 align:middle line:84%
And this is version
2.3, which is actually

00:15:21.680 --> 00:15:25.580 align:middle line:84%
vulnerable to a particular
exploit or vulnerability,

00:15:25.580 --> 00:15:27.920 align:middle line:84%
and we can easily exploit
this vulnerability

00:15:27.920 --> 00:15:29.240 align:middle line:90%
with the Metasploit framework.

00:15:29.240 --> 00:15:31.850 align:middle line:84%
So I'm just going to start
up the Metasploit framework.

00:15:31.850 --> 00:15:35.570 align:middle line:84%
I'll also start up the
PostgreSQL Database Service.

00:15:35.570 --> 00:15:38.915 align:middle line:84%
So service postgresql
start and msfconsole.

00:15:38.915 --> 00:15:42.190 align:middle line:90%


00:15:42.190 --> 00:15:42.850 align:middle line:90%
There we go.

00:15:42.850 --> 00:15:46.250 align:middle line:84%
We'll give this a
couple of seconds.

00:15:46.250 --> 00:15:48.770 align:middle line:84%
And I'm just going to copy
the target IP because I'm

00:15:48.770 --> 00:15:53.630 align:middle line:84%
going to set the target IP as a
global variable for the RHOSTS

00:15:53.630 --> 00:15:54.360 align:middle line:90%
option.

00:15:54.360 --> 00:15:57.860 align:middle line:84%
So I'm going to say setg
RHOSTS and target IP

00:15:57.860 --> 00:16:00.950 align:middle line:84%
so that I don't have to keep
on typing the target IP address

00:16:00.950 --> 00:16:03.500 align:middle line:84%
whenever I load a new
Metasploit module.

00:16:03.500 --> 00:16:04.620 align:middle line:90%
All right, so that's done.

00:16:04.620 --> 00:16:09.140 align:middle line:84%
I can now search for the
particular exploit module.

00:16:09.140 --> 00:16:12.050 align:middle line:84%
In this case, the target is
running a vulnerable version

00:16:12.050 --> 00:16:14.990 align:middle line:90%
of the rejetto HTTP file server.

00:16:14.990 --> 00:16:17.660 align:middle line:84%
You can see this is the
exploit module that essentially

00:16:17.660 --> 00:16:20.210 align:middle line:84%
exploits a vulnerability
that allows an attacker

00:16:20.210 --> 00:16:23.000 align:middle line:84%
to essentially perform
remote command execution.

00:16:23.000 --> 00:16:24.710 align:middle line:84%
And in this case,
this will provide us

00:16:24.710 --> 00:16:25.940 align:middle line:90%
with an Meterpreter session.

00:16:25.940 --> 00:16:28.490 align:middle line:84%
So I'll say, use,
paste that in there.

00:16:28.490 --> 00:16:30.200 align:middle line:84%
The default payload
configured will

00:16:30.200 --> 00:16:33.180 align:middle line:84%
be the standard 32-bit
Windows Meterpreter payload,

00:16:33.180 --> 00:16:34.640 align:middle line:90%
which is perfectly fine.

00:16:34.640 --> 00:16:37.970 align:middle line:84%
If I show the
options here, you can

00:16:37.970 --> 00:16:41.090 align:middle line:84%
see I can configure my payload
options right over here.

00:16:41.090 --> 00:16:43.610 align:middle line:84%
And, of course, I'm going to
leave these as the default.

00:16:43.610 --> 00:16:48.200 align:middle line:84%
In your case, you are free
to change the LPORT depending

00:16:48.200 --> 00:16:50.030 align:middle line:90%
on your current situation.

00:16:50.030 --> 00:16:52.160 align:middle line:84%
But if you follow if
you're following along

00:16:52.160 --> 00:16:55.280 align:middle line:84%
with this lab environment,
then just leave the defaults.

00:16:55.280 --> 00:16:57.080 align:middle line:84%
Given the fact that
I've already set up

00:16:57.080 --> 00:16:59.960 align:middle line:84%
the global variable value
for the RHOST option,

00:16:59.960 --> 00:17:02.570 align:middle line:84%
you can see that is
already set up for me,

00:17:02.570 --> 00:17:05.160 align:middle line:84%
and that's been configured
to the target IP address,

00:17:05.160 --> 00:17:06.740 align:middle line:90%
so I don't have to type that in.

00:17:06.740 --> 00:17:09.380 align:middle line:84%
And I really don't need to
configure anything else.

00:17:09.380 --> 00:17:11.750 align:middle line:84%
If the HTTP file
server was running

00:17:11.750 --> 00:17:14.420 align:middle line:84%
on a subdirectory
on the web server,

00:17:14.420 --> 00:17:15.869 align:middle line:90%
I could specify that here.

00:17:15.869 --> 00:17:18.650 align:middle line:84%
But in this case, it's running
at the root of the web server,

00:17:18.650 --> 00:17:21.520 align:middle line:90%
so I'll just hit exploit.

00:17:21.520 --> 00:17:23.819 align:middle line:84%
We will give this a
couple of seconds.

00:17:23.819 --> 00:17:26.598 align:middle line:84%
And we should obtain
a Meterpreter session.

00:17:26.598 --> 00:17:27.140 align:middle line:90%
There we are.

00:17:27.140 --> 00:17:29.540 align:middle line:84%
It's going to send the stage,
and we get a Meterpreter

00:17:29.540 --> 00:17:31.320 align:middle line:90%
session rather easily.

00:17:31.320 --> 00:17:33.560 align:middle line:84%
So we've successfully
been able to gain access

00:17:33.560 --> 00:17:34.710 align:middle line:90%
to the target system.

00:17:34.710 --> 00:17:37.760 align:middle line:84%
So let's perform some
basic local enumeration

00:17:37.760 --> 00:17:40.770 align:middle line:84%
to identify what version
of Windows is running,

00:17:40.770 --> 00:17:43.250 align:middle line:84%
what current user
we have access to,

00:17:43.250 --> 00:17:45.920 align:middle line:84%
what privileges this
user has, et cetera.

00:17:45.920 --> 00:17:47.930 align:middle line:90%
So I can say sysinfo.

00:17:47.930 --> 00:17:51.020 align:middle line:84%
This tells me that I'm running
on a Windows Server 2012

00:17:51.020 --> 00:17:54.710 align:middle line:84%
system, and that is, of
course, R2 build 9600.

00:17:54.710 --> 00:17:57.090 align:middle line:84%
That information is
very, very important.

00:17:57.090 --> 00:18:00.140 align:middle line:84%
And the current maturity
session is a 32-bit session,

00:18:00.140 --> 00:18:02.750 align:middle line:84%
so I can migrate to
the Explorer process.

00:18:02.750 --> 00:18:04.910 align:middle line:84%
So I can search for
the Explorer process

00:18:04.910 --> 00:18:09.870 align:middle line:84%
by saying pgrep and search
for the actual process

00:18:09.870 --> 00:18:12.330 align:middle line:90%
ID for explorer.exe.

00:18:12.330 --> 00:18:13.980 align:middle line:90%
So there we are.

00:18:13.980 --> 00:18:17.130 align:middle line:84%
And I can just say
migrate to 2448,

00:18:17.130 --> 00:18:21.270 align:middle line:84%
and that'll provide me with
a 64-bit Meterpreter session.

00:18:21.270 --> 00:18:23.130 align:middle line:84%
There we are, so
if I say sysinfo,

00:18:23.130 --> 00:18:25.680 align:middle line:84%
you can see that's
highlighted there.

00:18:25.680 --> 00:18:28.170 align:middle line:84%
So if I say get
user ID, you can see

00:18:28.170 --> 00:18:31.110 align:middle line:84%
that we're currently logged
on as the admin user, not

00:18:31.110 --> 00:18:32.010 align:middle line:90%
administrator.

00:18:32.010 --> 00:18:35.220 align:middle line:84%
This is another user
called admin that is not

00:18:35.220 --> 00:18:37.530 align:middle line:84%
the administrator
user but again should

00:18:37.530 --> 00:18:40.200 align:middle line:84%
be a part of the local
administrator's group.

00:18:40.200 --> 00:18:44.220 align:middle line:84%
We can, of course, identify
this through a command shell.

00:18:44.220 --> 00:18:46.590 align:middle line:84%
But before we do
that, we can also

00:18:46.590 --> 00:18:48.690 align:middle line:84%
get the current
privileges of this user

00:18:48.690 --> 00:18:51.210 align:middle line:84%
through Meterpreter
by saying getprivs.

00:18:51.210 --> 00:18:54.510 align:middle line:84%
And you can see the
privileges of very few,

00:18:54.510 --> 00:18:57.840 align:middle line:84%
and this indicates that
this user is not privileged

00:18:57.840 --> 00:18:58.995 align:middle line:90%
at this point in time.

00:18:58.995 --> 00:19:00.870 align:middle line:84%
Now that doesn't mean
that they can't perform

00:19:00.870 --> 00:19:03.810 align:middle line:84%
any administrative
activity or tasks

00:19:03.810 --> 00:19:06.480 align:middle line:84%
like running a program
as administrator

00:19:06.480 --> 00:19:10.530 align:middle line:84%
or executing a
malicious executable

00:19:10.530 --> 00:19:12.810 align:middle line:90%
or payload as the administrator.

00:19:12.810 --> 00:19:15.120 align:middle line:84%
So again, to verify
that this user is

00:19:15.120 --> 00:19:17.100 align:middle line:84%
a part of the local
administrator's group,

00:19:17.100 --> 00:19:19.200 align:middle line:84%
I'm just going to open
up a shell session.

00:19:19.200 --> 00:19:22.890 align:middle line:84%
And we can identify that
information by saying--

00:19:22.890 --> 00:19:25.230 align:middle line:84%
we can start off
by saying net user.

00:19:25.230 --> 00:19:28.117 align:middle line:84%
And you can see there's only
really two user accounts.

00:19:28.117 --> 00:19:30.450 align:middle line:84%
We have the administrator
account and the admin account,

00:19:30.450 --> 00:19:32.080 align:middle line:90%
which again is very different.

00:19:32.080 --> 00:19:34.410 align:middle line:84%
It's not to be
confused or mistaken

00:19:34.410 --> 00:19:36.030 align:middle line:90%
as the administrator account.

00:19:36.030 --> 00:19:42.100 align:middle line:84%
So we can then say net
local group administrators,

00:19:42.100 --> 00:19:44.290 align:middle line:84%
and you can see that
the admin user is

00:19:44.290 --> 00:19:46.900 align:middle line:84%
a part of the
Administrators group, which

00:19:46.900 --> 00:19:50.140 align:middle line:84%
means that this user can
essentially execute programs

00:19:50.140 --> 00:19:52.930 align:middle line:84%
with elevated privileges,
but in order to do

00:19:52.930 --> 00:19:54.880 align:middle line:90%
that, we'll need to bypass UAC.

00:19:54.880 --> 00:19:58.040 align:middle line:84%
An example of this
would be, for example,

00:19:58.040 --> 00:20:02.470 align:middle line:84%
if I was to say net user admin,
and I specify a new password

00:20:02.470 --> 00:20:04.900 align:middle line:84%
for that user like
123, you will see

00:20:04.900 --> 00:20:06.550 align:middle line:90%
it'll tell me access is denied.

00:20:06.550 --> 00:20:08.210 align:middle line:90%
System error five as occurred.

00:20:08.210 --> 00:20:10.990 align:middle line:84%
So that means the only
reason that's being denied

00:20:10.990 --> 00:20:16.690 align:middle line:84%
is because, again, this
particular activity or the act

00:20:16.690 --> 00:20:19.090 align:middle line:84%
of changing a
password for a user

00:20:19.090 --> 00:20:21.970 align:middle line:84%
requires me to
essentially accept

00:20:21.970 --> 00:20:26.170 align:middle line:84%
whenever the UAC consent form
or dialog box is brought up.

00:20:26.170 --> 00:20:28.840 align:middle line:84%
And through a command
shell, that really

00:20:28.840 --> 00:20:31.900 align:middle line:84%
can be done unless
we bypass UAC.

00:20:31.900 --> 00:20:35.830 align:middle line:84%
So now that we've taken a
look at how to gain access

00:20:35.830 --> 00:20:37.570 align:middle line:84%
to the target system
and we're verified

00:20:37.570 --> 00:20:39.700 align:middle line:84%
that the current user
account that we have access

00:20:39.700 --> 00:20:42.920 align:middle line:84%
to is part of the local
administrator's group

00:20:42.920 --> 00:20:46.270 align:middle line:84%
let's take a closer
look at UACMe.

00:20:46.270 --> 00:20:50.013 align:middle line:84%
So I'm just going to switch over
to the UACMe GitHub repository

00:20:50.013 --> 00:20:50.680 align:middle line:90%
right over here.

00:20:50.680 --> 00:20:53.110 align:middle line:84%
And of course, the link
to this GitHub repository

00:20:53.110 --> 00:20:55.190 align:middle line:90%
is attached to these slides.

00:20:55.190 --> 00:20:58.150 align:middle line:84%
And you can see that it's
a fairly simple GitHub

00:20:58.150 --> 00:21:02.140 align:middle line:84%
repository in that you have
the source code for the Akagi

00:21:02.140 --> 00:21:06.250 align:middle line:84%
executable, which is what is
going to help us bypass UAC.

00:21:06.250 --> 00:21:08.740 align:middle line:84%
And these are going
to be stored in

00:21:08.740 --> 00:21:11.980 align:middle line:84%
the decompiled or precompiled
binaries are going

00:21:11.980 --> 00:21:14.008 align:middle line:84%
to be stored in
binary, or rather

00:21:14.008 --> 00:21:15.550 align:middle line:84%
if we take a look
at the source, they

00:21:15.550 --> 00:21:18.910 align:middle line:84%
should be stored within the
source folder under Akagi.

00:21:18.910 --> 00:21:21.610 align:middle line:84%
And we have them under
the binaries here.

00:21:21.610 --> 00:21:23.740 align:middle line:84%
Now, this particular
lab environment

00:21:23.740 --> 00:21:28.760 align:middle line:84%
already has the Akagi executable
stored on the desktop.

00:21:28.760 --> 00:21:30.550 align:middle line:84%
So I'll just take
a step back here,

00:21:30.550 --> 00:21:33.610 align:middle line:84%
and let's take a look at
the documentation for UACMe

00:21:33.610 --> 00:21:35.480 align:middle line:84%
because it's very,
very important.

00:21:35.480 --> 00:21:37.750 align:middle line:84%
So you can see the
actual readme tells you

00:21:37.750 --> 00:21:41.050 align:middle line:84%
that this is used to
defeat Windows user account

00:21:41.050 --> 00:21:43.570 align:middle line:84%
control by abusing
built-in Windows

00:21:43.570 --> 00:21:45.370 align:middle line:90%
or to elevate back door.

00:21:45.370 --> 00:21:47.530 align:middle line:84%
So it's essentially
abusing or taking

00:21:47.530 --> 00:21:51.070 align:middle line:84%
advantage of the auto
elevate feature in Windows.

00:21:51.070 --> 00:21:52.310 align:middle line:90%
The system requirements.

00:21:52.310 --> 00:21:56.050 align:middle line:84%
You can see that it runs on
both 32-bit and 64-bit versions

00:21:56.050 --> 00:21:58.750 align:middle line:90%
of Windows 7, 8, 8.1, and 10.

00:21:58.750 --> 00:22:02.440 align:middle line:84%
And again, some methods
also work on Windows Server

00:22:02.440 --> 00:22:05.440 align:middle line:84%
as well, which in this
case, our target is actually

00:22:05.440 --> 00:22:07.840 align:middle line:90%
running Windows Server 2012.

00:22:07.840 --> 00:22:10.930 align:middle line:84%
So an admin account with UAC
set on the default settings

00:22:10.930 --> 00:22:11.570 align:middle line:90%
is required.

00:22:11.570 --> 00:22:14.440 align:middle line:84%
Remember, I highlighted this
on the Windows 10 system.

00:22:14.440 --> 00:22:16.900 align:middle line:84%
And again, if we take
a look at the usage,

00:22:16.900 --> 00:22:19.610 align:middle line:84%
we can run the executable
from the command line.

00:22:19.610 --> 00:22:22.060 align:middle line:84%
So we specify the
Akagi executable.

00:22:22.060 --> 00:22:25.360 align:middle line:84%
We then specify a
key and parameter.

00:22:25.360 --> 00:22:29.590 align:middle line:84%
And of course, this goes for
the 64-bit executable as well.

00:22:29.590 --> 00:22:34.180 align:middle line:84%
So the first parameter is
the number of method to use.

00:22:34.180 --> 00:22:37.630 align:middle line:84%
You can take a look
at the various methods

00:22:37.630 --> 00:22:41.020 align:middle line:84%
you can use by clicking
on the keys dropdown here.

00:22:41.020 --> 00:22:43.580 align:middle line:84%
And these are the various
methods you can specify.

00:22:43.580 --> 00:22:46.060 align:middle line:84%
So, for example, if I
wanted to use method one,

00:22:46.060 --> 00:22:52.480 align:middle line:84%
I would specify within my
command line akagi64.exe1

00:22:52.480 --> 00:22:55.480 align:middle line:84%
and then the application
or the path to the payload

00:22:55.480 --> 00:22:58.390 align:middle line:84%
that I want to execute with
administrative privileges

00:22:58.390 --> 00:23:02.350 align:middle line:84%
and consequently bypass UAC
during the execution process.

00:23:02.350 --> 00:23:05.890 align:middle line:84%
And the version or the type
of method that you will use

00:23:05.890 --> 00:23:08.680 align:middle line:84%
will depend on the
version of Windows

00:23:08.680 --> 00:23:11.890 align:middle line:84%
that is running on the target
as well as the technique

00:23:11.890 --> 00:23:15.730 align:middle line:84%
that again you have
found to be most suitable

00:23:15.730 --> 00:23:17.890 align:middle line:90%
in this particular scenario.

00:23:17.890 --> 00:23:20.770 align:middle line:84%
And if you click on the
keys right over here,

00:23:20.770 --> 00:23:22.660 align:middle line:84%
you can see it'll provide
you with the author

00:23:22.660 --> 00:23:24.490 align:middle line:90%
the type of method.

00:23:24.490 --> 00:23:26.920 align:middle line:84%
In this case, this
one is Dll hijacking.

00:23:26.920 --> 00:23:29.560 align:middle line:84%
The method is through
the IFile operation.

00:23:29.560 --> 00:23:34.300 align:middle line:84%
And the target or the actual
executable being used here

00:23:34.300 --> 00:23:36.610 align:middle line:90%
is sysprep.exe.

00:23:36.610 --> 00:23:39.880 align:middle line:84%
And it'll tell you on
what versions of Windows

00:23:39.880 --> 00:23:40.610 align:middle line:90%
it works on.

00:23:40.610 --> 00:23:42.520 align:middle line:84%
So, in this case,
from Windows 7,

00:23:42.520 --> 00:23:45.610 align:middle line:84%
build 7600, which
is service pack one.

00:23:45.610 --> 00:23:49.090 align:middle line:84%
However, you can see that
method one or key one

00:23:49.090 --> 00:23:54.460 align:middle line:84%
has been fixed in Windows
8.1 because sysprep.exe

00:23:54.460 --> 00:23:56.410 align:middle line:90%
has been hardened.

00:23:56.410 --> 00:23:58.480 align:middle line:84%
So, in this case,
we are going to be

00:23:58.480 --> 00:24:01.390 align:middle line:84%
utilizing method 23
as it works the best

00:24:01.390 --> 00:24:03.410 align:middle line:90%
in this particular scenario.

00:24:03.410 --> 00:24:05.260 align:middle line:84%
The author of this
particular method

00:24:05.260 --> 00:24:07.390 align:middle line:90%
is Leo Davidson derivative.

00:24:07.390 --> 00:24:10.070 align:middle line:84%
And, of course, this is a
derivative from the original.

00:24:10.070 --> 00:24:12.700 align:middle line:84%
So the type is Dll
hijacking, and we

00:24:12.700 --> 00:24:16.600 align:middle line:84%
are utilizing the
packagemanager.exe executable.

00:24:16.600 --> 00:24:19.390 align:middle line:84%
Now the package manager
utility on Windows

00:24:19.390 --> 00:24:22.690 align:middle line:84%
can be used to
install executables.

00:24:22.690 --> 00:24:26.470 align:middle line:84%
However, again this
particular executable

00:24:26.470 --> 00:24:28.780 align:middle line:90%
is not vulnerable inherently.

00:24:28.780 --> 00:24:30.850 align:middle line:84%
The Akagi executable
will actually

00:24:30.850 --> 00:24:33.790 align:middle line:84%
help us bypass UAC
because even if we

00:24:33.790 --> 00:24:37.660 align:middle line:84%
were to use package manager
to essentially execute

00:24:37.660 --> 00:24:41.240 align:middle line:84%
a malicious payload, it will
still bring up the UAC consent

00:24:41.240 --> 00:24:43.250 align:middle line:90%
form or dialog box.

00:24:43.250 --> 00:24:46.490 align:middle line:84%
And this works from
Windows 7, which

00:24:46.490 --> 00:24:50.210 align:middle line:84%
is build 7600, which
is service pack one,

00:24:50.210 --> 00:24:53.090 align:middle line:90%
and it is still unfixed.

00:24:53.090 --> 00:24:56.520 align:middle line:84%
So again, if you want to take
a look at this particular tool

00:24:56.520 --> 00:25:00.120 align:middle line:84%
and the documentation here, be
sure to clone the repository.

00:25:00.120 --> 00:25:03.470 align:middle line:84%
And again, compiling the
source code is fairly simple,

00:25:03.470 --> 00:25:06.120 align:middle line:84%
and instructions on how this
can be done have also been

00:25:06.120 --> 00:25:07.640 align:middle line:90%
had also been added here.

00:25:07.640 --> 00:25:10.880 align:middle line:84%
You can see UACMe comes with
full source code written

00:25:10.880 --> 00:25:12.950 align:middle line:84%
in C. In order to
build from source,

00:25:12.950 --> 00:25:16.520 align:middle line:84%
you need Microsoft Visual
Studio 15 and later versions.

00:25:16.520 --> 00:25:18.260 align:middle line:84%
As you can see,
compiled binaries here.

00:25:18.260 --> 00:25:20.450 align:middle line:84%
They are not
provided since 2.8.9

00:25:20.450 --> 00:25:23.540 align:middle line:84%
and will never be
provided in the future.

00:25:23.540 --> 00:25:26.840 align:middle line:84%
The reasons and why you
should too not provide them

00:25:26.840 --> 00:25:28.970 align:middle line:84%
to the general
public, and of course,

00:25:28.970 --> 00:25:31.490 align:middle line:84%
it gives you the reason why the
precompiled binaries are not

00:25:31.490 --> 00:25:32.190 align:middle line:90%
available.

00:25:32.190 --> 00:25:36.260 align:middle line:84%
However, in this case, or in the
case of this lab environment,

00:25:36.260 --> 00:25:40.730 align:middle line:84%
the Akagi 64 executable
has been provided for you,

00:25:40.730 --> 00:25:42.230 align:middle line:90%
the compiled version rather.

00:25:42.230 --> 00:25:44.570 align:middle line:84%
And all you need to do
is just transfer it over

00:25:44.570 --> 00:25:47.510 align:middle line:84%
to the target system, and
we'll be able to use it.

00:25:47.510 --> 00:25:51.950 align:middle line:84%
So I'm just going to switch
back over to the lab environment

00:25:51.950 --> 00:25:54.200 align:middle line:84%
right over here, and
we can take a look

00:25:54.200 --> 00:25:59.750 align:middle line:84%
at how we can use
Akagi in a few seconds.

00:25:59.750 --> 00:26:02.360 align:middle line:84%
Again, if we just
terminate this channel

00:26:02.360 --> 00:26:06.140 align:middle line:84%
and head back over into
our Meterpreter session,

00:26:06.140 --> 00:26:07.670 align:middle line:90%
we can upload it directly.

00:26:07.670 --> 00:26:11.060 align:middle line:84%
It is currently stored under
the desktop within this lab

00:26:11.060 --> 00:26:15.650 align:middle line:84%
environment under tools, and
it is stored under UACMe.

00:26:15.650 --> 00:26:16.310 align:middle line:90%
There we are.

00:26:16.310 --> 00:26:19.220 align:middle line:90%
And you have akagi64.exe

00:26:19.220 --> 00:26:22.250 align:middle line:84%
So before we do
that, we are going

00:26:22.250 --> 00:26:26.505 align:middle line:84%
to be generating a Meterpreter
payload with msfvenom.

00:26:26.505 --> 00:26:28.130 align:middle line:84%
We are then going to
be transferring it

00:26:28.130 --> 00:26:32.000 align:middle line:84%
over to the target, and we will
then use the Akagi executable

00:26:32.000 --> 00:26:35.900 align:middle line:84%
with the key or the method
23, and we will then

00:26:35.900 --> 00:26:39.980 align:middle line:84%
execute the payload or
the Meterpreter payload

00:26:39.980 --> 00:26:41.780 align:middle line:84%
that we've just
generated, and that

00:26:41.780 --> 00:26:46.070 align:middle line:84%
should bypass UAC and provide
us with an elevated Meterpreter

00:26:46.070 --> 00:26:48.060 align:middle line:90%
session on our listeners.

00:26:48.060 --> 00:26:49.670 align:middle line:84%
So the first step
here will involve

00:26:49.670 --> 00:26:53.150 align:middle line:84%
generating the interpreter
payload with MSF venom.

00:26:53.150 --> 00:26:56.090 align:middle line:84%
So I'm just going to say
msfvenom in a new tab.

00:26:56.090 --> 00:27:04.030 align:middle line:84%
Payload is windows,
meterpreter, reverse tcp.

00:27:04.030 --> 00:27:05.590 align:middle line:84%
And the LHOST host
option is going

00:27:05.590 --> 00:27:07.810 align:middle line:84%
to be your Kali
Linux IP which you

00:27:07.810 --> 00:27:10.480 align:middle line:90%
can obtain by saying ifconfig.

00:27:10.480 --> 00:27:13.270 align:middle line:84%
So I can take a look at
the Ethernet one interface,

00:27:13.270 --> 00:27:14.800 align:middle line:90%
and this is my IP address here.

00:27:14.800 --> 00:27:17.050 align:middle line:84%
In your case, it will
be different, so just

00:27:17.050 --> 00:27:18.490 align:middle line:90%
take note of that.

00:27:18.490 --> 00:27:20.320 align:middle line:84%
And then the LPORT,
I'm just going

00:27:20.320 --> 00:27:24.340 align:middle line:84%
to use port 1234 because I want
to keep things nice and simple

00:27:24.340 --> 00:27:25.310 align:middle line:90%
here.

00:27:25.310 --> 00:27:27.460 align:middle line:84%
We're going to output
this into exe format.

00:27:27.460 --> 00:27:31.030 align:middle line:84%
And we will call
this backdoor.exe.

00:27:31.030 --> 00:27:33.610 align:middle line:84%
And of course, you can
call it whatever you want.

00:27:33.610 --> 00:27:37.040 align:middle line:84%
However, for the
purpose of simplicity,

00:27:37.040 --> 00:27:39.520 align:middle line:84%
I'm just going to
call it backdoor.exe.

00:27:39.520 --> 00:27:40.900 align:middle line:90%
I'll hit Enter.

00:27:40.900 --> 00:27:45.410 align:middle line:84%
That's going to generate
the payload for me.

00:27:45.410 --> 00:27:46.190 align:middle line:90%
There we are.

00:27:46.190 --> 00:27:50.120 align:middle line:84%
And if I list out the contents
of my home directory here

00:27:50.120 --> 00:27:52.190 align:middle line:84%
and we are currently
using the root user,

00:27:52.190 --> 00:27:56.210 align:middle line:84%
you can see we have
backdoor.exe uploaded or created

00:27:56.210 --> 00:27:57.470 align:middle line:90%
right over there.

00:27:57.470 --> 00:28:00.410 align:middle line:84%
The next step, of course,
is to set up our listener

00:28:00.410 --> 00:28:01.970 align:middle line:90%
with msfconsole.

00:28:01.970 --> 00:28:03.560 align:middle line:90%
So I'll say msfconsole.

00:28:03.560 --> 00:28:05.840 align:middle line:84%
And, of course, I'm opening
a new Metasploit framework

00:28:05.840 --> 00:28:07.100 align:middle line:90%
console session.

00:28:07.100 --> 00:28:09.770 align:middle line:84%
And we then want to set
up our multi-handler

00:28:09.770 --> 00:28:12.590 align:middle line:84%
to receive the connection
once the payload is

00:28:12.590 --> 00:28:13.820 align:middle line:90%
executed on the target.

00:28:13.820 --> 00:28:16.292 align:middle line:84%
So I'm going to say
use multi-handler.

00:28:16.292 --> 00:28:17.750 align:middle line:84%
We're then going
to set the payload

00:28:17.750 --> 00:28:21.830 align:middle line:84%
we specified when generating the
actual payload with msfvenom.

00:28:21.830 --> 00:28:25.160 align:middle line:84%
In this case, we said we
specify the payload as Windows

00:28:25.160 --> 00:28:30.490 align:middle line:90%
Meterpreter reverse tcp.

00:28:30.490 --> 00:28:34.240 align:middle line:84%
We're then going to set the
lowest option to my Kali Linux

00:28:34.240 --> 00:28:34.840 align:middle line:90%
IP.

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

00:28:37.173 --> 00:28:39.130 align:middle line:84%
So I'm just going
to copy that again,

00:28:39.130 --> 00:28:41.860 align:middle line:84%
and we'll set that
to my IP there.

00:28:41.860 --> 00:28:44.650 align:middle line:84%
And set the LPORT to the
port that I had configured,

00:28:44.650 --> 00:28:48.490 align:middle line:84%
which in this case, is
1234, and I'll hit Run.

00:28:48.490 --> 00:28:50.680 align:middle line:84%
So we have the
reverse tcp handler

00:28:50.680 --> 00:28:54.310 align:middle line:84%
listening on port 1234 ready
to receive the connection

00:28:54.310 --> 00:28:56.530 align:middle line:84%
from the malicious or
the Meterpreter payload

00:28:56.530 --> 00:28:58.580 align:middle line:90%
that we just generated.

00:28:58.580 --> 00:29:01.570 align:middle line:84%
So now that we've done
that let me head back

00:29:01.570 --> 00:29:03.340 align:middle line:84%
into my Meterpreter
session here.

00:29:03.340 --> 00:29:05.290 align:middle line:84%
If I type in pwd,
we are currently

00:29:05.290 --> 00:29:07.600 align:middle line:90%
within Windows System32.

00:29:07.600 --> 00:29:11.260 align:middle line:84%
And if I say get user
ID and getprivs just

00:29:11.260 --> 00:29:14.710 align:middle line:84%
to confirm that we don't
have any privileges,

00:29:14.710 --> 00:29:19.030 align:middle line:84%
you can see we still have
very few privileges here.

00:29:19.030 --> 00:29:21.340 align:middle line:84%
So I'll navigate to the
root of the C drive,

00:29:21.340 --> 00:29:24.780 align:middle line:84%
and I'll create
a temp directory.

00:29:24.780 --> 00:29:25.590 align:middle line:90%
There we are.

00:29:25.590 --> 00:29:26.970 align:middle line:90%
Make Directory temp.

00:29:26.970 --> 00:29:28.890 align:middle line:84%
And as I said,
the temp directory

00:29:28.890 --> 00:29:31.620 align:middle line:84%
is pretty much the best
location for transferring

00:29:31.620 --> 00:29:34.380 align:middle line:84%
exploit code or executables
because you never

00:29:34.380 --> 00:29:36.720 align:middle line:84%
want to upload executable
or exploit code

00:29:36.720 --> 00:29:39.270 align:middle line:84%
to directories that
are frequently accessed

00:29:39.270 --> 00:29:41.050 align:middle line:90%
by users on the system.

00:29:41.050 --> 00:29:43.650 align:middle line:90%
So we'll navigate into temp.

00:29:43.650 --> 00:29:46.300 align:middle line:84%
There we are, and we'll
upload the back door first,

00:29:46.300 --> 00:29:50.590 align:middle line:84%
so I'm just going to say
upload back door dot exe.

00:29:50.590 --> 00:29:54.580 align:middle line:84%
There we are, and we now
need to upload Akagi 64.

00:29:54.580 --> 00:30:00.790 align:middle line:84%
So that's stored under root
desktop tools UACME and Akagi

00:30:00.790 --> 00:30:02.120 align:middle line:90%
64 dot exe.

00:30:02.120 --> 00:30:03.700 align:middle line:90%
All right, so I'll hit Enter.

00:30:03.700 --> 00:30:05.360 align:middle line:90%
That's going to upload it.

00:30:05.360 --> 00:30:07.840 align:middle line:84%
And I can open up a
shell session now,

00:30:07.840 --> 00:30:11.560 align:middle line:84%
and again, if I take a look at
the contents of this directory,

00:30:11.560 --> 00:30:15.350 align:middle line:84%
we have Akagi 64.exe
and backdoor.exe.

00:30:15.350 --> 00:30:18.410 align:middle line:84%
All right, so if we wanted
to execute backdoor.exe

00:30:18.410 --> 00:30:21.190 align:middle line:84%
with administrative
privileges, we

00:30:21.190 --> 00:30:23.830 align:middle line:84%
would not be able to
do it because again UAC

00:30:23.830 --> 00:30:26.780 align:middle line:84%
would essentially prevent
us from doing that.

00:30:26.780 --> 00:30:29.830 align:middle line:84%
So in order to bypass UAC
on this particular version

00:30:29.830 --> 00:30:34.720 align:middle line:84%
of Windows, we'll be
using method 23, or key 23

00:30:34.720 --> 00:30:37.270 align:middle line:84%
rather, which essentially
takes advantage

00:30:37.270 --> 00:30:39.260 align:middle line:90%
of package manager on Windows.

00:30:39.260 --> 00:30:49.310 align:middle line:84%
So again, I'll say Akagi64.exe
method 23 or key 23

00:30:49.310 --> 00:30:51.800 align:middle line:84%
and then I specify
the path to backdoor,

00:30:51.800 --> 00:30:55.580 align:middle line:84%
which is C on the temp, and
the name of the executable

00:30:55.580 --> 00:30:56.510 align:middle line:90%
is backdoor.exe.

00:30:56.510 --> 00:30:59.870 align:middle line:84%
Now when I hit Enter,
this will again

00:30:59.870 --> 00:31:03.710 align:middle line:84%
bypass UAC and backdoor.exe
should be executed

00:31:03.710 --> 00:31:06.290 align:middle line:84%
with elevated or
administrative privileges,

00:31:06.290 --> 00:31:08.360 align:middle line:84%
and because it is a
Meterpreter payload,

00:31:08.360 --> 00:31:10.290 align:middle line:84%
we should receive an
elevated Meterpreter

00:31:10.290 --> 00:31:13.380 align:middle line:84%
session on our listener
right over here.

00:31:13.380 --> 00:31:15.290 align:middle line:90%
So I'm just going to hit Enter.

00:31:15.290 --> 00:31:17.220 align:middle line:90%
You can see it's executed there.

00:31:17.220 --> 00:31:18.770 align:middle line:84%
And if we take a
look at our listener

00:31:18.770 --> 00:31:22.610 align:middle line:84%
here or our reverse TCP handler,
we can see it sends the stage

00:31:22.610 --> 00:31:24.740 align:middle line:84%
and we get a new
Meterpreter session.

00:31:24.740 --> 00:31:30.210 align:middle line:84%
So we can say this
info and get user ID,

00:31:30.210 --> 00:31:34.120 align:middle line:84%
and we still have access via the
admin user, which makes sense,

00:31:34.120 --> 00:31:37.470 align:middle line:84%
and if I say get
privs, you can see

00:31:37.470 --> 00:31:40.890 align:middle line:84%
we now have elevated privileges,
even though we have access

00:31:40.890 --> 00:31:42.280 align:middle line:90%
to the admin user.

00:31:42.280 --> 00:31:44.610 align:middle line:84%
So we have an increased
amount of privileges

00:31:44.610 --> 00:31:47.620 align:middle line:84%
and really this is
an elevated session.

00:31:47.620 --> 00:31:50.010 align:middle line:84%
However, if we list out
our process tree here,

00:31:50.010 --> 00:31:52.440 align:middle line:84%
we can migrate to any
of the other processes

00:31:52.440 --> 00:31:55.680 align:middle line:84%
here that have NT authority
system privileges.

00:31:55.680 --> 00:31:57.630 align:middle line:84%
And because we
are privileged, we

00:31:57.630 --> 00:31:59.390 align:middle line:84%
can migrate to any
of these services.

00:31:59.390 --> 00:32:03.750 align:middle line:84%
So for example, I can migrate
to the lsass.exe service

00:32:03.750 --> 00:32:06.930 align:middle line:84%
here that currently has NT
authority system privileges

00:32:06.930 --> 00:32:12.690 align:middle line:90%
so I can say migrate to 688.

00:32:12.690 --> 00:32:16.130 align:middle line:84%
There we are and
that will migrate,

00:32:16.130 --> 00:32:19.220 align:middle line:84%
and that will also provide
us with a 64-bit Meterpreter

00:32:19.220 --> 00:32:20.820 align:middle line:90%
session, as you can see here.

00:32:20.820 --> 00:32:25.880 align:middle line:84%
And if I now say get user
ID NT authority system,

00:32:25.880 --> 00:32:28.670 align:middle line:84%
and we've successfully been
able to elevate our privileges

00:32:28.670 --> 00:32:30.620 align:middle line:90%
by bypassing UAC.

00:32:30.620 --> 00:32:35.270 align:middle line:84%
And in this case, by bypassing
UAC on a system running Windows

00:32:35.270 --> 00:32:37.100 align:middle line:90%
Server 2012 R2.

00:32:37.100 --> 00:32:41.660 align:middle line:84%
Now I will be exploring
UACME in future courses,

00:32:41.660 --> 00:32:46.280 align:middle line:84%
primarily because UACME is quite
a complicated tool in regards

00:32:46.280 --> 00:32:48.990 align:middle line:84%
to what technique or
what method to use.

00:32:48.990 --> 00:32:50.780 align:middle line:84%
And as I said, that
will require a lot

00:32:50.780 --> 00:32:52.640 align:middle line:84%
of understanding of
the version of Windows

00:32:52.640 --> 00:32:54.620 align:middle line:84%
that you are
currently targeting.

00:32:54.620 --> 00:32:56.690 align:middle line:84%
And of course, I would
recommend that you

00:32:56.690 --> 00:32:58.370 align:middle line:84%
test this out
within your own home

00:32:58.370 --> 00:33:00.560 align:middle line:84%
lab to learn more about
what techniques work

00:33:00.560 --> 00:33:03.930 align:middle line:84%
and what techniques don't
work on different versions

00:33:03.930 --> 00:33:04.430 align:middle line:90%
of Windows.

00:33:04.430 --> 00:33:06.680 align:middle line:84%
So again, I would recommend
setting up a Windows 7

00:33:06.680 --> 00:33:10.520 align:middle line:84%
VM, a Windows 10 VM,
Windows 8.1 VM, and then

00:33:10.520 --> 00:33:14.300 align:middle line:84%
utilizing UACME or Akagi
to essentially test out

00:33:14.300 --> 00:33:16.230 align:middle line:84%
the various methods
that you can use.

00:33:16.230 --> 00:33:18.420 align:middle line:84%
And as I said, it's
fairly simple to use,

00:33:18.420 --> 00:33:20.760 align:middle line:84%
and you can try out all
of these methods here.

00:33:20.760 --> 00:33:22.970 align:middle line:84%
Of course, I would
recommend avoiding

00:33:22.970 --> 00:33:24.973 align:middle line:90%
the ones that have been fixed.

00:33:24.973 --> 00:33:26.390 align:middle line:84%
And of course, you
can take a look

00:33:26.390 --> 00:33:30.290 align:middle line:84%
at a few other interesting
ones like Key 33,

00:33:30.290 --> 00:33:34.050 align:middle line:84%
which in my experience has
worked quite well for me.

00:33:34.050 --> 00:33:36.140 align:middle line:84%
And you can see that
this is still unfixed

00:33:36.140 --> 00:33:39.650 align:middle line:84%
and this works on or
from Windows versions 10,

00:33:39.650 --> 00:33:41.790 align:middle line:84%
and it provides you with
the build number there.

00:33:41.790 --> 00:33:45.110 align:middle line:84%
So this is really the
actual method or key

00:33:45.110 --> 00:33:47.990 align:middle line:84%
that I use when I'm
targeting or trying to bypass

00:33:47.990 --> 00:33:50.240 align:middle line:90%
UAC on Windows 10 systems.

00:33:50.240 --> 00:33:52.880 align:middle line:84%
So again, definitely check
out the GitHub repository,

00:33:52.880 --> 00:33:56.750 align:middle line:84%
learn more about
how UACME works,

00:33:56.750 --> 00:33:59.180 align:middle line:84%
and the various methods
that you can use.

00:33:59.180 --> 00:34:01.070 align:middle line:84%
All right, so that
is going to conclude

00:34:01.070 --> 00:34:05.090 align:middle line:84%
the practical demonstration
side of this video.

00:34:05.090 --> 00:34:09.159 align:middle line:84%
All right, so that is how to
bypass UAC on Windows systems

00:34:09.159 --> 00:34:11.440 align:middle line:84%
in order to elevate
your privileges.

00:34:11.440 --> 00:34:15.730 align:middle line:84%
Now this is by no means an
exhaustive view or exposition

00:34:15.730 --> 00:34:19.690 align:middle line:84%
into privilege escalation
via UAC bypass.

00:34:19.690 --> 00:34:22.330 align:middle line:84%
I will be exploring
privilege escalation in depth

00:34:22.330 --> 00:34:25.880 align:middle line:84%
in its own course, so
do stay tuned for that.

00:34:25.880 --> 00:34:29.030 align:middle line:84%
However, in the next
video within this course,

00:34:29.030 --> 00:34:31.540 align:middle line:84%
we are going to be exploring
the process of elevating

00:34:31.540 --> 00:34:33.940 align:middle line:84%
our privileges on
a Windows system

00:34:33.940 --> 00:34:36.489 align:middle line:84%
by taking advantage
of access tokens,

00:34:36.489 --> 00:34:39.100 align:middle line:84%
and more specifically,
we will be

00:34:39.100 --> 00:34:40.960 align:middle line:84%
exploring the
process of performing

00:34:40.960 --> 00:34:43.010 align:middle line:90%
access token impersonation.

00:34:43.010 --> 00:34:46.650 align:middle line:84%
So I'll see you
in the next video.

00:34:46.650 --> 00:34:48.000 align:middle line:90%