WEBVTT

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


00:00:04.810 --> 00:00:07.696 align:middle line:90%
[MUSIC PLAYING]

00:00:07.696 --> 00:00:10.110 align:middle line:90%


00:00:10.110 --> 00:00:13.260 align:middle line:84%
Searching for publicly
available exploits.

00:00:13.260 --> 00:00:14.880 align:middle line:84%
All right, so we've
just completed

00:00:14.880 --> 00:00:16.952 align:middle line:84%
the vulnerability
scanning and detection

00:00:16.952 --> 00:00:17.910 align:middle line:90%
section of this course.

00:00:17.910 --> 00:00:20.880 align:middle line:84%
And we've taken a look at
how to identify and scan

00:00:20.880 --> 00:00:23.850 align:middle line:84%
for vulnerabilities
on a particular target

00:00:23.850 --> 00:00:27.270 align:middle line:84%
or to identify vulnerabilities
that affect a service that's

00:00:27.270 --> 00:00:29.820 align:middle line:90%
running on a particular target.

00:00:29.820 --> 00:00:32.380 align:middle line:84%
Well, what's the next step
as a penetration test?

00:00:32.380 --> 00:00:35.160 align:middle line:84%
Well, the next step is
to find and identify

00:00:35.160 --> 00:00:37.290 align:middle line:84%
exploit code that can
be used to exploit

00:00:37.290 --> 00:00:41.490 align:middle line:84%
these vulnerabilities that we
were able to actually identify.

00:00:41.490 --> 00:00:46.170 align:middle line:84%
Now, why are we actually
making or taking

00:00:46.170 --> 00:00:48.045 align:middle line:84%
the time to make an
entire video on this--

00:00:48.045 --> 00:00:50.220 align:middle line:84%
on the process of
searching for exploits?

00:00:50.220 --> 00:00:51.640 align:middle line:84%
You might be
thinking to yourself,

00:00:51.640 --> 00:00:54.330 align:middle line:84%
well, all I need to do
is just fire up Google

00:00:54.330 --> 00:00:57.180 align:middle line:84%
and type in the name
of the service as well

00:00:57.180 --> 00:00:59.393 align:middle line:84%
as the keyword
exploit, and I'll be

00:00:59.393 --> 00:01:00.810 align:middle line:84%
able to find what
I'm looking for.

00:01:00.810 --> 00:01:03.150 align:middle line:84%
Well, there's a few
considerations to take.

00:01:03.150 --> 00:01:05.519 align:middle line:84%
And in this video, we're
going to be taking a look

00:01:05.519 --> 00:01:09.060 align:middle line:84%
at some really good exploit
databases or sources where

00:01:09.060 --> 00:01:13.110 align:middle line:84%
you can find exploits that have
been tested and/or verified.

00:01:13.110 --> 00:01:14.850 align:middle line:90%
And we'll actually get--

00:01:14.850 --> 00:01:16.950 align:middle line:84%
we'll take a look at
why that's important,

00:01:16.950 --> 00:01:21.360 align:middle line:84%
as well as we'll also be taking
a look at a few quick or really

00:01:21.360 --> 00:01:24.180 align:middle line:84%
useful tricks that
you can use whenever

00:01:24.180 --> 00:01:25.950 align:middle line:90%
you're searching for exploits.

00:01:25.950 --> 00:01:29.640 align:middle line:84%
All right, so after identifying
a potential vulnerability

00:01:29.640 --> 00:01:32.640 align:middle line:84%
within a target or a service
that's running on the target,

00:01:32.640 --> 00:01:34.590 align:middle line:84%
the next logical
step will involve

00:01:34.590 --> 00:01:36.690 align:middle line:84%
searching for exploit
code that can be used

00:01:36.690 --> 00:01:38.430 align:middle line:90%
to exploit the vulnerability.

00:01:38.430 --> 00:01:41.460 align:middle line:84%
Now, in terms of exploit
code, especially when

00:01:41.460 --> 00:01:43.530 align:middle line:84%
you're working as a
penetration tester,

00:01:43.530 --> 00:01:46.140 align:middle line:84%
there's really two
sources or two techniques.

00:01:46.140 --> 00:01:48.210 align:middle line:84%
You can look for
exploit code online,

00:01:48.210 --> 00:01:51.160 align:middle line:84%
or you can use
locally-available exploit code.

00:01:51.160 --> 00:01:53.940 align:middle line:84%
So for example, if you're
utilizing Kali Linux or Parrot

00:01:53.940 --> 00:01:58.830 align:middle line:84%
OS, you will have access to a
locally-stored exploit database

00:01:58.830 --> 00:02:01.140 align:middle line:84%
or repository in the
case of SearchSploit

00:02:01.140 --> 00:02:03.042 align:middle line:84%
or with the
Metasploit framework.

00:02:03.042 --> 00:02:04.500 align:middle line:84%
However, in this
video, we're going

00:02:04.500 --> 00:02:07.260 align:middle line:84%
to be focusing on searching
for exploits online.

00:02:07.260 --> 00:02:10.259 align:middle line:84%
Now, it's important to note
that exploit code can easily

00:02:10.259 --> 00:02:14.700 align:middle line:84%
be found online if the actual
exploit code was made available

00:02:14.700 --> 00:02:18.060 align:middle line:84%
by the exploit developer or the
individual who, essentially,

00:02:18.060 --> 00:02:20.710 align:middle line:84%
identified an exploited
the vulnerability.

00:02:20.710 --> 00:02:25.200 align:middle line:84%
However, it is important to note
that downloading and running

00:02:25.200 --> 00:02:28.938 align:middle line:84%
exploit code against a target
can be quite dangerous,

00:02:28.938 --> 00:02:30.480 align:middle line:84%
especially when
you're downloading it

00:02:30.480 --> 00:02:32.485 align:middle line:90%
from unverified sources.

00:02:32.485 --> 00:02:34.360 align:middle line:84%
Now, you might be thinking
to yourself, well,

00:02:34.360 --> 00:02:35.550 align:middle line:90%
why is it dangerous?

00:02:35.550 --> 00:02:37.440 align:middle line:84%
I mean, I'm just searching
for exploit code,

00:02:37.440 --> 00:02:38.880 align:middle line:90%
and I then run it on the target.

00:02:38.880 --> 00:02:40.560 align:middle line:84%
And it either works,
or it doesn't work.

00:02:40.560 --> 00:02:47.850 align:middle line:84%
Well, as we've seen over the
last 10, 15, 20 years, given

00:02:47.850 --> 00:02:50.700 align:middle line:84%
the fact that anyone can
set up a GitHub repository,

00:02:50.700 --> 00:02:54.210 align:middle line:84%
for example, and
then create a script,

00:02:54.210 --> 00:02:59.370 align:middle line:84%
or a Python script, a C
file, or a batch script,

00:02:59.370 --> 00:03:00.870 align:middle line:90%
they can call it an exploit.

00:03:00.870 --> 00:03:03.210 align:middle line:84%
And they can essentially
describe the fact

00:03:03.210 --> 00:03:05.320 align:middle line:84%
that it exploits a
particular vulnerability.

00:03:05.320 --> 00:03:07.860 align:middle line:84%
However, in some
cases, we have actually

00:03:07.860 --> 00:03:11.040 align:middle line:84%
seen exploit code
being weaponized.

00:03:11.040 --> 00:03:12.990 align:middle line:84%
And you might be asking
yourself, in what way?

00:03:12.990 --> 00:03:15.480 align:middle line:84%
Well, a lot of
individuals have actually

00:03:15.480 --> 00:03:18.930 align:middle line:84%
created fake or
false exploit code

00:03:18.930 --> 00:03:21.900 align:middle line:84%
that really doesn't
do what it's supposed

00:03:21.900 --> 00:03:24.420 align:middle line:84%
to be doing in regards to
exploiting a vulnerability

00:03:24.420 --> 00:03:26.410 align:middle line:90%
on a service or on a target.

00:03:26.410 --> 00:03:29.070 align:middle line:84%
Instead, what it does
is it's been set up

00:03:29.070 --> 00:03:33.330 align:middle line:84%
to, essentially, act maliciously
in that when a penetration

00:03:33.330 --> 00:03:36.360 align:middle line:84%
tester or attacker runs
the exploit code locally

