WEBVTT

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


00:00:04.383 --> 00:00:07.792 align:middle line:90%
[THEME MUSIC]

00:00:07.792 --> 00:00:10.230 align:middle line:90%


00:00:10.230 --> 00:00:13.270 align:middle line:84%
Overview of Windows
vulnerabilities.

00:00:13.270 --> 00:00:16.710 align:middle line:84%
Now that we have an idea of what
system a host based attacks are

00:00:16.710 --> 00:00:18.660 align:middle line:84%
and why they're so
important, let's

00:00:18.660 --> 00:00:21.930 align:middle line:84%
get started with our first
operating system, which

00:00:21.930 --> 00:00:23.460 align:middle line:90%
is going to be Windows.

00:00:23.460 --> 00:00:26.490 align:middle line:84%
And before we can get started
with exploiting Windows

00:00:26.490 --> 00:00:29.310 align:middle line:84%
and taking a look at the
various vulnerabilities

00:00:29.310 --> 00:00:33.090 align:middle line:84%
that we can exploit in
order to exploit them, let's

00:00:33.090 --> 00:00:36.600 align:middle line:84%
get an overview of the various
Windows vulnerabilities

00:00:36.600 --> 00:00:42.030 align:middle line:84%
that we can exploit and just get
an idea of the overall threat

00:00:42.030 --> 00:00:45.240 align:middle line:84%
surface and how
Windows is developed

00:00:45.240 --> 00:00:48.150 align:middle line:84%
and how that development
philosophy leads

00:00:48.150 --> 00:00:54.120 align:middle line:84%
to the creation or the actual
development of new exploits.

00:00:54.120 --> 00:00:57.570 align:middle line:84%
So first things first, a
brief history of Windows

00:00:57.570 --> 00:00:58.420 align:middle line:90%
vulnerabilities.

00:00:58.420 --> 00:01:01.890 align:middle line:84%
Now, Microsoft Windows has been
around for a very long time

00:01:01.890 --> 00:01:04.860 align:middle line:84%
and it is one of
the most popular

00:01:04.860 --> 00:01:07.830 align:middle line:84%
and dominant operating systems
worldwide with a market

00:01:07.830 --> 00:01:13.380 align:middle line:84%
share of 70% and probably even
more than that as of 2021.

00:01:13.380 --> 00:01:15.600 align:middle line:84%
Now, the popularity
and deployment

00:01:15.600 --> 00:01:19.380 align:middle line:84%
of the Windows operating system
by individuals and companies

00:01:19.380 --> 00:01:22.560 align:middle line:84%
makes it a prime target for
attackers given the threat

00:01:22.560 --> 00:01:23.220 align:middle line:90%
surface.

00:01:23.220 --> 00:01:26.580 align:middle line:84%
So the rule of thumb
is that whenever

00:01:26.580 --> 00:01:30.000 align:middle line:84%
a system, service
application, or device is

00:01:30.000 --> 00:01:32.940 align:middle line:84%
used by a lot of people,
attackers will generally

00:01:32.940 --> 00:01:36.660 align:middle line:84%
speaking shift their attention
to that platform application

00:01:36.660 --> 00:01:39.870 align:middle line:84%
operating system or device
because many users are

00:01:39.870 --> 00:01:41.040 align:middle line:90%
using it.

00:01:41.040 --> 00:01:43.320 align:middle line:84%
And over the last
15 years Windows

00:01:43.320 --> 00:01:46.260 align:middle line:84%
has had its fair share of
severe vulnerabilities ranging

00:01:46.260 --> 00:01:52.860 align:middle line:84%
from MS08-067, also known
as Conflcker to MS17-010,

00:01:52.860 --> 00:01:54.510 align:middle line:90%
which is known as EternalBlue.

00:01:54.510 --> 00:01:57.240 align:middle line:84%
And, of course, these
vulnerabilities really

00:01:57.240 --> 00:02:01.890 align:middle line:84%
had a huge part to play in
the infosec or cybersecurity

