WEBVTT

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


00:00:03.840 --> 00:00:05.760 align:middle line:90%
[CLICKING]

00:00:05.760 --> 00:00:08.640 align:middle line:90%
[MUSIC PLAYING]

00:00:08.640 --> 00:00:10.080 align:middle line:90%


00:00:10.080 --> 00:00:13.080 align:middle line:84%
Exploiting SUID
binaries-- all right,

00:00:13.080 --> 00:00:16.440 align:middle line:84%
so this is the final
privileged escalation technique

00:00:16.440 --> 00:00:18.930 align:middle line:84%
that we're going to be
exploring for Linux,

00:00:18.930 --> 00:00:21.840 align:middle line:84%
and it will involve
the exploitation

00:00:21.840 --> 00:00:25.890 align:middle line:90%
of misconfigured SUID binaries.

00:00:25.890 --> 00:00:29.220 align:middle line:84%
So let's get an understanding
of what SUID binaries are

00:00:29.220 --> 00:00:32.369 align:middle line:90%
or what the SUID permission is.

00:00:32.369 --> 00:00:35.250 align:middle line:84%
In addition to the three
main file access permissions

00:00:35.250 --> 00:00:38.070 align:middle line:84%
on Linux-- you have your
read, write, and execute--

00:00:38.070 --> 00:00:41.400 align:middle line:84%
Linux also provides users
with specialized permissions

00:00:41.400 --> 00:00:44.490 align:middle line:84%
that can be utilized
in specific situations.

00:00:44.490 --> 00:00:48.600 align:middle line:84%
One of these access permissions
is the SUID permission, which

00:00:48.600 --> 00:00:51.150 align:middle line:90%
stands for Set Owner User ID.

00:00:51.150 --> 00:00:53.460 align:middle line:84%
When applied to
a file or binary,

00:00:53.460 --> 00:00:56.430 align:middle line:84%
this permission provides
users with the ability

00:00:56.430 --> 00:00:59.640 align:middle line:84%
to execute a script or
binary with the permissions

00:00:59.640 --> 00:01:02.820 align:middle line:84%
of the file owner, as
opposed to the user that is

00:01:02.820 --> 00:01:05.160 align:middle line:90%
running the script or binary.

00:01:05.160 --> 00:01:07.260 align:middle line:84%
SUID permissions
are typically used

00:01:07.260 --> 00:01:09.810 align:middle line:84%
to provide unprivileged
users with the ability

00:01:09.810 --> 00:01:14.130 align:middle line:84%
to run specific scripts or
binaries with root permissions.

00:01:14.130 --> 00:01:17.160 align:middle line:84%
It needs to be noted,
however, that the provision

00:01:17.160 --> 00:01:19.530 align:middle line:84%
of elevated
privileges is limited

00:01:19.530 --> 00:01:22.290 align:middle line:84%
to the execution of
the script or binary

00:01:22.290 --> 00:01:25.170 align:middle line:84%
and does not translate to
elevation of privileges.

00:01:25.170 --> 00:01:27.840 align:middle line:84%
However, if
improperly configured,

00:01:27.840 --> 00:01:30.870 align:middle line:84%
unprivileged users can
exploit misconfigurations

00:01:30.870 --> 00:01:33.690 align:middle line:84%
or vulnerabilities within
the binary or script

00:01:33.690 --> 00:01:36.000 align:middle line:90%
to obtain an elevated session.

00:01:36.000 --> 00:01:38.700 align:middle line:84%
All right, so let me use
a scenario or example

00:01:38.700 --> 00:01:40.290 align:middle line:90%
to essentially explain this.

00:01:40.290 --> 00:01:44.340 align:middle line:84%
Now, I want you to think of a
binary on Linux that actually

00:01:44.340 --> 00:01:49.470 align:middle line:84%
allows standard users or users
to execute specific commands

00:01:49.470 --> 00:01:51.090 align:middle line:90%
with root privileges.

00:01:51.090 --> 00:01:54.150 align:middle line:84%
Well, one of these binaries
is the sudo binary, right?

00:01:54.150 --> 00:01:58.740 align:middle line:84%
So the sudo binary allows
users to essentially execute

00:01:58.740 --> 00:02:01.985 align:middle line:84%
specific commands
with root privileges.

00:02:01.985 --> 00:02:04.110 align:middle line:84%
And, of course, they need
to provide their password

00:02:04.110 --> 00:02:07.360 align:middle line:84%
that they need to be
part of the sudo group.