00:03:36.360 --> 00:03:40.380 align:middle line:84%
on their Linux system or their
Kali Linux virtual machine,

00:03:40.380 --> 00:03:42.390 align:middle line:84%
it then performs
malicious activity,

00:03:42.390 --> 00:03:46.020 align:middle line:84%
like, for example, compromising
the actual attacker's system,

00:03:46.020 --> 00:03:49.530 align:middle line:84%
as well as deleting files
or deleting the entire file

00:03:49.530 --> 00:03:50.050 align:middle line:90%
system.

00:03:50.050 --> 00:03:52.390 align:middle line:84%
So we've actually
seen this quite a lot.

00:03:52.390 --> 00:03:54.210 align:middle line:84%
So it's very important
that you actually

00:03:54.210 --> 00:03:58.740 align:middle line:84%
get exploit code from
verifiable and vetted sources.

00:03:58.740 --> 00:04:01.590 align:middle line:84%
Because you never want
to be in a position where

00:04:01.590 --> 00:04:03.450 align:middle line:84%
you've downloaded exploit
code and you think

00:04:03.450 --> 00:04:05.867 align:middle line:84%
that it's going to work and
you run it against the target,

00:04:05.867 --> 00:04:08.790 align:middle line:84%
and it essentially wipes
your entire file system,

00:04:08.790 --> 00:04:11.710 align:middle line:84%
or even worse,
compromises your system.

00:04:11.710 --> 00:04:13.530 align:middle line:90%
So it's very important.

00:04:13.530 --> 00:04:17.250 align:middle line:84%
And it is recommended to
analyze the exploit code closely

00:04:17.250 --> 00:04:19.730 align:middle line:84%
to ensure that it
works as intended.

00:04:19.730 --> 00:04:22.230 align:middle line:84%
Now, this is something that you
will learn and become better

00:04:22.230 --> 00:04:25.320 align:middle line:84%
at as you move on or as you
progress within your pen

00:04:25.320 --> 00:04:26.400 align:middle line:90%
testing career.

00:04:26.400 --> 00:04:29.070 align:middle line:84%
And you don't really
need to be a programmer

00:04:29.070 --> 00:04:32.870 align:middle line:84%
to understand what is happening
within a particular exploit,

00:04:32.870 --> 00:04:34.830 align:middle line:90%
irregardless of the language.

00:04:34.830 --> 00:04:38.070 align:middle line:84%
You just need to understand
what's happening from a class

00:04:38.070 --> 00:04:39.690 align:middle line:90%
and function perspective.

00:04:39.690 --> 00:04:42.880 align:middle line:84%
And that is something that
you'll become better at.

00:04:42.880 --> 00:04:49.140 align:middle line:84%
So in terms of online exploit
resources or databases,

00:04:49.140 --> 00:04:52.290 align:middle line:84%
there are a handful of
legitimate and vetted exploit

00:04:52.290 --> 00:04:55.080 align:middle line:84%
databases that you
should, essentially,

00:04:55.080 --> 00:04:57.372 align:middle line:84%
be using when searching
for exploits online.

00:04:57.372 --> 00:04:58.830 align:middle line:84%
And that's exactly
what we're going

00:04:58.830 --> 00:05:02.110 align:middle line:84%
to be taking a look at during
the practical demonstration.

00:05:02.110 --> 00:05:04.810 align:middle line:84%
So a few of them that I
can state within this slide

00:05:04.810 --> 00:05:07.210 align:middle line:84%
are Exploit-DB, or
the Exploit Database,

00:05:07.210 --> 00:05:12.280 align:middle line:84%
which you should be familiar
with, if you've actually been

00:05:12.280 --> 00:05:13.720 align:middle line:90%
working within this industry.

00:05:13.720 --> 00:05:14.890 align:middle line:90%
If you've not, don't worry.

00:05:14.890 --> 00:05:16.670 align:middle line:84%
I'm going to be
explaining everything.

00:05:16.670 --> 00:05:18.010 align:middle line:90%
And then, we have Rapid7.

00:05:18.010 --> 00:05:22.090 align:middle line:84%
So now that we have an idea of
what we are going to be doing

00:05:22.090 --> 00:05:24.730 align:middle line:84%
and some very important
considerations when

00:05:24.730 --> 00:05:27.620 align:middle line:84%
it comes down to searching
for exploit code,

00:05:27.620 --> 00:05:29.860 align:middle line:84%
we can actually take a look
at some of these sources

00:05:29.860 --> 00:05:31.990 align:middle line:84%
and take a look at a
few tricks that we can

00:05:31.990 --> 00:05:33.790 align:middle line:90%
use to search for exploit code.

00:05:33.790 --> 00:05:36.233 align:middle line:84%
So this video doesn't
have a lab environment.

00:05:36.233 --> 00:05:38.650 align:middle line:84%
As I said, this is more this
is going to be really focused

00:05:38.650 --> 00:05:40.180 align:middle line:90%
on searching--

00:05:40.180 --> 00:05:43.780 align:middle line:84%
the techniques involved during
the search for exploit code,

00:05:43.780 --> 00:05:46.180 align:middle line:84%
as opposed to actually
exploiting a target.

00:05:46.180 --> 00:05:49.450 align:middle line:84%
This information will be very
useful during the black box

00:05:49.450 --> 00:05:52.450 align:middle line:84%
penetration tests that
we will be performing

00:05:52.450 --> 00:05:55.750 align:middle line:84%
during the Windows and
Linux exploitation sections

00:05:55.750 --> 00:05:56.780 align:middle line:90%
respectively.

00:05:56.780 --> 00:05:59.230 align:middle line:84%
So I'll switch over
to my Kali Linux VM,

00:05:59.230 --> 00:06:01.690 align:middle line:84%
and we can take a look
at some of these sources,

00:06:01.690 --> 00:06:04.580 align:middle line:84%
resources, databases,
as well as tools.

00:06:04.580 --> 00:06:08.820 align:middle line:84%
So I'll see you there
in a couple of seconds.

00:06:08.820 --> 00:06:11.310 align:middle line:84%
All right, so I'm back
on my Kali Linux VM,

00:06:11.310 --> 00:06:13.980 align:middle line:84%
and the first
resource or database

00:06:13.980 --> 00:06:17.310 align:middle line:84%
that we're going to be taking
a look at is Exploit-DB.

00:06:17.310 --> 00:06:20.280 align:middle line:84%
So I'm just going to open up
my browser, which is Firefox,

00:06:20.280 --> 00:06:21.960 align:middle line:84%
and we can search
for Exploit-DB.

00:06:21.960 --> 00:06:26.220 align:middle line:84%
You can just launch a search,
or just type in exploit-db.com

00:06:26.220 --> 00:06:29.160 align:middle line:90%
and hit Enter.

00:06:29.160 --> 00:06:32.070 align:middle line:84%
So we'll give this a couple
of seconds to load up.

00:06:32.070 --> 00:06:35.940 align:middle line:84%
And Exploit-DB essentially
stands for exploit database.

00:06:35.940 --> 00:06:37.960 align:middle line:84%
Now, you might be
asking yourself, well,

00:06:37.960 --> 00:06:39.360 align:middle line:90%
what is Exploit-DB?

00:06:39.360 --> 00:06:42.900 align:middle line:84%
Well, it's exactly what
its name suggests it is.

00:06:42.900 --> 00:06:46.650 align:middle line:84%
It is an online, really
comprehensive database

00:06:46.650 --> 00:06:50.100 align:middle line:84%
of free exploits or
publicly available exploits.

00:06:50.100 --> 00:06:52.620 align:middle line:84%
Right now, a few
important things

00:06:52.620 --> 00:06:55.300 align:middle line:84%
need to be taken into
consideration here.

00:06:55.300 --> 00:06:58.350 align:middle line:84%
So when I open up
Exploit-DB, you

00:06:58.350 --> 00:07:00.570 align:middle line:84%
can see that we have
a list of exploits

00:07:00.570 --> 00:07:02.170 align:middle line:90%
that have just been submitted.

00:07:02.170 --> 00:07:04.332 align:middle line:84%
And you can actually
see the date right

00:07:04.332 --> 00:07:05.790 align:middle line:84%
over here-- the
date of submission.

00:07:05.790 --> 00:07:08.160 align:middle line:84%
You have the ability to
download the exploit code.