00:02:01.890 --> 00:02:03.990 align:middle line:84%
industry and it
actually helped us

00:02:03.990 --> 00:02:06.180 align:middle line:84%
change the way we think
of vulnerabilities

00:02:06.180 --> 00:02:09.630 align:middle line:90%
and securing operating systems.

00:02:09.630 --> 00:02:11.940 align:middle line:84%
Now, given the
popularity of Windows,

00:02:11.940 --> 00:02:13.650 align:middle line:84%
most of these
vulnerabilities have

00:02:13.650 --> 00:02:18.030 align:middle line:84%
publicly available
accessible exploit code,

00:02:18.030 --> 00:02:20.920 align:middle line:84%
which makes them relatively
straightforward to exploit.

00:02:20.920 --> 00:02:24.510 align:middle line:84%
So again, given the popularity
of the Windows operating system

00:02:24.510 --> 00:02:27.240 align:middle line:84%
and the sheer number of
vulnerabilities as well

00:02:27.240 --> 00:02:29.970 align:middle line:84%
as the different
versions of Windows,

00:02:29.970 --> 00:02:32.430 align:middle line:84%
attackers will typically
find vulnerabilities

00:02:32.430 --> 00:02:36.000 align:middle line:84%
within the operating system and
either keep them to themselves

00:02:36.000 --> 00:02:39.360 align:middle line:84%
as zero days or they may
disclose them to Windows.

00:02:39.360 --> 00:02:42.000 align:middle line:84%
Whatever the case, most
of these vulnerabilities

00:02:42.000 --> 00:02:44.940 align:middle line:84%
can be exploited
relatively easily

00:02:44.940 --> 00:02:48.060 align:middle line:84%
through the use of publicly
available exploit code

00:02:48.060 --> 00:02:50.760 align:middle line:84%
with various resources
and proof of concepts

00:02:50.760 --> 00:02:53.190 align:middle line:84%
that explain how to exploit
these vulnerabilities.

00:02:53.190 --> 00:02:57.690 align:middle line:84%
So Windows really is the
prime target for attackers

00:02:57.690 --> 00:03:01.350 align:middle line:84%
and most of you should
already be familiar with that.

00:03:01.350 --> 00:03:05.370 align:middle line:84%
Now, in terms of
Windows vulnerabilities,

00:03:05.370 --> 00:03:08.220 align:middle line:84%
Microsoft Windows has various
operating system versions

00:03:08.220 --> 00:03:09.300 align:middle line:90%
and releases.

00:03:09.300 --> 00:03:13.500 align:middle line:84%
And what this
eventually leads to is

00:03:13.500 --> 00:03:17.310 align:middle line:84%
it actually leads to a
fragmented threat surface

00:03:17.310 --> 00:03:18.670 align:middle line:90%
in terms of vulnerability.

00:03:18.670 --> 00:03:21.600 align:middle line:84%
So an example of this
would be vulnerabilities

00:03:21.600 --> 00:03:24.930 align:middle line:84%
that exist on Windows 7 are
not present in Windows 10.

00:03:24.930 --> 00:03:28.800 align:middle line:84%
And looking deeper, companies
that have been around

00:03:28.800 --> 00:03:32.400 align:middle line:84%
for the last 10 years may
have been using Windows XP

00:03:32.400 --> 00:03:37.410 align:middle line:84%
and may not have made the
transition to Windows 7

00:03:37.410 --> 00:03:39.330 align:middle line:84%
or Windows 10 for
that matter or may

00:03:39.330 --> 00:03:41.160 align:middle line:84%
have made the
transition to Windows 7,

00:03:41.160 --> 00:03:44.970 align:middle line:84%
but not Windows 10 yet given
the nature of organizations

00:03:44.970 --> 00:03:48.210 align:middle line:84%
and the bureaucracy involved
in making a transition

00:03:48.210 --> 00:03:50.070 align:middle line:84%
or changing the versions
of software that