00:02:07.360 --> 00:02:11.340 align:middle line:84%
However, that particular binary
is owned by the root user,

00:02:11.340 --> 00:02:14.130 align:middle line:84%
and it is an SUID
binary in that it

00:02:14.130 --> 00:02:20.370 align:middle line:84%
allows unprivileged users to
execute that specific binary

00:02:20.370 --> 00:02:23.350 align:middle line:90%
with elevated privileges.

00:02:23.350 --> 00:02:27.030 align:middle line:84%
Now, again, this is something--
or this particular permission,

00:02:27.030 --> 00:02:28.950 align:middle line:84%
the SUID permission
is, as I said,

00:02:28.950 --> 00:02:32.490 align:middle line:84%
typically used to provide
non-privileged users

00:02:32.490 --> 00:02:34.500 align:middle line:84%
with the ability
to execute a script

00:02:34.500 --> 00:02:36.882 align:middle line:84%
or binary with the
permissions of the file owner.

00:02:36.882 --> 00:02:38.340 align:middle line:84%
And in this case,
we're going to be

00:02:38.340 --> 00:02:43.290 align:middle line:84%
looking for SUID binaries that
are owned by the root user.

00:02:43.290 --> 00:02:46.530 align:middle line:84%
Right now, as I said, as
highlighted previously,

00:02:46.530 --> 00:02:48.720 align:middle line:84%
it's to be noted
that the provision

00:02:48.720 --> 00:02:51.840 align:middle line:84%
of elevated
privileges is limited

00:02:51.840 --> 00:02:54.270 align:middle line:84%
to the execution of
the script or binary.

00:02:54.270 --> 00:02:58.890 align:middle line:84%
So it doesn't provide you with
a free range or free-for-all

00:02:58.890 --> 00:03:01.770 align:middle line:84%
elevated session after
executing the command.

00:03:01.770 --> 00:03:03.720 align:middle line:84%
It's only limited
to the execution

00:03:03.720 --> 00:03:05.380 align:middle line:90%
of that specific binary.

00:03:05.380 --> 00:03:08.490 align:middle line:84%
However, we can find
specific misconfigurations

00:03:08.490 --> 00:03:12.420 align:middle line:84%
or vulnerabilities within
the specific binary

00:03:12.420 --> 00:03:15.900 align:middle line:84%
that's been configured
with the SUID permission.

00:03:15.900 --> 00:03:18.300 align:middle line:84%
And if there are vulnerabilities
that we can exploit,

00:03:18.300 --> 00:03:23.850 align:middle line:84%
then we can get that SUID binary
to execute specific commands

00:03:23.850 --> 00:03:26.940 align:middle line:84%
with root privileges,
consequently providing us

00:03:26.940 --> 00:03:28.830 align:middle line:90%
with an elevated session.

00:03:28.830 --> 00:03:31.950 align:middle line:84%
Now, in terms of the
actual requirements

00:03:31.950 --> 00:03:35.190 align:middle line:84%
of what we're going to
be looking for, in order

00:03:35.190 --> 00:03:39.090 align:middle line:84%
to exploit an SUID
binary, in order

00:03:39.090 --> 00:03:42.570 align:middle line:84%
to elevate our privileges,
the actual technique,

00:03:42.570 --> 00:03:44.310 align:middle line:84%
or this particular
technique, will depend

00:03:44.310 --> 00:03:45.640 align:middle line:90%
on the following factors.

00:03:45.640 --> 00:03:48.630 align:middle line:84%
Number one, the owner
of the SUID binary--

00:03:48.630 --> 00:03:51.720 align:middle line:84%
given that we are attempting
to elevate our privileges,

00:03:51.720 --> 00:03:54.870 align:middle line:84%
we will only be
exploiting SUID binaries

00:03:54.870 --> 00:03:58.530 align:middle line:84%
that are owned by the root
user or other privileged users.

00:03:58.530 --> 00:04:00.750 align:middle line:84%
Secondly, the
access permissions--

00:04:00.750 --> 00:04:03.390 align:middle line:84%
we will require executable
permissions in order

00:04:03.390 --> 00:04:05.190 align:middle line:90%
to execute the SUID binary.

00:04:05.190 --> 00:04:07.950 align:middle line:84%
So we are really looking
for an SUID binary

00:04:07.950 --> 00:04:10.890 align:middle line:84%
that is owned by the root
user and that we can actually