00:07:08.160 --> 00:07:09.870 align:middle line:84%
You can also click
on it, and you

00:07:09.870 --> 00:07:12.960 align:middle line:84%
can see this additional
sorting and categorization.

00:07:12.960 --> 00:07:15.640 align:middle line:84%
You can essentially
sort through the type,

00:07:15.640 --> 00:07:19.350 align:middle line:84%
whether it's a web app exploit,
a Windows exploit, et cetera.

00:07:19.350 --> 00:07:22.000 align:middle line:84%
And that can also be
fine-tuned by, again,

00:07:22.000 --> 00:07:24.990 align:middle line:84%
taking a look at the
actual platform column.

00:07:24.990 --> 00:07:28.350 align:middle line:84%
And then, you have the author
of the actual exploit code.

00:07:28.350 --> 00:07:31.700 align:middle line:84%
And you can see that there's
quite a lot of exploits here.

00:07:31.700 --> 00:07:35.580 align:middle line:84%
So this is what-- this is
the resource that I typically

00:07:35.580 --> 00:07:38.550 align:middle line:84%
would recommend that you start
with whenever you've identified

00:07:38.550 --> 00:07:41.850 align:middle line:84%
a vulnerability or
you're trying to look

00:07:41.850 --> 00:07:45.010 align:middle line:84%
for exploits that can exploit
a particular vulnerability.

00:07:45.010 --> 00:07:48.990 align:middle line:84%
So as I said
Exploit-DB is really

00:07:48.990 --> 00:07:52.740 align:middle line:84%
the most comprehensive source
or databases of exploits.

00:07:52.740 --> 00:07:55.440 align:middle line:84%
And exploit developers
themselves actually

00:07:55.440 --> 00:07:57.840 align:middle line:90%
submit exploits to Exploit-DB.

00:07:57.840 --> 00:08:00.420 align:middle line:84%
And Exploit-DB is
actually maintained

00:08:00.420 --> 00:08:04.410 align:middle line:84%
by offensive security-- the
developers of Kali Linux.

00:08:04.410 --> 00:08:06.960 align:middle line:84%
So again, in terms
of verification--

00:08:06.960 --> 00:08:08.940 align:middle line:84%
we'll actually get into
that in a few seconds.

00:08:08.940 --> 00:08:11.940 align:middle line:84%
You can see there is a
verification filter here

00:08:11.940 --> 00:08:14.250 align:middle line:84%
that allows you to
only display exploits

00:08:14.250 --> 00:08:15.270 align:middle line:90%
that have been verified.

00:08:15.270 --> 00:08:17.740 align:middle line:84%
And that's something that's
very, very important.

00:08:17.740 --> 00:08:20.430 align:middle line:84%
Now, one of the great things
about the Exploit Database

00:08:20.430 --> 00:08:24.240 align:middle line:84%
is that whenever a malicious
user tries to upload exploit

00:08:24.240 --> 00:08:27.780 align:middle line:84%
code that is malicious
or that is fake or phony,

00:08:27.780 --> 00:08:29.970 align:middle line:84%
that exploit is
actually rejected

00:08:29.970 --> 00:08:34.320 align:middle line:84%
and/or removed later
on until it's actually

00:08:34.320 --> 00:08:35.460 align:middle line:90%
tested and vetted.

00:08:35.460 --> 00:08:38.490 align:middle line:84%
So let's take a look at
some of these filters.

00:08:38.490 --> 00:08:40.559 align:middle line:84%
So if we click on
filters here, you

00:08:40.559 --> 00:08:43.030 align:middle line:84%
can see that we
can filter by type.

00:08:43.030 --> 00:08:45.840 align:middle line:84%
So we can essentially
specify the type of exploit.

00:08:45.840 --> 00:08:48.670 align:middle line:84%
So we can say dos,
local, remote, web apps.

00:08:48.670 --> 00:08:51.180 align:middle line:84%
So if we're trying to
exploit a target remotely,

00:08:51.180 --> 00:08:53.490 align:middle line:84%
then this would typically--
the remote option

00:08:53.490 --> 00:08:56.010 align:middle line:84%
is what we would
typically be utilizing

00:08:56.010 --> 00:08:57.870 align:middle line:90%
in terms of a search filter.

00:08:57.870 --> 00:09:00.000 align:middle line:84%
If we are trying to perform
privilege escalation,

00:09:00.000 --> 00:09:03.240 align:middle line:84%
then we would typically click
on local, et cetera, et cetera.

00:09:03.240 --> 00:09:06.960 align:middle line:84%
For platform, you can
see it's sorted quite

00:09:06.960 --> 00:09:09.210 align:middle line:84%
comprehensively in terms
of the target platform.

00:09:09.210 --> 00:09:12.720 align:middle line:84%
So you can look for Linux,
Windows, Solaris, BSD, Unix,

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

00:09:13.980 --> 00:09:16.500 align:middle line:84%
And in terms of Windows,
you have the architecture

00:09:16.500 --> 00:09:18.940 align:middle line:84%
specified here, which
is an additional help.

00:09:18.940 --> 00:09:20.730 align:middle line:84%
So for example, if
I was only looking

00:09:20.730 --> 00:09:24.060 align:middle line:84%
for exploits pertinent to a
32-bit version of Windows,

00:09:24.060 --> 00:09:25.410 align:middle line:90%
I can click on that there.

00:09:25.410 --> 00:09:27.810 align:middle line:84%
It's then going to
process and sort exploit

00:09:27.810 --> 00:09:29.820 align:middle line:90%
based on that criteria.

00:09:29.820 --> 00:09:31.380 align:middle line:84%
And I'm just going
to clear that out,

00:09:31.380 --> 00:09:34.410 align:middle line:84%
because I don't need to
actually use that filter.

00:09:34.410 --> 00:09:36.510 align:middle line:84%
You can then search
for exploits released

00:09:36.510 --> 00:09:37.800 align:middle line:90%
by a particular author.

00:09:37.800 --> 00:09:39.300 align:middle line:84%
That's only useful
if you are trying

00:09:39.300 --> 00:09:42.870 align:middle line:84%
to identify whether a particular
author has improved or has

00:09:42.870 --> 00:09:46.620 align:middle line:84%
released a new exploit or an
improved version of an existing

00:09:46.620 --> 00:09:48.000 align:middle line:90%
exploit.

00:09:48.000 --> 00:09:50.730 align:middle line:84%
As for ports, if you're
looking for exploits

00:09:50.730 --> 00:09:55.290 align:middle line:84%
pertinent to a particular port,
maybe for Port 21 for FTP,

00:09:55.290 --> 00:09:57.690 align:middle line:84%
you can sort and filter
through the exploits

00:09:57.690 --> 00:10:00.990 align:middle line:84%
based on the types of
exploits-- so based

00:10:00.990 --> 00:10:03.720 align:middle line:84%
on the types of exploits
or the actual port

00:10:03.720 --> 00:10:05.530 align:middle line:84%
that they are
actually targeting.

00:10:05.530 --> 00:10:08.880 align:middle line:84%
So as I correctly
stated, Port 21 is FTP.

00:10:08.880 --> 00:10:12.540 align:middle line:84%
And as a result, it only
displays FTP exploits.

00:10:12.540 --> 00:10:15.300 align:middle line:84%
And of course, these are
sorted based on the actual FTP

00:10:15.300 --> 00:10:18.780 align:middle line:84%
version or the
actual FTP solution

00:10:18.780 --> 00:10:22.230 align:middle line:90%
that they are pertinent to.

00:10:22.230 --> 00:10:24.750 align:middle line:84%
You also have the
ability to utilize tags.

00:10:24.750 --> 00:10:26.970 align:middle line:84%
And tags essentially
allow you to specify

00:10:26.970 --> 00:10:28.680 align:middle line:90%
the type of vulnerability.

00:10:28.680 --> 00:10:33.210 align:middle line:84%
Now, this is very different
than this particular type here.

00:10:33.210 --> 00:10:35.915 align:middle line:84%
But it allows you to sort based
on the type of vulnerability.

00:10:35.915 --> 00:10:37.290 align:middle line:84%
So for example,
if you are trying

00:10:37.290 --> 00:10:40.260 align:middle line:84%
to look for a buffer
overflow exploit,