00:03:50.070 --> 00:03:51.990 align:middle line:90%
is being used by that company.

00:03:51.990 --> 00:03:57.090 align:middle line:84%
Now, what this means is that
companies are pretty much

00:03:57.090 --> 00:03:59.820 align:middle line:84%
going to be running the
latest version of Windows

00:03:59.820 --> 00:04:01.433 align:middle line:90%
or an older version of Windows.

00:04:01.433 --> 00:04:03.600 align:middle line:84%
And if they are running an
older version of Windows,

00:04:03.600 --> 00:04:05.267 align:middle line:84%
then they're going
to be left vulnerable

00:04:05.267 --> 00:04:07.860 align:middle line:84%
because the longer an
operating system or a product

00:04:07.860 --> 00:04:09.960 align:middle line:84%
is out there, the
more vulnerabilities

00:04:09.960 --> 00:04:12.270 align:middle line:84%
will be detected making
the company even more

00:04:12.270 --> 00:04:14.190 align:middle line:90%
vulnerable to attack.

00:04:14.190 --> 00:04:17.459 align:middle line:84%
Now, regardless of the
various versions and releases

00:04:17.459 --> 00:04:20.970 align:middle line:84%
of Windows, all of the
various versions of Windows

00:04:20.970 --> 00:04:23.100 align:middle line:84%
share the likeness
given the development

00:04:23.100 --> 00:04:26.790 align:middle line:84%
model and the philosophy
that they're built on.

00:04:26.790 --> 00:04:29.830 align:middle line:84%
So let's take a look at
this a little bit more.

00:04:29.830 --> 00:04:31.950 align:middle line:84%
So Windows operating
systems have

00:04:31.950 --> 00:04:33.450 align:middle line:84%
been developed in
the C programming

00:04:33.450 --> 00:04:34.890 align:middle line:90%
language that's not new.

00:04:34.890 --> 00:04:38.580 align:middle line:84%
Most of the operating systems
out there like Linux or any

00:04:38.580 --> 00:04:43.350 align:middle line:84%
NICs based operating system all
are built in some way or form

00:04:43.350 --> 00:04:45.690 align:middle line:90%
with C or C+.

00:04:45.690 --> 00:04:47.940 align:middle line:84%
Now what this means or
what this leads to is

00:04:47.940 --> 00:04:50.700 align:middle line:84%
it leads these operating
systems to essentially

00:04:50.700 --> 00:04:54.360 align:middle line:84%
be vulnerable to vulnerabilities
or exploits like buffer

00:04:54.360 --> 00:04:57.730 align:middle line:84%
overflows, arbitrary code,
execution et cetera, et cetera.

00:04:57.730 --> 00:04:59.850 align:middle line:84%
And that is down to the
vulnerabilities that

00:04:59.850 --> 00:05:03.250 align:middle line:84%
exist within the
programming language itself,

00:05:03.250 --> 00:05:06.250 align:middle line:84%
and we'll get to this
in a few seconds.

00:05:06.250 --> 00:05:08.530 align:middle line:84%
Secondly, by default,
Windows is not

00:05:08.530 --> 00:05:10.720 align:middle line:84%
really configured
to run securely

00:05:10.720 --> 00:05:13.030 align:middle line:84%
and requires a
proactive implementation

00:05:13.030 --> 00:05:15.610 align:middle line:84%
of security practices
in order to configure

00:05:15.610 --> 00:05:16.750 align:middle line:90%
Windows to run securely.

00:05:16.750 --> 00:05:20.830 align:middle line:84%
So when you install a fresh
new version of Windows

00:05:20.830 --> 00:05:23.440 align:middle line:84%
or, for example,
Windows 10, it's not

00:05:23.440 --> 00:05:25.930 align:middle line:84%
configured to be secure,
and that's really

00:05:25.930 --> 00:05:28.120 align:middle line:84%
not something that we
can blame Microsoft for.

00:05:28.120 --> 00:05:30.610 align:middle line:84%
That's just the nature of
the operating system given