00:04:10.890 --> 00:04:13.320 align:middle line:84%
execute with our current
permissions, which

00:04:13.320 --> 00:04:14.880 align:middle line:90%
are not elevated.

00:04:14.880 --> 00:04:16.649 align:middle line:84%
And as I said,
the objective here

00:04:16.649 --> 00:04:19.200 align:middle line:84%
is to identify or to
find a vulnerability

00:04:19.200 --> 00:04:22.650 align:middle line:84%
within that binary that we
can essentially take advantage

00:04:22.650 --> 00:04:26.490 align:middle line:84%
of and have the
SUID binary execute

00:04:26.490 --> 00:04:28.650 align:middle line:84%
additional commands
that will provide us

00:04:28.650 --> 00:04:30.150 align:middle line:90%
with an elevated session.

00:04:30.150 --> 00:04:33.070 align:middle line:84%
And the really ingenious ways
of doing this-- as I said,

00:04:33.070 --> 00:04:35.940 align:middle line:84%
there's a lot of techniques
and tools out there

00:04:35.940 --> 00:04:39.690 align:middle line:84%
that can be used to really
execute quite a few SUID

00:04:39.690 --> 00:04:41.520 align:middle line:84%
binaries if they
have been configured

00:04:41.520 --> 00:04:44.110 align:middle line:84%
with the SUID permission
for that matter.

00:04:44.110 --> 00:04:46.650 align:middle line:84%
So we're not looking
for standard binaries.

00:04:46.650 --> 00:04:50.760 align:middle line:84%
These binaries need to have the
SUID permission applied to them

00:04:50.760 --> 00:04:52.960 align:middle line:84%
and the owner needs
to be the root user.

00:04:52.960 --> 00:04:55.120 align:middle line:84%
So again, just
keep that in mind.

00:04:55.120 --> 00:04:59.070 align:middle line:84%
Now the lab environment that
has been attached to this video

00:04:59.070 --> 00:05:02.100 align:middle line:84%
will really highlight or
showcase how this can be done,

00:05:02.100 --> 00:05:04.830 align:middle line:84%
and all you need to do is just
fire up the lab environment

00:05:04.830 --> 00:05:07.470 align:middle line:84%
and I'll see you within
the lab environment.

00:05:07.470 --> 00:05:10.170 align:middle line:90%


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

00:05:12.730 --> 00:05:14.730 align:middle line:84%
And again, in this
case, you don't

00:05:14.730 --> 00:05:17.370 align:middle line:84%
need to gain access
to a target system.

00:05:17.370 --> 00:05:19.590 align:middle line:84%
This is a very similar
lab environment

00:05:19.590 --> 00:05:21.070 align:middle line:90%
to the previous video.

00:05:21.070 --> 00:05:23.340 align:middle line:84%
So you already logged
on the target system

00:05:23.340 --> 00:05:26.010 align:middle line:84%
as the user student,
who is not privileged.

00:05:26.010 --> 00:05:29.040 align:middle line:84%
And of course, if I say
whoami, you can see student.

00:05:29.040 --> 00:05:31.620 align:middle line:84%
And if I view the groups
that this particular user is

00:05:31.620 --> 00:05:34.710 align:middle line:84%
a part of-- so I can
say groups student.

00:05:34.710 --> 00:05:36.900 align:middle line:84%
You can see that it's a
part of its own group, which

00:05:36.900 --> 00:05:38.340 align:middle line:90%
is unprivileged.

00:05:38.340 --> 00:05:40.480 align:middle line:84%
It's really not part
of the sudo group,

00:05:40.480 --> 00:05:44.220 align:middle line:84%
so we can't do anything that
requires root privileges.

00:05:44.220 --> 00:05:47.220 align:middle line:84%
All right, so let's take
a look at the SUID binary

00:05:47.220 --> 00:05:48.420 align:middle line:90%
that we will be exploiting.

00:05:48.420 --> 00:05:51.990 align:middle line:84%
So I'm currently within the
working or home directory

00:05:51.990 --> 00:05:54.300 align:middle line:84%
of the student, which
is /home/student.

00:05:54.300 --> 00:05:56.940 align:middle line:84%
And if I list out the
contents of this directory,

00:05:56.940 --> 00:05:58.530 align:middle line:90%
we have two binaries here.

00:05:58.530 --> 00:06:00.510 align:middle line:84%
We have a binary
called greetings

00:06:00.510 --> 00:06:03.780 align:middle line:84%
and we have a binary
called welcome.