00:10:40.260 --> 00:10:43.500 align:middle line:90%
you can specify buffer overflow.

00:10:43.500 --> 00:10:44.670 align:middle line:90%
If you're looking for--

00:10:44.670 --> 00:10:47.550 align:middle line:84%
let's see if we
can find that here.

00:10:47.550 --> 00:10:50.940 align:middle line:90%
If we're looking for--

00:10:50.940 --> 00:10:52.950 align:middle line:90%
I believe-- there we are--

00:10:52.950 --> 00:10:53.907 align:middle line:90%
Metasploit framework.

00:10:53.907 --> 00:10:55.740 align:middle line:84%
If you're looking for
a Metasploit framework

00:10:55.740 --> 00:10:58.320 align:middle line:84%
exploit module, you can
click on that there.

00:10:58.320 --> 00:11:02.580 align:middle line:84%
And it's then only going to
display the actual Metasploit

00:11:02.580 --> 00:11:07.200 align:middle line:84%
framework exploit module
pertinent to the actual service

00:11:07.200 --> 00:11:10.110 align:middle line:84%
or program that's
being exploited.

00:11:10.110 --> 00:11:12.900 align:middle line:84%
So you can then click on and
exploit that interests you.

00:11:12.900 --> 00:11:15.687 align:middle line:84%
Or if you know what you're
looking for in terms

00:11:15.687 --> 00:11:17.520 align:middle line:84%
of the service that
you're trying to exploit

00:11:17.520 --> 00:11:21.390 align:middle line:84%
as well as the service version,
you can launch a direct search.

00:11:21.390 --> 00:11:26.250 align:middle line:84%
So an example of this would
be if I have identified

00:11:26.250 --> 00:11:29.190 align:middle line:84%
a service running on a
target and the service is

00:11:29.190 --> 00:11:31.860 align:middle line:90%
vsftpd 2.3.4.

00:11:31.860 --> 00:11:35.680 align:middle line:84%
Now, this is a vulnerable
version of vsftpd,

00:11:35.680 --> 00:11:38.830 align:middle line:84%
so I'm just going to use
this very basic example.

00:11:38.830 --> 00:11:43.320 align:middle line:90%
I can say, vsftpd 2.3.4.

00:11:43.320 --> 00:11:45.300 align:middle line:84%
And that is going to
give me the results.

00:11:45.300 --> 00:11:48.510 align:middle line:84%
And you can see that we
have two types of exploits,

00:11:48.510 --> 00:11:50.610 align:middle line:84%
and you also have
their dates in terms

00:11:50.610 --> 00:11:52.060 align:middle line:90%
of when they were released.

00:11:52.060 --> 00:11:53.910 align:middle line:84%
And you can see
right over here we

00:11:53.910 --> 00:11:59.400 align:middle line:84%
have vsftpd 2.3.4 backdoor
command execution.

00:11:59.400 --> 00:12:01.770 align:middle line:84%
And then you have the
Metasploit module available

00:12:01.770 --> 00:12:05.040 align:middle line:84%
that essentially does what this
exploit does but just automates

00:12:05.040 --> 00:12:07.770 align:middle line:90%
the entire exploitation process.

00:12:07.770 --> 00:12:10.262 align:middle line:84%
In terms of the type,
these are remote exploits,

00:12:10.262 --> 00:12:11.970 align:middle line:84%
which means an attacker
could potentially

00:12:11.970 --> 00:12:15.210 align:middle line:84%
gain remote access to a
target through the use

00:12:15.210 --> 00:12:16.530 align:middle line:90%
of this particular exploit.

00:12:16.530 --> 00:12:19.980 align:middle line:84%
The platform is Unix, and we
have two different authors.

00:12:19.980 --> 00:12:21.930 align:middle line:84%
One of them, of
course, is Metasploit,

00:12:21.930 --> 00:12:24.300 align:middle line:90%
which is going to be verified.

00:12:24.300 --> 00:12:27.960 align:middle line:84%
Now, again, if you
want to make sure

00:12:27.960 --> 00:12:30.450 align:middle line:84%
that you're only using
verified exploit code,

00:12:30.450 --> 00:12:32.860 align:middle line:90%
you can click on verified here.

00:12:32.860 --> 00:12:35.910 align:middle line:84%
And in that case, it will only
display verified exploit code.

00:12:35.910 --> 00:12:39.180 align:middle line:84%
Now, if you take a look at
these three columns here,

00:12:39.180 --> 00:12:42.240 align:middle line:84%
we have download exploit-- that
allows you to directly download

00:12:42.240 --> 00:12:43.320 align:middle line:90%
the exploit code.

00:12:43.320 --> 00:12:45.340 align:middle line:84%
You then have
vulnerable application.

00:12:45.340 --> 00:12:47.100 align:middle line:90%
Now, what is this used for?

00:12:47.100 --> 00:12:50.040 align:middle line:84%
Well, this is a fantastic
piece of functionality

00:12:50.040 --> 00:12:54.450 align:middle line:84%
that allows you to download the
affected version of software

00:12:54.450 --> 00:12:57.530 align:middle line:84%
or the affected
service, essentially,

00:12:57.530 --> 00:12:58.900 align:middle line:90%
for testing purposes.

00:12:58.900 --> 00:13:04.050 align:middle line:84%
So for example, if I wanted
to test out this exploit,

00:13:04.050 --> 00:13:06.930 align:middle line:84%
it provides me with the
actual affected version

00:13:06.930 --> 00:13:13.080 align:middle line:84%
of vsftpd, which in this case is
2.3.4, which I can then install

00:13:13.080 --> 00:13:15.750 align:middle line:84%
and run the exploit
code against to perform

00:13:15.750 --> 00:13:19.620 align:middle line:84%
local testing to ensure that
this particular exploit does

00:13:19.620 --> 00:13:20.190 align:middle line:90%
indeed work.

00:13:20.190 --> 00:13:23.580 align:middle line:84%
So I can click on the
actual application here.

00:13:23.580 --> 00:13:26.400 align:middle line:90%
You can see that vsftpd 2.3.4.

00:13:26.400 --> 00:13:28.950 align:middle line:84%
I can then build, and
compile it, and install it,

00:13:28.950 --> 00:13:31.060 align:middle line:84%
and I can then test
the exploit against it.

00:13:31.060 --> 00:13:35.370 align:middle line:84%
This is a fantastic resource
for beginners and anyone

00:13:35.370 --> 00:13:37.740 align:middle line:84%
who is learning about
penetration testing.

00:13:37.740 --> 00:13:40.650 align:middle line:84%
You can essentially test
out all of these exploits

00:13:40.650 --> 00:13:44.430 align:middle line:84%
by installing a vulnerable--
the actual affected version

00:13:44.430 --> 00:13:47.610 align:middle line:84%
that this exploit targets,
run the test, see if it works,

00:13:47.610 --> 00:13:50.790 align:middle line:84%
get an understanding of what's
going on, modify the exploit,

00:13:50.790 --> 00:13:54.220 align:middle line:84%
learn about it, so
on and so forth.

00:13:54.220 --> 00:13:57.150 align:middle line:84%
And of course, you have the
ability to click on Has App

00:13:57.150 --> 00:13:59.490 align:middle line:84%
to only display
the exploits that

00:13:59.490 --> 00:14:04.440 align:middle line:84%
have the actual, available,
vulnerable application.

00:14:04.440 --> 00:14:06.210 align:middle line:90%
So I can just get rid of that.

00:14:06.210 --> 00:14:08.370 align:middle line:84%
And for example, if
we were interested

00:14:08.370 --> 00:14:11.860 align:middle line:84%
in the manual exploit code
here, I can click on it.

00:14:11.860 --> 00:14:14.250 align:middle line:84%
And we'll give this
a couple of seconds.

00:14:14.250 --> 00:14:16.420 align:middle line:84%
And this is the
exploit code page.

00:14:16.420 --> 00:14:18.630 align:middle line:84%
So it will give you
a basic description.

00:14:18.630 --> 00:14:21.120 align:middle line:84%
It'll tell you whether
it's been verified

00:14:21.120 --> 00:14:22.510 align:middle line:90%
by the exploit database.

00:14:22.510 --> 00:14:25.980 align:middle line:84%
It also has a unique
exploit database ID.