00:05:30.610 --> 00:05:34.810 align:middle line:84%
the various use cases for
individuals, companies,

00:05:34.810 --> 00:05:37.580 align:middle line:90%
artists, architects, et cetera.

00:05:37.580 --> 00:05:40.690 align:middle line:84%
So what that means is
that by default, Windows

00:05:40.690 --> 00:05:43.690 align:middle line:84%
is vulnerable and requires
endpoint protection.

00:05:43.690 --> 00:05:46.450 align:middle line:84%
So within an
organization, companies

00:05:46.450 --> 00:05:49.360 align:middle line:84%
have to configure Windows to
run based on their own security

00:05:49.360 --> 00:05:52.550 align:middle line:84%
policies or in compliance
with the security policies.

00:05:52.550 --> 00:05:55.180 align:middle line:84%
They also need to take a
look at endpoint security.

00:05:55.180 --> 00:05:58.180 align:middle line:84%
So installing
antivirus solutions

00:05:58.180 --> 00:06:00.940 align:middle line:84%
performing patch management,
all of that stuff

00:06:00.940 --> 00:06:02.870 align:middle line:90%
has to be handled by a company.

00:06:02.870 --> 00:06:06.340 align:middle line:84%
And if it's not handled in a
systematic methodological way,

00:06:06.340 --> 00:06:09.940 align:middle line:84%
that again leaves the
door open for attackers

00:06:09.940 --> 00:06:12.160 align:middle line:84%
to exploit various
vulnerabilities that

00:06:12.160 --> 00:06:15.670 align:middle line:84%
could be inherent or caused
by misconfigurations.

00:06:15.670 --> 00:06:18.470 align:middle line:84%
So that is something that
you really need to be--

00:06:18.470 --> 00:06:21.160 align:middle line:84%
you really need to take
into consideration.

00:06:21.160 --> 00:06:23.380 align:middle line:84%
Furthermore, newly
discovered vulnerabilities

00:06:23.380 --> 00:06:26.170 align:middle line:84%
are not immediately
patched by Microsoft.

00:06:26.170 --> 00:06:28.840 align:middle line:84%
And given the fragmented
nature of Windows,

00:06:28.840 --> 00:06:30.520 align:middle line:90%
many systems are left unpatched.

00:06:30.520 --> 00:06:33.280 align:middle line:84%
So as I said, Windows
over the last 10 years

00:06:33.280 --> 00:06:35.440 align:middle line:84%
has seen three to
four major releases.

00:06:35.440 --> 00:06:41.080 align:middle line:84%
So you have had XP, Vista,
Windows 7, Windows 8.1,

00:06:41.080 --> 00:06:43.360 align:middle line:90%
Windows 10, and now Windows 11.

00:06:43.360 --> 00:06:46.660 align:middle line:84%
All of these versions are
totally different versions

00:06:46.660 --> 00:06:48.790 align:middle line:84%
and they suffer from
their own vulnerabilities,

00:06:48.790 --> 00:06:51.190 align:middle line:84%
and Microsoft is
constantly shifting

00:06:51.190 --> 00:06:54.530 align:middle line:84%
the goalposts in regards to
the latest version of Windows.

00:06:54.530 --> 00:06:57.010 align:middle line:84%
So whenever there's a
new version of Windows,

00:06:57.010 --> 00:06:59.620 align:middle line:84%
they're trying to get as
much of their customer base

00:06:59.620 --> 00:07:02.110 align:middle line:84%
onto the new version
and to actually

00:07:02.110 --> 00:07:03.320 align:middle line:90%
ditch the previous version.

00:07:03.320 --> 00:07:05.860 align:middle line:84%
But of course, as we know,
companies don't really

00:07:05.860 --> 00:07:09.220 align:middle line:84%
operate that way and changing
the version of Windows

00:07:09.220 --> 00:07:11.810 align:middle line:90%
being used is a long process.

00:07:11.810 --> 00:07:14.020 align:middle line:84%
So for example,
if companies are--