00:06:03.780 --> 00:06:09.240 align:middle line:84%
Now welcome, as we can see
here, is owned by the root user,

00:06:09.240 --> 00:06:13.115 align:middle line:84%
and we can actually execute
this particular binary,

00:06:13.115 --> 00:06:13.740 align:middle line:90%
as you can see.

00:06:13.740 --> 00:06:18.510 align:middle line:84%
Every user, every other user
account and group on the system

00:06:18.510 --> 00:06:20.290 align:middle line:90%
can execute this binary.

00:06:20.290 --> 00:06:24.930 align:middle line:84%
However, if we take or pay close
attention to this s permission

00:06:24.930 --> 00:06:27.640 align:middle line:84%
here, that is the
SUID permission.

00:06:27.640 --> 00:06:30.090 align:middle line:84%
So if you take a look at
the other binaries here,

00:06:30.090 --> 00:06:33.600 align:middle line:84%
they don't have the s permission
applied here, which as I said,

00:06:33.600 --> 00:06:36.810 align:middle line:84%
implies that the SUID
permission has been applied

00:06:36.810 --> 00:06:40.890 align:middle line:84%
to this particular binary, which
means it is executed with root

00:06:40.890 --> 00:06:41.890 align:middle line:90%
privileges.

00:06:41.890 --> 00:06:44.370 align:middle line:84%
So let's try and execute
the greetings binary.

00:06:44.370 --> 00:06:47.740 align:middle line:84%
So we'll say greetings, although
we actually cannot execute it.

00:06:47.740 --> 00:06:49.200 align:middle line:84%
So I'm just going
to say greetings.

00:06:49.200 --> 00:06:51.670 align:middle line:84%
And of course, we are
told permission denied.

00:06:51.670 --> 00:06:53.850 align:middle line:84%
If we try and execute
the welcome directory,

00:06:53.850 --> 00:06:55.990 align:middle line:84%
or the welcome binary
for that matter,

00:06:55.990 --> 00:06:58.570 align:middle line:84%
it'll tell us "Welcome
to Attack Defense Labs."

00:06:58.570 --> 00:07:01.440 align:middle line:84%
So again, this binary
will just set up

00:07:01.440 --> 00:07:03.480 align:middle line:84%
to demonstrate
this vulnerability.

00:07:03.480 --> 00:07:05.790 align:middle line:84%
What we can do now
is learn more about

00:07:05.790 --> 00:07:07.560 align:middle line:90%
this particular welcome binary.

00:07:07.560 --> 00:07:10.380 align:middle line:84%
And the way we can do
that is, of course,

00:07:10.380 --> 00:07:13.060 align:middle line:84%
by utilizing the
type or file command.

00:07:13.060 --> 00:07:16.680 align:middle line:84%
So again, we can essentially
just say, for example,

00:07:16.680 --> 00:07:20.280 align:middle line:84%
here we can just say
file and welcome,

00:07:20.280 --> 00:07:24.330 align:middle line:84%
and it'll tell us that this is
a standard ELF binary for Linux.

00:07:24.330 --> 00:07:26.490 align:middle line:90%
And again, it tells you--

00:07:26.490 --> 00:07:30.780 align:middle line:84%
it gives you an idea as to what
shared objects are being loaded

00:07:30.780 --> 00:07:32.280 align:middle line:90%
by this particular binary.

00:07:32.280 --> 00:07:34.830 align:middle line:84%
That is also another
alternative when it comes down

00:07:34.830 --> 00:07:38.010 align:middle line:90%
to exploiting SUID binaries.

00:07:38.010 --> 00:07:41.550 align:middle line:84%
If you can somehow find
missing shared objects,

00:07:41.550 --> 00:07:43.740 align:middle line:84%
you can essentially create
your own shared object

00:07:43.740 --> 00:07:45.720 align:middle line:90%
and get this binary to load it.

00:07:45.720 --> 00:07:47.160 align:middle line:84%
And of course,
that shared object

00:07:47.160 --> 00:07:48.840 align:middle line:84%
is going to be
malicious in nature,

00:07:48.840 --> 00:07:51.360 align:middle line:84%
or it is going to execute
malicious commands that

00:07:51.360 --> 00:07:52.680 align:middle line:90%
will elevate your session.

00:07:52.680 --> 00:07:54.870 align:middle line:84%
But in this case,
this particular binary

00:07:54.870 --> 00:07:57.670 align:middle line:84%
doesn't have any
missing shared objects.