00:14:25.980 --> 00:14:30.120 align:middle line:84%
This will come in handy when we
will be utilizing SearchSploit

00:14:30.120 --> 00:14:31.380 align:middle line:90%
in the next video.

00:14:31.380 --> 00:14:34.140 align:middle line:84%
You then have the ability
to view the exploit raw

00:14:34.140 --> 00:14:36.010 align:middle line:90%
or download it directly.

00:14:36.010 --> 00:14:38.430 align:middle line:84%
And again, if it does have
a vulnerable application,

00:14:38.430 --> 00:14:40.090 align:middle line:90%
it'll also be displayed here.

00:14:40.090 --> 00:14:42.720 align:middle line:84%
Now, as you can see, it
displays the exploit code here.

00:14:42.720 --> 00:14:46.950 align:middle line:84%
And you can pretty much tell
that this is a Python exploit,

00:14:46.950 --> 00:14:50.160 align:middle line:84%
as you can see the actual
environment variable

00:14:50.160 --> 00:14:52.800 align:middle line:84%
or the interpreter has
been specified there.

00:14:52.800 --> 00:14:55.440 align:middle line:84%
It gives you a description
right over here

00:14:55.440 --> 00:14:57.810 align:middle line:84%
that's pertinent to
this particular exploit,

00:14:57.810 --> 00:15:00.900 align:middle line:84%
like the CVE, where
it's been tested on,

00:15:00.900 --> 00:15:01.990 align:middle line:90%
et cetera, et cetera.

00:15:01.990 --> 00:15:04.770 align:middle line:84%
So as a penetration
tester, given the fact

00:15:04.770 --> 00:15:07.230 align:middle line:84%
that this has been
verified and we

00:15:07.230 --> 00:15:08.820 align:middle line:84%
have the exploit
code available to us,

00:15:08.820 --> 00:15:10.470 align:middle line:90%
we can click on Download.

00:15:10.470 --> 00:15:11.280 align:middle line:90%
And there we are.

00:15:11.280 --> 00:15:12.570 align:middle line:90%
It will actually give us--

00:15:12.570 --> 00:15:15.750 align:middle line:84%
the actual exploit
name will directly

00:15:15.750 --> 00:15:18.300 align:middle line:84%
correspond to the
exploit database ID.

00:15:18.300 --> 00:15:21.010 align:middle line:84%
As I said, that's something
very, very important.

00:15:21.010 --> 00:15:24.060 align:middle line:84%
So I can then save the file
and launch it or run it

00:15:24.060 --> 00:15:24.970 align:middle line:90%
against the target.

00:15:24.970 --> 00:15:27.270 align:middle line:90%
So that is the Exploit Database.

00:15:27.270 --> 00:15:30.645 align:middle line:84%
Now, the Exploit Database is not
just limited to exploits alone.

00:15:30.645 --> 00:15:35.700 align:middle line:84%
, You can see that if you
navigate to the actual sidebar

00:15:35.700 --> 00:15:38.820 align:middle line:84%
here you also have your
Google Hacking Database,

00:15:38.820 --> 00:15:44.490 align:middle line:84%
which contains a series of
Google Docs or Google search

00:15:44.490 --> 00:15:46.650 align:middle line:84%
filters that allow
you to, essentially,

00:15:46.650 --> 00:15:52.440 align:middle line:84%
search for affected websites
or services that are publicly

00:15:52.440 --> 00:15:53.430 align:middle line:90%
exposed.

00:15:53.430 --> 00:15:55.200 align:middle line:84%
But we'll not go
through this right now.

00:15:55.200 --> 00:15:58.090 align:middle line:84%
That is something that
we'll cover later on.

00:15:58.090 --> 00:16:01.173 align:middle line:84%
You can also take a look
at the SearchSploit manual

00:16:01.173 --> 00:16:01.840 align:middle line:90%
right over here.

00:16:01.840 --> 00:16:03.215 align:middle line:84%
That'll give you
an understanding

00:16:03.215 --> 00:16:04.720 align:middle line:90%
of how to use the SearchSploit.

00:16:04.720 --> 00:16:07.870 align:middle line:84%
You then have the ability to
search Exploit Database, which

00:16:07.870 --> 00:16:09.070 align:middle line:90%
we've gone through.

00:16:09.070 --> 00:16:11.512 align:middle line:84%
And you also have the
ability to submit exploits.

00:16:11.512 --> 00:16:13.720 align:middle line:84%
And of course, this is
something that you'll probably

00:16:13.720 --> 00:16:18.190 align:middle line:84%
do once you've actually
progressed with your career.

00:16:18.190 --> 00:16:19.840 align:middle line:84%
All right, so that
is how to search

00:16:19.840 --> 00:16:22.000 align:middle line:90%
for exploits on Exploit-DB.

00:16:22.000 --> 00:16:23.650 align:middle line:84%
As I said, it's
fairly simple to,

00:16:23.650 --> 00:16:26.590 align:middle line:84%
essentially, search
for and identify

00:16:26.590 --> 00:16:28.210 align:middle line:90%
what you're looking for.

00:16:28.210 --> 00:16:31.600 align:middle line:84%
One thing that I want to
cover is the actual Metasploit

00:16:31.600 --> 00:16:32.390 align:middle line:90%
module.

00:16:32.390 --> 00:16:35.962 align:middle line:84%
Now, if you are clicking on an
exploit that is a Metasploit

00:16:35.962 --> 00:16:38.170 align:middle line:84%
module, you can see that
it's going to be in the Ruby

00:16:38.170 --> 00:16:39.520 align:middle line:90%
programming language.

00:16:39.520 --> 00:16:42.190 align:middle line:84%
If it is verified,
then you don't

00:16:42.190 --> 00:16:44.560 align:middle line:84%
need to download this
Ruby file and then

00:16:44.560 --> 00:16:45.910 align:middle line:90%
load it into Metasploit.

00:16:45.910 --> 00:16:49.240 align:middle line:84%
It is already available within
the Metasploit framework.

00:16:49.240 --> 00:16:52.120 align:middle line:84%
All you need to do is just
search for the affected service

00:16:52.120 --> 00:16:55.700 align:middle line:84%
version right over here, and the
same exploit will be available.

00:16:55.700 --> 00:16:58.510 align:middle line:84%
And of course, in the
case of Metasploit,

00:16:58.510 --> 00:17:00.280 align:middle line:84%
the Metasploit
module essentially

00:17:00.280 --> 00:17:02.120 align:middle line:84%
automates the
exploitation process,

00:17:02.120 --> 00:17:04.210 align:middle line:90%
which makes it much simpler.

00:17:04.210 --> 00:17:06.369 align:middle line:90%
OK, so that is Exploit-DB.

00:17:06.369 --> 00:17:09.099 align:middle line:84%
The next resource we're are
going to be taking a look at

00:17:09.099 --> 00:17:10.569 align:middle line:90%
is Rapid7.

00:17:10.569 --> 00:17:14.109 align:middle line:84%
All right, so I'm just going to
run a Google search for Rapid7

00:17:14.109 --> 00:17:15.130 align:middle line:90%
here.

00:17:15.130 --> 00:17:19.119 align:middle line:84%
And you can see that it's
going to open up the actual--

00:17:19.119 --> 00:17:21.490 align:middle line:84%
it's going to give you a
description of the company.

00:17:21.490 --> 00:17:27.849 align:middle line:84%
Rapid7 is the company that
currently owns and maintains

00:17:27.849 --> 00:17:32.190 align:middle line:84%
the Metasploit framework-- the
Metasploit project, as it were.

00:17:32.190 --> 00:17:37.795 align:middle line:84%
So the actual Rapid7 website
is their company website.

00:17:37.795 --> 00:17:39.920 align:middle line:84%
However, you can see that
we have the Vulnerability

00:17:39.920 --> 00:17:41.550 align:middle line:90%
and Exploit Database.

00:17:41.550 --> 00:17:49.100 align:middle line:84%
So if you click on that, you
can see that rapid7.com/db.

00:17:49.100 --> 00:17:52.070 align:middle line:84%
This is the Rapid7 Vulnerability
and Exploit Database.

00:17:52.070 --> 00:17:55.190 align:middle line:84%
You have the ability to search
for a particular exploit,

00:17:55.190 --> 00:17:58.580 align:middle line:84%
and you can specify whether
you're looking for a Metasploit