00:07:14.020 --> 00:07:16.780 align:middle line:84%
when Windows 10 was released,
companies were still

00:07:16.780 --> 00:07:18.130 align:middle line:90%
running on Windows 7.

00:07:18.130 --> 00:07:22.930 align:middle line:84%
And Windows 7 was a very old
operating system at the time

00:07:22.930 --> 00:07:26.650 align:middle line:84%
and was still being exploited
and new vulnerabilities

00:07:26.650 --> 00:07:27.850 align:middle line:90%
were still being found.

00:07:27.850 --> 00:07:31.300 align:middle line:84%
And Microsoft was very slow in
patching the vulnerabilities

00:07:31.300 --> 00:07:33.160 align:middle line:84%
on Windows 7, because
they were primarily

00:07:33.160 --> 00:07:36.370 align:middle line:84%
focused on Windows 10,
which meant that companies

00:07:36.370 --> 00:07:41.090 align:middle line:84%
were left vulnerable and had to
implement patches themselves.

00:07:41.090 --> 00:07:47.650 align:middle line:84%
So this fragmented nature
of Windows as well as

00:07:47.650 --> 00:07:53.660 align:middle line:84%
Microsoft's policy or the actual
viewpoint on patching really,

00:07:53.660 --> 00:07:55.180 align:middle line:90%
really causes a lot of issues.

00:07:55.180 --> 00:07:58.480 align:middle line:84%
And around the
world, you still have

00:07:58.480 --> 00:08:00.830 align:middle line:84%
companies running
Windows 7, some are still

00:08:00.830 --> 00:08:02.230 align:middle line:90%
even running Windows XP.

00:08:02.230 --> 00:08:04.540 align:middle line:84%
And in the context
of Windows Server,

00:08:04.540 --> 00:08:07.750 align:middle line:84%
many companies are still
running Windows Server 2012,

00:08:07.750 --> 00:08:12.040 align:middle line:84%
which is a largely vulnerable
if not patched correctly.

00:08:12.040 --> 00:08:14.620 align:middle line:84%
And also I've seen a lot
of companies still running

00:08:14.620 --> 00:08:15.910 align:middle line:90%
Windows Server 2008.

00:08:15.910 --> 00:08:19.990 align:middle line:84%
So that's one of the
biggest issues with Windows

00:08:19.990 --> 00:08:23.140 align:middle line:84%
is the fragmentation of
the actual deployment

00:08:23.140 --> 00:08:25.510 align:middle line:84%
of the operating system
and the fact that older

00:08:25.510 --> 00:08:29.530 align:middle line:84%
versions of Windows are
still running out there.

00:08:29.530 --> 00:08:33.580 align:middle line:84%
Now, let's explore
this a little bit more.

00:08:33.580 --> 00:08:37.539 align:middle line:84%
Given the frequent releases of
the new versions of Windows,

00:08:37.539 --> 00:08:39.309 align:middle line:84%
this is also a
contributing factor

00:08:39.309 --> 00:08:43.150 align:middle line:84%
to exploitation or the
actual threat surface

00:08:43.150 --> 00:08:47.500 align:middle line:84%
that Windows operating systems
face as many companies take

00:08:47.500 --> 00:08:50.110 align:middle line:84%
a substantial length
of time to upgrade

00:08:50.110 --> 00:08:52.090 align:middle line:84%
their systems to the
latest version of Windows

00:08:52.090 --> 00:08:53.710 align:middle line:84%
and opt to use
older versions that

00:08:53.710 --> 00:08:56.600 align:middle line:84%
may be affected by an increasing
number of vulnerabilities.

00:08:56.600 --> 00:08:57.970 align:middle line:90%
I've already mentioned this.

00:08:57.970 --> 00:09:00.310 align:middle line:84%
So companies still
using older versions

00:09:00.310 --> 00:09:02.770 align:middle line:84%
and newer vulnerabilities being
discovered for those older

00:09:02.770 --> 00:09:07.070 align:middle line:84%
versions, and that leaves
them open to attack.