00:07:57.670 --> 00:08:00.210 align:middle line:84%
So let's try and
identify what strings

00:08:00.210 --> 00:08:01.585 align:middle line:90%
we can find within this binary.

00:08:01.585 --> 00:08:03.210 align:middle line:84%
So the strings command
will essentially

00:08:03.210 --> 00:08:05.890 align:middle line:84%
give us a list of strings
within the binary.

00:08:05.890 --> 00:08:08.320 align:middle line:84%
So this is just basic
static analysis.

00:08:08.320 --> 00:08:10.530 align:middle line:90%
So I'll type in strings welcome.

00:08:10.530 --> 00:08:12.460 align:middle line:84%
And let's start off
from the beginning.

00:08:12.460 --> 00:08:14.700 align:middle line:84%
So you can see it
actually loads or calls

00:08:14.700 --> 00:08:19.890 align:middle line:84%
upon the shared object here and
another one right over there.

00:08:19.890 --> 00:08:23.190 align:middle line:84%
And you can see the
setuid permission.

00:08:23.190 --> 00:08:28.450 align:middle line:84%
And let's take a look at some
of the other options here.

00:08:28.450 --> 00:08:30.780 align:middle line:84%
And if we take a
look at this here,

00:08:30.780 --> 00:08:34.110 align:middle line:84%
we can see that it calls upon
the greetings binary, which is

00:08:34.110 --> 00:08:35.549 align:middle line:90%
very, very interesting, right?

00:08:35.549 --> 00:08:39.760 align:middle line:84%
So it's calling upon an external
binary, which is, as I said,

00:08:39.760 --> 00:08:40.510 align:middle line:90%
very interesting.

00:08:40.510 --> 00:08:44.130 align:middle line:84%
So what if we create or
modify the greetings binary

00:08:44.130 --> 00:08:46.920 align:middle line:84%
and we have it execute
a command like bash

00:08:46.920 --> 00:08:49.980 align:middle line:84%
or we have it execute
the bash binary.

00:08:49.980 --> 00:08:53.520 align:middle line:84%
And of course, because this
particular welcome binary

00:08:53.520 --> 00:08:56.520 align:middle line:84%
is being executed
with root privileges

00:08:56.520 --> 00:08:59.070 align:middle line:84%
because it is an
SUID binary, then it

00:08:59.070 --> 00:09:02.490 align:middle line:90%
will execute the commands or--

00:09:02.490 --> 00:09:04.680 align:middle line:84%
it will actually execute
the command specified

00:09:04.680 --> 00:09:07.210 align:middle line:90%
within the greetings binary.

00:09:07.210 --> 00:09:09.900 align:middle line:84%
So let's actually
clear out the terminal.

00:09:09.900 --> 00:09:12.720 align:middle line:84%
And we can actually get rid
of the current greetings

00:09:12.720 --> 00:09:13.980 align:middle line:90%
binary here.

00:09:13.980 --> 00:09:15.720 align:middle line:90%
And I'm just going to hit Yes.

00:09:15.720 --> 00:09:18.990 align:middle line:84%
And what we can do is we
can essentially just say--

00:09:18.990 --> 00:09:21.990 align:middle line:84%
or we can create our own
greetings binary quite

00:09:21.990 --> 00:09:24.150 align:middle line:90%
simply by saying--

00:09:24.150 --> 00:09:28.790 align:middle line:84%
we can copy bin/bash,
so essentially just

00:09:28.790 --> 00:09:30.950 align:middle line:84%
creating a copy
of bash, and we're

00:09:30.950 --> 00:09:33.260 align:middle line:90%
going to save it as greetings.

00:09:33.260 --> 00:09:37.620 align:middle line:84%
So this is essentially
a bash binary,

00:09:37.620 --> 00:09:39.050 align:middle line:90%
but it's called greetings.

00:09:39.050 --> 00:09:41.540 align:middle line:84%
Now because the
welcome binary calls

00:09:41.540 --> 00:09:44.780 align:middle line:84%
upon the greetings
binary, it'll execute bash

00:09:44.780 --> 00:09:46.820 align:middle line:84%
with root privileges,
which will consequently

00:09:46.820 --> 00:09:49.820 align:middle line:84%
provide us with a
root bash session

00:09:49.820 --> 00:09:51.200 align:middle line:90%
with elevated privileges.

00:09:51.200 --> 00:09:52.800 align:middle line:84%
So we can actually
test this out.