00:17:58.580 --> 00:18:01.100 align:middle line:90%
module or a vulnerability.

00:18:01.100 --> 00:18:03.200 align:middle line:84%
So as you can see
right over here,

00:18:03.200 --> 00:18:06.260 align:middle line:84%
this is a curated repository
of vetted computer software

00:18:06.260 --> 00:18:09.110 align:middle line:84%
exploits and exploitable
vulnerabilities.

00:18:09.110 --> 00:18:12.890 align:middle line:84%
Technical details for over
180,000 vulnerabilities

00:18:12.890 --> 00:18:16.640 align:middle line:84%
and 4,000 exploits are available
for security professionals

00:18:16.640 --> 00:18:18.530 align:middle line:90%
and researchers to review.

00:18:18.530 --> 00:18:21.410 align:middle line:84%
These vulnerabilities are
utilized by our vulnerability

00:18:21.410 --> 00:18:23.390 align:middle line:90%
management tool, InsightVM.

00:18:23.390 --> 00:18:26.330 align:middle line:84%
The exploits are all included
in the Metasploit framework

00:18:26.330 --> 00:18:30.170 align:middle line:84%
and utilized by our penetration
testing tool, Metasploit Pro.

00:18:30.170 --> 00:18:33.470 align:middle line:84%
Our vulnerability and exploit
database is updated frequently

00:18:33.470 --> 00:18:36.968 align:middle line:84%
and contains the most
recent security research.

00:18:36.968 --> 00:18:38.510 align:middle line:84%
All right, the key
thing to note here

00:18:38.510 --> 00:18:40.550 align:middle line:84%
is that these exploits
and vulnerabilities

00:18:40.550 --> 00:18:41.690 align:middle line:90%
have been vetted.

00:18:41.690 --> 00:18:44.870 align:middle line:84%
And again, the reason why I'm
recommending or suggesting

00:18:44.870 --> 00:18:46.940 align:middle line:84%
Rapid7 is it is
probably the best

00:18:46.940 --> 00:18:51.020 align:middle line:84%
way to identify Metasploit
modules or exploits that

00:18:51.020 --> 00:18:53.600 align:middle line:84%
have been ported into
Metasploit modules,

00:18:53.600 --> 00:18:56.420 align:middle line:84%
essentially, to automate
the exploitation process.

00:18:56.420 --> 00:18:58.790 align:middle line:84%
So if you're finding
it difficult to utilize

00:18:58.790 --> 00:19:01.460 align:middle line:84%
a manual exploit,
like the Python script

00:19:01.460 --> 00:19:04.370 align:middle line:84%
that we just
explored previously,

00:19:04.370 --> 00:19:07.490 align:middle line:84%
then we can essentially look,
or essentially try and find,

00:19:07.490 --> 00:19:10.190 align:middle line:84%
whether the exploit has been
ported into a Metasploit

00:19:10.190 --> 00:19:10.920 align:middle line:90%
module.

00:19:10.920 --> 00:19:15.950 align:middle line:84%
So again, we can launch the
search vsftpd 2.3.4 here.

00:19:15.950 --> 00:19:17.450 align:middle line:84%
We'll give that a
couple of seconds.

00:19:17.450 --> 00:19:20.330 align:middle line:90%


00:19:20.330 --> 00:19:22.100 align:middle line:84%
You can see that it
returns no results.

00:19:22.100 --> 00:19:25.468 align:middle line:84%
We can fine tune
that into a module.

00:19:25.468 --> 00:19:27.260 align:middle line:84%
And in this case, you
can see that it's not

00:19:27.260 --> 00:19:28.950 align:middle line:90%
displaying anything there.

00:19:28.950 --> 00:19:31.730 align:middle line:84%
However, if we get rid of
the actual service version,

00:19:31.730 --> 00:19:33.290 align:middle line:90%
it should display some results.

00:19:33.290 --> 00:19:34.290 align:middle line:90%
There we are.

00:19:34.290 --> 00:19:36.500 align:middle line:84%
So in some cases,
you may need to be

00:19:36.500 --> 00:19:38.900 align:middle line:84%
very specific with
the actual versioning.

00:19:38.900 --> 00:19:42.230 align:middle line:84%
You may need to use the version
option there or the version

00:19:42.230 --> 00:19:43.040 align:middle line:90%
prefix.

00:19:43.040 --> 00:19:46.670 align:middle line:84%
And you can see this will
display the actual exploit

00:19:46.670 --> 00:19:47.280 align:middle line:90%
here--

00:19:47.280 --> 00:19:51.260 align:middle line:84%
so vsftpd 2.3.4 backdoor
command execution.

00:19:51.260 --> 00:19:55.460 align:middle line:84%
It was disclosed in July-
on the third of July, 2011.

00:19:55.460 --> 00:19:57.980 align:middle line:84%
And this has a
Metasploit module.

00:19:57.980 --> 00:19:59.690 align:middle line:90%
So we can click on that there.

00:19:59.690 --> 00:20:02.000 align:middle line:84%
And you can see, it
gives you a description

00:20:02.000 --> 00:20:03.410 align:middle line:90%
of the Metasploit module.

00:20:03.410 --> 00:20:05.600 align:middle line:84%
The module exploits
a malicious backdoor

00:20:05.600 --> 00:20:08.690 align:middle line:84%
that was added to the
vsftpd download archive.

00:20:08.690 --> 00:20:12.980 align:middle line:84%
This backdoor was introduced
into vsftpd 2.3.4--

00:20:12.980 --> 00:20:15.530 align:middle line:84%
the actual archive--
between the following dates.

00:20:15.530 --> 00:20:18.290 align:middle line:84%
And then, it provides you with
the actual module options,

00:20:18.290 --> 00:20:19.950 align:middle line:90%
which is extremely helpful.

00:20:19.950 --> 00:20:21.950 align:middle line:84%
So if you want to use
the Metasploit module,

00:20:21.950 --> 00:20:24.320 align:middle line:84%
it gives you the
actual module name.

00:20:24.320 --> 00:20:26.210 align:middle line:84%
It then gives you
additional information

00:20:26.210 --> 00:20:28.820 align:middle line:84%
regarding how to configure
the Metasploit module.

00:20:28.820 --> 00:20:32.000 align:middle line:84%
And right over here, exploit,
and that is pretty much it.

00:20:32.000 --> 00:20:33.590 align:middle line:84%
As I said, this is
not just limited

00:20:33.590 --> 00:20:35.240 align:middle line:90%
to this particular exploit.

00:20:35.240 --> 00:20:39.680 align:middle line:84%
You can also search for
EternalBlue, for example.

00:20:39.680 --> 00:20:40.700 align:middle line:90%
There we are.

00:20:40.700 --> 00:20:43.430 align:middle line:84%
And you can see it gives
you the various Metasploit

00:20:43.430 --> 00:20:46.160 align:middle line:84%
modules pertinent to
the EternalBlue exploit.

00:20:46.160 --> 00:20:49.730 align:middle line:84%
And again, the same thing
goes for Exploit Database.

00:20:49.730 --> 00:20:55.620 align:middle line:84%
If I was searching for
EternalBlue and I hit Enter,

00:20:55.620 --> 00:20:58.620 align:middle line:84%
you can see that it gives
me the actual EternalBlue

00:20:58.620 --> 00:20:59.760 align:middle line:90%
exploits here.

00:20:59.760 --> 00:21:03.420 align:middle line:84%
And then I can specify whether I
only want the verified exploits

00:21:03.420 --> 00:21:04.110 align:middle line:90%
there.

00:21:04.110 --> 00:21:07.080 align:middle line:84%
And you can see right
over here that these

00:21:07.080 --> 00:21:08.895 align:middle line:84%
are all the manual
exploits that you

00:21:08.895 --> 00:21:10.900 align:middle line:90%
would need to execute manually.

00:21:10.900 --> 00:21:15.490 align:middle line:84%
So for example, if I
click on this one here,

00:21:15.490 --> 00:21:16.720 align:middle line:90%
this is a Python script.

00:21:16.720 --> 00:21:18.790 align:middle line:84%
And it gives you
documentation regarding

00:21:18.790 --> 00:21:23.410 align:middle line:84%
how the exploit works and the
affected versions of Windows,

00:21:23.410 --> 00:21:25.702 align:middle line:84%
as well as where
it's been tested on.