00:09:07.070 --> 00:09:08.980 align:middle line:84%
In addition to inherent
vulnerabilities,

00:09:08.980 --> 00:09:12.530 align:middle line:84%
Windows is also vulnerable to
cross-platform vulnerabilities,

00:09:12.530 --> 00:09:14.090 align:middle line:90%
for example, SQL injection.

00:09:14.090 --> 00:09:16.480 align:middle line:84%
So if you have a Windows
system or Windows

00:09:16.480 --> 00:09:19.240 align:middle line:84%
Server running
the Microsoft IIS,

00:09:19.240 --> 00:09:22.150 align:middle line:84%
a web server and you're hosting
a web application on that web

00:09:22.150 --> 00:09:25.540 align:middle line:84%
server, that web server
or that web application

00:09:25.540 --> 00:09:28.780 align:middle line:84%
is still vulnerable to
cross-platform vulnerabilities

00:09:28.780 --> 00:09:31.910 align:middle line:84%
like SQL injection, cross-site
scripting, et cetera, et

00:09:31.910 --> 00:09:32.410 align:middle line:90%
cetera.

00:09:32.410 --> 00:09:35.710 align:middle line:84%
So that also needs to be
taken into consideration.

00:09:35.710 --> 00:09:38.200 align:middle line:84%
Now, systems or hosts
that are running Windows

00:09:38.200 --> 00:09:40.090 align:middle line:84%
are also vulnerable
to physical attacks.

00:09:40.090 --> 00:09:41.590 align:middle line:84%
And this is something
that will not

00:09:41.590 --> 00:09:43.900 align:middle line:84%
be covering because
of the variability

00:09:43.900 --> 00:09:45.700 align:middle line:90%
of the attacks available.

00:09:45.700 --> 00:09:47.350 align:middle line:84%
And the types of
physical attacks

00:09:47.350 --> 00:09:50.590 align:middle line:84%
range from theft of
the system itself,

00:09:50.590 --> 00:09:54.220 align:middle line:84%
malicious peripheral
devices like USB drives

00:09:54.220 --> 00:09:57.280 align:middle line:84%
with malware on
them or USB drives

00:09:57.280 --> 00:09:59.530 align:middle line:84%
that have been configured
to run as key loggers.

00:09:59.530 --> 00:10:02.560 align:middle line:84%
So when it comes down to
host based security or system

00:10:02.560 --> 00:10:05.270 align:middle line:84%
and host a security,
you need to take

00:10:05.270 --> 00:10:07.550 align:middle line:84%
in a holistic view of
the vulnerabilities

00:10:07.550 --> 00:10:09.290 align:middle line:84%
and physical security
is definitely

00:10:09.290 --> 00:10:11.540 align:middle line:90%
one of the key elements of this.

00:10:11.540 --> 00:10:14.120 align:middle line:84%
And, of course, that comes
into the whole aspect

00:10:14.120 --> 00:10:16.010 align:middle line:84%
of physical penetration
testing, which

00:10:16.010 --> 00:10:18.200 align:middle line:84%
we'll not be touching
upon, but it's still

00:10:18.200 --> 00:10:20.540 align:middle line:90%
very, very important.

00:10:20.540 --> 00:10:22.760 align:middle line:84%
As for the various
types of Windows

00:10:22.760 --> 00:10:24.710 align:middle line:84%
vulnerabilities out
there, they are typically

00:10:24.710 --> 00:10:27.240 align:middle line:84%
classified into the following
categories and, of course,

00:10:27.240 --> 00:10:30.830 align:middle line:84%
this is not an exhaustive
list of the different types

00:10:30.830 --> 00:10:33.170 align:middle line:84%
of vulnerabilities
that affect Windows.

00:10:33.170 --> 00:10:35.510 align:middle line:84%
In this case, it's going
to be the vulnerabilities

00:10:35.510 --> 00:10:37.170 align:middle line:90%
that we'll be focusing on.