00:09:52.800 --> 00:09:56.580 align:middle line:84%
So if I say welcome-- if I
run the welcome binary again,

00:09:56.580 --> 00:09:58.250 align:middle line:84%
you can see that
it's going to execute

00:09:58.250 --> 00:10:01.820 align:middle line:84%
the greetings binary, which is,
in essence, just a bash binary.

00:10:01.820 --> 00:10:04.910 align:middle line:84%
And we immediately
obtain root privileges.

00:10:04.910 --> 00:10:08.180 align:middle line:84%
And if I say ID, you can see
where currently we currently

00:10:08.180 --> 00:10:09.650 align:middle line:90%
have access as the root user.

00:10:09.650 --> 00:10:11.760 align:middle line:84%
And of course I can
confirm that there.

00:10:11.760 --> 00:10:13.820 align:middle line:84%
And if I try and
execute or run commands

00:10:13.820 --> 00:10:15.860 align:middle line:84%
that require root
privileges, like the ability

00:10:15.860 --> 00:10:18.050 align:middle line:84%
to view the shadow
file, you can see

00:10:18.050 --> 00:10:20.660 align:middle line:84%
I can list out the contents
of the shadow file right

00:10:20.660 --> 00:10:21.500 align:middle line:90%
over here.

00:10:21.500 --> 00:10:25.610 align:middle line:84%
And we have successfully been
able to elevate our privileges

00:10:25.610 --> 00:10:29.490 align:middle line:84%
through the use
of an SUID binary.

00:10:29.490 --> 00:10:31.880 align:middle line:84%
Now as I said, there's
multiple misconfigurations

00:10:31.880 --> 00:10:32.810 align:middle line:90%
that you can look for.

00:10:32.810 --> 00:10:35.260 align:middle line:84%
As I said, one of
them is to obtain

00:10:35.260 --> 00:10:39.320 align:middle line:84%
missing shared objects that are
being called upon by the SUID

00:10:39.320 --> 00:10:42.450 align:middle line:84%
binary and creating
your own shared object.

00:10:42.450 --> 00:10:44.690 align:middle line:84%
And again, once the
binary is executed,

00:10:44.690 --> 00:10:46.460 align:middle line:84%
it will then find
the shared object

00:10:46.460 --> 00:10:49.790 align:middle line:84%
that it couldn't find before
and it will execute that shared

00:10:49.790 --> 00:10:52.430 align:middle line:84%
object with the malicious
comments that you

00:10:52.430 --> 00:10:54.620 align:middle line:84%
have that you've actually
entered within the shared

00:10:54.620 --> 00:10:57.440 align:middle line:84%
object file, consequently
providing you

00:10:57.440 --> 00:10:58.890 align:middle line:90%
with elevated privileges.

00:10:58.890 --> 00:11:01.460 align:middle line:84%
So that's really as simple
as it gets in regards

00:11:01.460 --> 00:11:03.860 align:middle line:90%
to exploiting SUID binaries.

00:11:03.860 --> 00:11:06.770 align:middle line:84%
This is by no means
a comprehensive view

00:11:06.770 --> 00:11:12.080 align:middle line:84%
or look at SUID binaries and
how they can be exploited.

00:11:12.080 --> 00:11:15.950 align:middle line:84%
I will definitely be exploring
all the various SUID binary

00:11:15.950 --> 00:11:19.520 align:middle line:84%
exploitation techniques in the
privileged escalation course.

00:11:19.520 --> 00:11:22.310 align:middle line:84%
All right, so this is going
to conclude-- or rather,

00:11:22.310 --> 00:11:24.830 align:middle line:84%
this is the conclusion to
the practical demonstration

00:11:24.830 --> 00:11:27.760 align:middle line:90%
side of this video.

00:11:27.760 --> 00:11:30.150 align:middle line:84%
All right, so that
is going to conclude

00:11:30.150 --> 00:11:33.970 align:middle line:84%
the Linux privileged escalation
section of this course.

00:11:33.970 --> 00:11:36.780 align:middle line:84%
We're now moving on to the final
section of this course, which

00:11:36.780 --> 00:11:40.260 align:middle line:84%
will essentially entail the
process of dumping credentials

00:11:40.260 --> 00:11:43.000 align:middle line:90%
and hashes from Linux systems.

00:11:43.000 --> 00:11:45.500 align:middle line:90%
So I'll see you there.

00:11:45.500 --> 00:11:46.000 align:middle line:90%