00:21:25.702 --> 00:21:27.160 align:middle line:84%
And then, it gives
you instructions

00:21:27.160 --> 00:21:30.110 align:middle line:84%
on how to generate shellcode,
et cetera, et cetera.

00:21:30.110 --> 00:21:34.348 align:middle line:84%
So these are great resources
for looking for exploits.

00:21:34.348 --> 00:21:35.890 align:middle line:84%
Now, as I said, you
don't really need

00:21:35.890 --> 00:21:38.480 align:middle line:84%
to navigate to the
websites themselves.

00:21:38.480 --> 00:21:42.550 align:middle line:84%
You can also utilize Google
Docs to essentially fine tune

00:21:42.550 --> 00:21:44.590 align:middle line:90%
your searches with Google.

00:21:44.590 --> 00:21:49.180 align:middle line:84%
So for example, I can
essentially run the same search

00:21:49.180 --> 00:21:50.720 align:middle line:90%
from Google.

00:21:50.720 --> 00:21:54.610 align:middle line:84%
So I can-- what I'll do
here is, for example, if I'm

00:21:54.610 --> 00:21:59.560 align:middle line:84%
searching for vsftpd
2.3.4, I can hit Enter.

00:21:59.560 --> 00:22:01.490 align:middle line:84%
And that's a typical
Google search.

00:22:01.490 --> 00:22:04.780 align:middle line:84%
And you can see, already these
results pertinent to Rapid7.

00:22:04.780 --> 00:22:07.030 align:middle line:84%
And this is because
I've actually

00:22:07.030 --> 00:22:08.770 align:middle line:90%
clicked on those websites.

00:22:08.770 --> 00:22:11.740 align:middle line:84%
However, I can also
fine tune my results.

00:22:11.740 --> 00:22:14.170 align:middle line:84%
And you can go
directly and click

00:22:14.170 --> 00:22:17.170 align:middle line:84%
on exploit, Exploit-DB,
exploit GitHub, which

00:22:17.170 --> 00:22:18.100 align:middle line:90%
I don't recommend.

00:22:18.100 --> 00:22:19.900 align:middle line:84%
As a penetration tester,
you should always

00:22:19.900 --> 00:22:23.740 align:middle line:84%
be familiar with search engines
and how to essentially make

00:22:23.740 --> 00:22:27.700 align:middle line:84%
them work to what you're
looking for or make

00:22:27.700 --> 00:22:30.710 align:middle line:90%
them work exactly how you want.

00:22:30.710 --> 00:22:33.370 align:middle line:84%
And that can be done through
the use of Google Docs.

00:22:33.370 --> 00:22:36.940 align:middle line:84%
So for example, if I only wanted
to limit the results to only

00:22:36.940 --> 00:22:40.750 align:middle line:84%
show results or to only
display results pertinent

00:22:40.750 --> 00:22:44.590 align:middle line:84%
to Exploit-DB, I can use the
site search filter and say,

00:22:44.590 --> 00:22:47.170 align:middle line:84%
I only want you to show
me results pertinent

00:22:47.170 --> 00:22:49.090 align:middle line:90%
to exploit-db.com.

00:22:49.090 --> 00:22:52.270 align:middle line:84%
I hit Enter, and now it's
only going to show me results

00:22:52.270 --> 00:22:56.240 align:middle line:84%
pertinent to exploit-db.com,
which is fantastic.

00:22:56.240 --> 00:22:58.285 align:middle line:84%
So I've now narrowed
down my search.

00:22:58.285 --> 00:22:59.660 align:middle line:84%
And you can see
right at the top,

00:22:59.660 --> 00:23:03.610 align:middle line:84%
we have the exploits that
we just explored previously.

00:23:03.610 --> 00:23:06.590 align:middle line:84%
And of course, this works
for really any vulnerability.

00:23:06.590 --> 00:23:11.480 align:middle line:84%
So for example, I
can say openssh 7.2.

00:23:11.480 --> 00:23:12.500 align:middle line:90%
Hit Enter.

00:23:12.500 --> 00:23:14.420 align:middle line:84%
And you can see, we
have the username

00:23:14.420 --> 00:23:17.990 align:middle line:84%
exploit right over here, the
username enumeration exploit,

00:23:17.990 --> 00:23:20.900 align:middle line:84%
and then a few others,
like denial of service,

00:23:20.900 --> 00:23:23.120 align:middle line:84%
authenticated xauth
command injection.

00:23:23.120 --> 00:23:28.160 align:middle line:84%
And this way, I am able to find
legitimate, verified exploits

00:23:28.160 --> 00:23:31.310 align:middle line:84%
you know that I can immediately
jump into or essentially

00:23:31.310 --> 00:23:34.410 align:middle line:84%
use to essentially test
against the target.

00:23:34.410 --> 00:23:37.490 align:middle line:84%
So that is how to
use Google Docs.

00:23:37.490 --> 00:23:38.990 align:middle line:84%
And of course, I'll
not go into all

00:23:38.990 --> 00:23:41.150 align:middle line:84%
of these search filters
that you can utilize

00:23:41.150 --> 00:23:44.370 align:middle line:84%
to fine tune your
result. But for example,

00:23:44.370 --> 00:23:46.070 align:middle line:90%
if I was looking for--

00:23:46.070 --> 00:23:48.140 align:middle line:84%
and I'll just go
back a step here.

00:23:48.140 --> 00:23:50.300 align:middle line:84%
I can also do the
same for Rapid7.

00:23:50.300 --> 00:23:54.120 align:middle line:90%
So I can say rapid7.com.

00:23:54.120 --> 00:23:56.010 align:middle line:90%
Let me talk that in correctly.

00:23:56.010 --> 00:23:58.910 align:middle line:90%
That is rapid7.com.

00:23:58.910 --> 00:24:02.220 align:middle line:84%
And make sure I
correct that there.

00:24:02.220 --> 00:24:02.980 align:middle line:90%
There we are.

00:24:02.980 --> 00:24:05.140 align:middle line:84%
We also can see this
will only display

00:24:05.140 --> 00:24:07.900 align:middle line:90%
results pertinent to Rapid7.

00:24:07.900 --> 00:24:09.610 align:middle line:84%
And in this case,
you can see that this

00:24:09.610 --> 00:24:11.980 align:middle line:84%
is the first time you've
probably seen Google run out

00:24:11.980 --> 00:24:13.180 align:middle line:90%
of search results.

00:24:13.180 --> 00:24:16.180 align:middle line:84%
And that's because there really
is only one Metasploit module

00:24:16.180 --> 00:24:19.720 align:middle line:90%
pertinent to vsftpd 2.3.4.

00:24:19.720 --> 00:24:23.590 align:middle line:84%
OK, so that is how to
utilize various Google

00:24:23.590 --> 00:24:25.390 align:middle line:84%
Docs to essentially
limit your results

00:24:25.390 --> 00:24:29.890 align:middle line:84%
to the following resources
or exploit databases.

00:24:29.890 --> 00:24:33.130 align:middle line:84%
Now, as I said, you can also
search for exploits that

00:24:33.130 --> 00:24:34.390 align:middle line:90%
have been hosted on GitHub.

00:24:34.390 --> 00:24:37.120 align:middle line:90%
So I can say site github.com.

00:24:37.120 --> 00:24:39.310 align:middle line:84%
However, in this case,
you are essentially

00:24:39.310 --> 00:24:40.990 align:middle line:90%
firing a gun in the dark.

00:24:40.990 --> 00:24:47.170 align:middle line:84%
Because unless you actually
analyze the code yourself,

00:24:47.170 --> 00:24:49.010 align:middle line:84%
then you really don't
know what it's doing.

00:24:49.010 --> 00:24:51.010 align:middle line:84%
So you can see in this
case, it's very difficult

00:24:51.010 --> 00:24:53.290 align:middle line:90%
to find an actual exploit here.

00:24:53.290 --> 00:24:56.860 align:middle line:84%
But for example, if we click
on this GitHub repository,

00:24:56.860 --> 00:24:59.650 align:middle line:90%
the exploit might be legitimate.

00:24:59.650 --> 00:25:01.720 align:middle line:84%
And we can click on
the Python script here.

00:25:01.720 --> 00:25:04.780 align:middle line:84%
You then need to manually
go through it and see what