00:10:37.170 --> 00:10:39.680 align:middle line:84%
So firstly, we have
information disclosure.

00:10:39.680 --> 00:10:41.360 align:middle line:84%
Information disclosure
is essentially

00:10:41.360 --> 00:10:43.580 align:middle line:84%
a vulnerability that
allows an attacker

00:10:43.580 --> 00:10:47.030 align:middle line:84%
to access confidential data
or data that they should not

00:10:47.030 --> 00:10:50.930 align:middle line:84%
be able to access, and
that is quite frequent

00:10:50.930 --> 00:10:54.350 align:middle line:84%
and may not lead
directly to exploitation,

00:10:54.350 --> 00:10:57.740 align:middle line:84%
but it is still a compromise
of the company's security

00:10:57.740 --> 00:11:00.710 align:middle line:84%
or that particular
system or host security.

00:11:00.710 --> 00:11:03.680 align:middle line:84%
We then have both buffer
overflows, which most of you

00:11:03.680 --> 00:11:05.402 align:middle line:90%
should be familiar with.

00:11:05.402 --> 00:11:06.860 align:middle line:84%
These vulnerabilities
are typically

00:11:06.860 --> 00:11:10.250 align:middle line:84%
caused by a programming
error that essentially allows

00:11:10.250 --> 00:11:12.960 align:middle line:84%
an attacker to write
data to a buffer

00:11:12.960 --> 00:11:16.130 align:middle line:84%
and overrun the allocated
buffer consequently writing data

00:11:16.130 --> 00:11:17.475 align:middle line:90%
to allocated memory addresses.

00:11:17.475 --> 00:11:19.850 align:middle line:84%
And, of course, the data that
they're going to be writing

00:11:19.850 --> 00:11:20.990 align:middle line:90%
is malicious.

00:11:20.990 --> 00:11:23.660 align:middle line:84%
And once they overrun
an allocated buffer,

00:11:23.660 --> 00:11:27.800 align:middle line:84%
they are writing it to memory
addresses or allocated memory

00:11:27.800 --> 00:11:29.930 align:middle line:84%
addresses for
other applications.

00:11:29.930 --> 00:11:33.830 align:middle line:84%
And if executed-- if this
malicious code is executed,

00:11:33.830 --> 00:11:36.530 align:middle line:84%
it could give them
remote access or it

00:11:36.530 --> 00:11:40.430 align:middle line:84%
could be used to execute
malicious code that

00:11:40.430 --> 00:11:43.490 align:middle line:84%
could be used to perform a
plethora of functionality

00:11:43.490 --> 00:11:48.060 align:middle line:84%
like executing or downloading
malware so on and so forth.

00:11:48.060 --> 00:11:49.923 align:middle line:84%
We then have remote
code execution,

00:11:49.923 --> 00:11:51.590 align:middle line:84%
and this is rather
simple to understand.

00:11:51.590 --> 00:11:54.680 align:middle line:84%
This is a vulnerability that
allows an attacker to remotely

00:11:54.680 --> 00:11:56.240 align:middle line:90%
execute on the target system.

00:11:56.240 --> 00:11:57.860 align:middle line:84%
And of course,
we'll be exploring

00:11:57.860 --> 00:12:00.830 align:middle line:84%
the various ways that this
has been achieved previously

00:12:00.830 --> 00:12:02.690 align:middle line:84%
and the various
protocols that have

00:12:02.690 --> 00:12:05.120 align:middle line:84%
been used to facilitate
this type of vulnerability

00:12:05.120 --> 00:12:06.080 align:middle line:90%
or attack.

00:12:06.080 --> 00:12:09.120 align:middle line:84%
We then have privilege
escalation vulnerabilities,

00:12:09.120 --> 00:12:11.150 align:middle line:84%
and this is essentially
a vulnerability

00:12:11.150 --> 00:12:13.310 align:middle line:84%
as we already know
that allows an attacker

00:12:13.310 --> 00:12:16.430 align:middle line:84%
to elevate their privileges
after initial compromise.