00:25:04.780 --> 00:25:07.060 align:middle line:90%
it's doing in the background--

00:25:07.060 --> 00:25:09.220 align:middle line:84%
actually see what this
code is doing in order

00:25:09.220 --> 00:25:11.530 align:middle line:84%
to verify that
this is legitimate.

00:25:11.530 --> 00:25:13.870 align:middle line:84%
And GitHub isn't a bad
source of exploits,

00:25:13.870 --> 00:25:17.140 align:middle line:84%
as you will actually see
during this course and courses

00:25:17.140 --> 00:25:18.010 align:middle line:90%
in the future.

00:25:18.010 --> 00:25:20.320 align:middle line:84%
You just need to be sure
of what you're running.

00:25:20.320 --> 00:25:23.530 align:middle line:84%
And that's something that I want
you to take into consideration

00:25:23.530 --> 00:25:25.010 align:middle line:90%
as you move forward.

00:25:25.010 --> 00:25:28.600 align:middle line:84%
Now, another website that I will
end on is called Packet Storm.

00:25:28.600 --> 00:25:32.620 align:middle line:84%
So I can just launch a
search for Packet Storm here.

00:25:32.620 --> 00:25:35.080 align:middle line:84%
Packet Storm really isn't
an exploit database.

00:25:35.080 --> 00:25:37.660 align:middle line:84%
It is an information
security website

00:25:37.660 --> 00:25:41.380 align:middle line:84%
that essentially provides you
with the latest information

00:25:41.380 --> 00:25:44.380 align:middle line:84%
pertinent to new
vulnerabilities, exploits, et

00:25:44.380 --> 00:25:44.890 align:middle line:90%
cetera.

00:25:44.890 --> 00:25:47.830 align:middle line:84%
So you can see right
over here, it's

00:25:47.830 --> 00:25:50.170 align:middle line:84%
a fairly old website
in terms of its design.

00:25:50.170 --> 00:25:53.350 align:middle line:84%
But it's extremely useful,
at least, in my experience.

00:25:53.350 --> 00:25:55.630 align:middle line:84%
So you can see right over
here, the recent files.

00:25:55.630 --> 00:25:58.400 align:middle line:84%
These are the latest
vulnerabilities.

00:25:58.400 --> 00:26:02.530 align:middle line:84%
So you can click on it here,
on this one right over here.

00:26:02.530 --> 00:26:05.020 align:middle line:84%
You can see that it provides
you with information

00:26:05.020 --> 00:26:07.420 align:middle line:90%
regarding this vulnerability.

00:26:07.420 --> 00:26:10.978 align:middle line:84%
And you can then click
on Download, for example.

00:26:10.978 --> 00:26:11.520 align:middle line:90%
There we are.

00:26:11.520 --> 00:26:14.370 align:middle line:84%
And this is just an
advisory or information

00:26:14.370 --> 00:26:15.780 align:middle line:90%
pertinent to that vulnerability.

00:26:15.780 --> 00:26:19.620 align:middle line:84%
Now, as I said, this is a great
place for penetration testers

00:26:19.620 --> 00:26:21.270 align:middle line:84%
and security
professionals if you

00:26:21.270 --> 00:26:24.600 align:middle line:84%
are trying to get the
latest news on the latest

00:26:24.600 --> 00:26:27.210 align:middle line:84%
vulnerabilities that have
just been discovered.

00:26:27.210 --> 00:26:31.380 align:middle line:84%
You can also subscribe
to the actual RSS feed.

00:26:31.380 --> 00:26:33.810 align:middle line:84%
If I click on exploits,
you can see that it now

00:26:33.810 --> 00:26:36.390 align:middle line:84%
provides you with
exploits pertinent

00:26:36.390 --> 00:26:38.520 align:middle line:90%
to particular vulnerabilities.

00:26:38.520 --> 00:26:41.040 align:middle line:84%
The only issue with
this is you really--

00:26:41.040 --> 00:26:45.000 align:middle line:84%
the actual search
filters are quite vague,

00:26:45.000 --> 00:26:48.150 align:middle line:84%
and you really can't fine
tune what you're looking for.

00:26:48.150 --> 00:26:51.630 align:middle line:84%
One of the great features about
this website is the tools.

00:26:51.630 --> 00:26:54.300 align:middle line:84%
And the Tools
section essentially

00:26:54.300 --> 00:26:56.730 align:middle line:84%
provides you with
various security tools

00:26:56.730 --> 00:27:00.380 align:middle line:84%
that you can utilize
for penetration testing.

00:27:00.380 --> 00:27:02.130 align:middle line:84%
And then, of course,
you have white papers

00:27:02.130 --> 00:27:04.650 align:middle line:84%
that explain certain
vulnerabilities

00:27:04.650 --> 00:27:07.560 align:middle line:84%
or may explain certain
exploits, which is, again,

00:27:07.560 --> 00:27:09.330 align:middle line:84%
another great place
to essentially

00:27:09.330 --> 00:27:11.940 align:middle line:84%
search for our white
papers that essentially

00:27:11.940 --> 00:27:14.460 align:middle line:84%
explain how to exploit a
particular vulnerability,

00:27:14.460 --> 00:27:15.640 align:middle line:90%
for example.

00:27:15.640 --> 00:27:18.240 align:middle line:84%
So I could search
for EternalBlue.

00:27:18.240 --> 00:27:21.120 align:middle line:84%
And I'm just using these two
examples, because they're

00:27:21.120 --> 00:27:23.050 align:middle line:90%
fairly simple to understand.

00:27:23.050 --> 00:27:27.040 align:middle line:84%
So you can see that-- let's
click on this one here.

00:27:27.040 --> 00:27:29.230 align:middle line:84%
You can see that if
we click on Download--

00:27:29.230 --> 00:27:30.930 align:middle line:84%
and I'll just show
you what this is.

00:27:30.930 --> 00:27:33.130 align:middle line:90%
This is a ZIP file.

00:27:33.130 --> 00:27:35.650 align:middle line:84%
In terms of its
description, you can

00:27:35.650 --> 00:27:39.940 align:middle line:84%
see that the EternalBlueC
is the EternalBlue suite

00:27:39.940 --> 00:27:44.740 align:middle line:84%
remade in C, which contains
or includes the MS17-010

00:27:44.740 --> 00:27:46.870 align:middle line:90%
exploit, et cetera.

00:27:46.870 --> 00:27:48.400 align:middle line:84%
And it contains
all the shellcode.

00:27:48.400 --> 00:27:50.170 align:middle line:90%
So this is an exploit here.

00:27:50.170 --> 00:27:53.710 align:middle line:84%
Now, let's take
a step back here.

00:27:53.710 --> 00:27:57.910 align:middle line:84%
And let's see this one right
over here, which is a write up.

00:27:57.910 --> 00:28:03.610 align:middle line:84%
So you can see that this is for
the actual Metasploit module.

00:28:03.610 --> 00:28:06.770 align:middle line:84%
And yeah, this is the
Metasploit module itself here.

00:28:06.770 --> 00:28:08.230 align:middle line:84%
So again, this is
another resource

00:28:08.230 --> 00:28:14.630 align:middle line:84%
that you can essentially take a
look at off if all else fails.

00:28:14.630 --> 00:28:17.830 align:middle line:84%
However, again,
Exploit-DB and Rapid7

00:28:17.830 --> 00:28:19.450 align:middle line:84%
are pretty much
the best resources

00:28:19.450 --> 00:28:21.490 align:middle line:84%
to get started
with as a beginner.

00:28:21.490 --> 00:28:23.290 align:middle line:84%
All right, so that
is going to conclude

00:28:23.290 --> 00:28:25.525 align:middle line:84%
the practical demonstration
side of this video.

00:28:25.525 --> 00:28:29.950 align:middle line:90%


00:28:29.950 --> 00:28:31.920 align:middle line:84%
In the next video,
we will be exploring

00:28:31.920 --> 00:28:35.670 align:middle line:84%
the process of searching
for locally-stored exploits

00:28:35.670 --> 00:28:38.440 align:middle line:84%
through the use of the
SearchSploit utility.

00:28:38.440 --> 00:28:40.970 align:middle line:90%
So I'll see you there.

00:28:40.970 --> 00:28:42.000 align:middle line:90%