00:12:16.430 --> 00:12:19.550 align:middle line:84%
And there are various ways that
this can be done, most of which

00:12:19.550 --> 00:12:23.420 align:middle line:84%
that we'll be exploring will
tie into the actual core

00:12:23.420 --> 00:12:27.440 align:middle line:84%
of the Windows operating
system and misconfigurations or

00:12:27.440 --> 00:12:28.970 align:middle line:90%
inherent vulnerabilities.

00:12:28.970 --> 00:12:32.210 align:middle line:84%
We then have denial of
service right or DOS attacks,

00:12:32.210 --> 00:12:35.240 align:middle line:84%
and this is, of course,
different to the distributed

00:12:35.240 --> 00:12:36.620 align:middle line:90%
denial of service attacks.

00:12:36.620 --> 00:12:38.750 align:middle line:84%
In the case of a denial
of service attacks,

00:12:38.750 --> 00:12:40.280 align:middle line:84%
this is essentially
a vulnerability

00:12:40.280 --> 00:12:43.340 align:middle line:84%
that allows an
attacker to consume

00:12:43.340 --> 00:12:45.350 align:middle line:90%
a system of hosts resources.

00:12:45.350 --> 00:12:48.110 align:middle line:84%
And the resources
I'm referring to here

00:12:48.110 --> 00:12:53.630 align:middle line:84%
are CPU resources or CPU
usage, RAM, network consumption

00:12:53.630 --> 00:12:54.500 align:middle line:90%
cetera.

00:12:54.500 --> 00:12:59.540 align:middle line:84%
This consequently
prevents the system

00:12:59.540 --> 00:13:02.330 align:middle line:90%
from functioning normally.

00:13:02.330 --> 00:13:08.210 align:middle line:84%
So an example of this would be a
simple denial of service attack

00:13:08.210 --> 00:13:10.490 align:middle line:84%
that essentially
prevents a web server

00:13:10.490 --> 00:13:13.580 align:middle line:84%
or consumes all the
resources on a system

00:13:13.580 --> 00:13:16.640 align:middle line:84%
and prevents a web server
from essentially serving

00:13:16.640 --> 00:13:18.590 align:middle line:84%
requests or
responding to requests

00:13:18.590 --> 00:13:20.510 align:middle line:90%
from legitimate customers.

00:13:20.510 --> 00:13:24.260 align:middle line:84%
And, of course, that is really
not something that is good.

00:13:24.260 --> 00:13:27.890 align:middle line:84%
So we really will
not be focusing

00:13:27.890 --> 00:13:30.350 align:middle line:84%
on denial of service
vulnerabilities and attacks,

00:13:30.350 --> 00:13:34.220 align:middle line:84%
because we are primarily
interested in gaining access,

00:13:34.220 --> 00:13:37.440 align:middle line:84%
elevating privileges,
so on and so forth.

00:13:37.440 --> 00:13:40.160 align:middle line:84%
That being said, that is
going to conclude this video.

00:13:40.160 --> 00:13:41.660 align:middle line:84%
In the next video,
we'll take a look

00:13:41.660 --> 00:13:44.390 align:middle line:84%
at some of the frequently
exploited Windows features

00:13:44.390 --> 00:13:46.010 align:middle line:90%
as well as services.

00:13:46.010 --> 00:13:47.570 align:middle line:84%
And then after
we've explored that,

00:13:47.570 --> 00:13:49.850 align:middle line:84%
we'll then move on to
the next section that

00:13:49.850 --> 00:13:52.370 align:middle line:84%
will cover the actual
exploitation of these features

00:13:52.370 --> 00:13:53.370 align:middle line:90%
and services.

00:13:53.370 --> 00:13:55.310 align:middle line:84%
So that's going to
be it for this video,

00:13:55.310 --> 00:13:58.670 align:middle line:84%
and I'll be seeing
you in the next video.

00:13:58.670 --> 00:13:59.170 align:middle line:90%