WEBVTT

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


00:00:04.365 --> 00:00:07.760 align:middle line:90%
[MUSIC PLAYING]

00:00:07.760 --> 00:00:09.977 align:middle line:90%


00:00:09.977 --> 00:00:12.060 align:middle line:84%
In this lab, we're going
to put what we've learned

00:00:12.060 --> 00:00:13.410 align:middle line:90%
into a little bit of practice.

00:00:13.410 --> 00:00:15.960 align:middle line:84%
We're going to find
a service and check

00:00:15.960 --> 00:00:17.250 align:middle line:90%
for our vulnerability.

00:00:17.250 --> 00:00:20.460 align:middle line:84%
And then from there, we're going
to actually try exploiting it

00:00:20.460 --> 00:00:21.990 align:middle line:90%
based on what we find.

00:00:21.990 --> 00:00:26.430 align:middle line:84%
So let's jump into our
environment and give it a look.

00:00:26.430 --> 00:00:30.900 align:middle line:84%
Ran an Nmap scan with service
enumeration on our target IP.

00:00:30.900 --> 00:00:32.910 align:middle line:90%
And what we came across--

00:00:32.910 --> 00:00:33.660 align:middle line:90%
start at the top.

00:00:33.660 --> 00:00:35.550 align:middle line:90%
First port-- port 80/tcp.

00:00:35.550 --> 00:00:42.300 align:middle line:84%
It's plain old HTTP, and
it's running on BadBlue 2.7.

00:00:42.300 --> 00:00:44.370 align:middle line:84%
The rest of this
looks to be Windows,

00:00:44.370 --> 00:00:50.550 align:middle line:84%
and it says it's a Windows
Server 2008 R2 to 2012.

00:00:50.550 --> 00:00:52.860 align:middle line:84%
And that's probably
fairly accurate.

00:00:52.860 --> 00:00:54.910 align:middle line:84%
We could get into
that more if we want,

00:00:54.910 --> 00:00:57.420 align:middle line:84%
but let's find out
about this BadBlue.

00:00:57.420 --> 00:01:00.300 align:middle line:84%
Going to the IP address,
looks like it automatically

00:01:00.300 --> 00:01:03.520 align:middle line:90%
loaded some information for us.

00:01:03.520 --> 00:01:04.709 align:middle line:90%
But this is a BadBlue.

00:01:04.709 --> 00:01:08.130 align:middle line:90%
Looks to be a file server.

00:01:08.130 --> 00:01:10.500 align:middle line:90%
And you can upload files.

00:01:10.500 --> 00:01:12.210 align:middle line:84%
Or there's this query
area right here.

00:01:12.210 --> 00:01:15.040 align:middle line:90%


00:01:15.040 --> 00:01:17.560 align:middle line:84%
All right, this looks like
it could be something.

00:01:17.560 --> 00:01:19.570 align:middle line:84%
What do we do if we want
to research something?

00:01:19.570 --> 00:01:23.320 align:middle line:84%
Well it's 2022 now,
so we go to Google.

00:01:23.320 --> 00:01:33.550 align:middle line:90%


00:01:33.550 --> 00:01:37.000 align:middle line:84%
Looking at BadBlue
2.7 for CVEs, we

00:01:37.000 --> 00:01:44.840 align:middle line:84%
can come across the
missed page for it.

00:01:44.840 --> 00:01:51.950 align:middle line:84%
And there we are,
CVE-2007-6377 details.

00:01:51.950 --> 00:01:55.160 align:middle line:84%
And it looks like there is a
stack-based buffer overflow

00:01:55.160 --> 00:02:02.150 align:middle line:84%
in the PassThru functionality
in ext.dll and BadBlue 2.72b

00:02:02.150 --> 00:02:04.250 align:middle line:90%
and earlier.

00:02:04.250 --> 00:02:07.160 align:middle line:84%
Allows remote attackers
to execute arbitrary code

00:02:07.160 --> 00:02:10.740 align:middle line:90%
via a long query string.

00:02:10.740 --> 00:02:13.220 align:middle line:84%
Now, some of that might
not make a ton of sense

00:02:13.220 --> 00:02:16.520 align:middle line:84%
to you right now, being that
this is a junior penetration

00:02:16.520 --> 00:02:21.890 align:middle line:84%
test course, but
what we do understand

00:02:21.890 --> 00:02:26.090 align:middle line:84%
there is we can run arbitrary
code in old versions

00:02:26.090 --> 00:02:29.180 align:middle line:84%
of the software, software
that we are currently

00:02:29.180 --> 00:02:31.640 align:middle line:90%
running on our target machine.

00:02:31.640 --> 00:02:33.800 align:middle line:90%
Well, that seems neat.

00:02:33.800 --> 00:02:36.350 align:middle line:90%


00:02:36.350 --> 00:02:38.450 align:middle line:84%
Anything else in here that
we need to know about?

00:02:38.450 --> 00:02:41.110 align:middle line:90%


00:02:41.110 --> 00:02:48.090 align:middle line:84%
We could get into the
AltaVista Advisory,

00:02:48.090 --> 00:02:52.660 align:middle line:90%
and that's just the exploit.

00:02:52.660 --> 00:02:55.670 align:middle line:90%


00:02:55.670 --> 00:02:58.090 align:middle line:90%
Get into the actual advisory.

00:02:58.090 --> 00:03:00.700 align:middle line:90%


00:03:00.700 --> 00:03:02.590 align:middle line:90%
And that is an old page.

00:03:02.590 --> 00:03:08.510 align:middle line:90%


00:03:08.510 --> 00:03:10.600 align:middle line:84%
Looks like this
information is so old,

00:03:10.600 --> 00:03:13.450 align:middle line:84%
we're not going to get
anything great in here.

00:03:13.450 --> 00:03:16.090 align:middle line:84%
Any extra in the
analysis description?

00:03:16.090 --> 00:03:17.290 align:middle line:90%
No.

00:03:17.290 --> 00:03:22.540 align:middle line:84%
Basically, old versions
of BadBlue 2.7 and earlier

00:03:22.540 --> 00:03:25.540 align:middle line:90%
have this problem.

00:03:25.540 --> 00:03:29.140 align:middle line:84%
There might be new
versions of BadBlue,

00:03:29.140 --> 00:03:31.870 align:middle line:84%
or there might be other ways
of serving up these files,

00:03:31.870 --> 00:03:34.610 align:middle line:84%
but in order to fully
understand this,

00:03:34.610 --> 00:03:38.710 align:middle line:84%
let's go investigate
a little further.

00:03:38.710 --> 00:03:41.590 align:middle line:84%
Might have seen I clicked over,
and that took us to an exploit.

00:03:41.590 --> 00:03:43.570 align:middle line:84%
It might not have
made a lot of sense.

00:03:43.570 --> 00:03:47.920 align:middle line:84%
Here is exploit-db
with an exploit for it.

00:03:47.920 --> 00:03:51.610 align:middle line:84%
And let's navigate
there ourselves.

00:03:51.610 --> 00:03:54.580 align:middle line:84%
This is exploit-db,
exploit database,

00:03:54.580 --> 00:04:00.340 align:middle line:84%
and it's managed by our
friends at Offensive Security.

00:04:00.340 --> 00:04:05.050 align:middle line:84%
But anyone can upload
their proof of concepts,

00:04:05.050 --> 00:04:10.180 align:middle line:84%
their exploits here, and the
community can then utilize them

00:04:10.180 --> 00:04:14.950 align:middle line:84%
after they've been verified
or at least submitted

00:04:14.950 --> 00:04:17.230 align:middle line:90%
into the database.

00:04:17.230 --> 00:04:19.390 align:middle line:84%
How it works-- we have
a search bar over here.

00:04:19.390 --> 00:04:22.060 align:middle line:84%
There's some
functionality over here.

00:04:22.060 --> 00:04:24.700 align:middle line:84%
There's papers, which
are helpful, shellcode,

00:04:24.700 --> 00:04:25.750 align:middle line:90%
which is great.

00:04:25.750 --> 00:04:28.150 align:middle line:84%
What I'm going to do is just
start with what we know,

00:04:28.150 --> 00:04:30.130 align:middle line:90%
BadBlue.

00:04:30.130 --> 00:04:32.140 align:middle line:90%
And it will update as we go.

00:04:32.140 --> 00:04:34.270 align:middle line:84%
Ooh, looks like they're
even older versions.

00:04:34.270 --> 00:04:40.930 align:middle line:84%
2.7 because that's what
our machine says, is 2.7.

00:04:40.930 --> 00:04:42.600 align:middle line:90%
Looks to be a denial of service.

00:04:42.600 --> 00:04:45.910 align:middle line:84%
OK, that's not going to help
us, but it's good to note.

00:04:45.910 --> 00:04:49.300 align:middle line:90%
It's also for 1.2.7.

00:04:49.300 --> 00:04:51.880 align:middle line:84%
Same with this full
path disclosure.

00:04:51.880 --> 00:04:56.650 align:middle line:84%
It's 1.2.7, so probably
not super helpful.

00:04:56.650 --> 00:04:59.350 align:middle line:90%
2.7.2, PassThru Buffer Overflow.

00:04:59.350 --> 00:05:06.580 align:middle line:84%
This one's for Metasploit
here is a non Metasploit let's

00:05:06.580 --> 00:05:12.160 align:middle line:84%
jump into that one and see if
there is notes in the code.

00:05:12.160 --> 00:05:14.320 align:middle line:84%
So your submissions to
ExploitDB look like this.

00:05:14.320 --> 00:05:17.530 align:middle line:84%
Each has an ID, the CVE
that it's related to,

00:05:17.530 --> 00:05:19.120 align:middle line:90%
the author for attribution.

00:05:19.120 --> 00:05:20.620 align:middle line:90%
See what else they've made.

00:05:20.620 --> 00:05:22.750 align:middle line:90%
What type of code is it?

00:05:22.750 --> 00:05:24.650 align:middle line:90%
It's remote in this case.

00:05:24.650 --> 00:05:26.620 align:middle line:90%
What platform does it apply to?

00:05:26.620 --> 00:05:29.590 align:middle line:84%
And then you can download
the Vulnerable app,

00:05:29.590 --> 00:05:30.850 align:middle line:90%
if you really want.

00:05:30.850 --> 00:05:32.920 align:middle line:84%
You can get the
code, see it raw.

00:05:32.920 --> 00:05:33.730 align:middle line:90%
This is the code.

00:05:33.730 --> 00:05:37.090 align:middle line:90%


00:05:37.090 --> 00:05:41.080 align:middle line:84%
[? Straight. ?] And this
one is a Perl script.

00:05:41.080 --> 00:05:43.660 align:middle line:84%
If you don't know
Perl, that's fine.

00:05:43.660 --> 00:05:46.840 align:middle line:84%
I don't know Perl either,
but it's written in English,

00:05:46.840 --> 00:05:51.930 align:middle line:84%
and if you've seen one
scripting language,

00:05:51.930 --> 00:05:54.720 align:middle line:90%
you've probably seen them all.

00:05:54.720 --> 00:05:57.360 align:middle line:84%
Let's just try to make a
little bit of sense out of it.

00:05:57.360 --> 00:06:01.380 align:middle line:84%
Usually, things start with a
pound sign, hashtag, are just

00:06:01.380 --> 00:06:02.790 align:middle line:90%
comments.

00:06:02.790 --> 00:06:04.170 align:middle line:90%
We've got an if statement.

00:06:04.170 --> 00:06:07.320 align:middle line:84%
It looks to see if it
has arguments past.

00:06:07.320 --> 00:06:10.660 align:middle line:84%
It's going to say, hey, this
is the usage, which is nice.

00:06:10.660 --> 00:06:12.420 align:middle line:90%
It tells you how to use it.

00:06:12.420 --> 00:06:17.760 align:middle line:84%
If you just type the exploit,
I guess, or Perl and this file,

00:06:17.760 --> 00:06:20.230 align:middle line:84%
and you don't give an extra
argument, then it tells you,

00:06:20.230 --> 00:06:23.460 align:middle line:84%
hey, you need to have
a victim and a port.

00:06:23.460 --> 00:06:25.170 align:middle line:90%
OK, that makes sense.

00:06:25.170 --> 00:06:29.820 align:middle line:84%
Probably our victim IP
number, n port 80 in our case.

00:06:29.820 --> 00:06:33.360 align:middle line:84%
There's this
Metasploit Win32 bind,

00:06:33.360 --> 00:06:42.160 align:middle line:84%
and, OK, looks like they
used an LPORT of 4444,

00:06:42.160 --> 00:06:47.350 align:middle line:84%
size of 709, this PaxAlphaNum
encoder, and the exit function

00:06:47.350 --> 00:06:48.400 align:middle line:90%
is SEH.

00:06:48.400 --> 00:06:55.180 align:middle line:84%
To create this shellcode,
this is in hexadecimal.

00:06:55.180 --> 00:06:58.120 align:middle line:84%
We'll get into hexadecimal and
a lot more of the scripting

00:06:58.120 --> 00:06:59.600 align:middle line:90%
in a later course.

00:06:59.600 --> 00:07:04.090 align:middle line:84%
But we're just trying
to see what's here.

00:07:04.090 --> 00:07:05.560 align:middle line:90%
OK, it said we needed a victim.

00:07:05.560 --> 00:07:08.590 align:middle line:84%
This looks to be a variable
with that dollar sign

00:07:08.590 --> 00:07:12.430 align:middle line:84%
out in front, Java,
and Perl, I guess.

00:07:12.430 --> 00:07:16.080 align:middle line:90%
Both use that dollar sign.

00:07:16.080 --> 00:07:19.230 align:middle line:84%
And it connects a
socket over INET,

00:07:19.230 --> 00:07:22.650 align:middle line:84%
so it's just going to
connect to that IP address.

00:07:22.650 --> 00:07:29.270 align:middle line:84%
Over TCP, utilizing
our arguments.

00:07:29.270 --> 00:07:30.680 align:middle line:90%
And some other stuff--

00:07:30.680 --> 00:07:31.910 align:middle line:90%
OK, neat.

00:07:31.910 --> 00:07:35.600 align:middle line:90%
Looks to be some extra code.

00:07:35.600 --> 00:07:39.980 align:middle line:90%
OK, some more functionality.

00:07:39.980 --> 00:07:44.420 align:middle line:84%
With these buffer overflows,
again, later courses

00:07:44.420 --> 00:07:47.300 align:middle line:84%
will make a lot more sense here,
what they're doing in memory.

00:07:47.300 --> 00:07:52.670 align:middle line:84%
But basically, utilizing
overflowing memory in order

00:07:52.670 --> 00:07:55.370 align:middle line:90%
to run our own code.

00:07:55.370 --> 00:07:58.460 align:middle line:84%
So what they do here
is they overflow,

00:07:58.460 --> 00:08:02.210 align:middle line:84%
then they jump around in memory
until they find a place where

00:08:02.210 --> 00:08:03.500 align:middle line:90%
they can run code.

00:08:03.500 --> 00:08:07.340 align:middle line:84%
And then they run the shellcode
that's there, upload it

00:08:07.340 --> 00:08:10.940 align:middle line:90%
on top of the rest of this.

00:08:10.940 --> 00:08:14.060 align:middle line:84%
And it all gets passed
via a GET request.

00:08:14.060 --> 00:08:16.880 align:middle line:84%
With that, OK,
forward slash exit--

00:08:16.880 --> 00:08:19.940 align:middle line:90%
ext.dll, and then send commands.

00:08:19.940 --> 00:08:20.585 align:middle line:90%
Wait a second.

00:08:20.585 --> 00:08:23.420 align:middle line:90%


00:08:23.420 --> 00:08:29.730 align:middle line:90%
We had-- [INAUDIBLE] here.

00:08:29.730 --> 00:08:36.390 align:middle line:84%
All right, forward slash ext.dll
question mark mfc, OK, command.

00:08:36.390 --> 00:08:37.830 align:middle line:90%
And it tells it to do stuff.

00:08:37.830 --> 00:08:46.695 align:middle line:84%
So the command is
going to be PassThru&,

00:08:46.695 --> 00:08:48.820 align:middle line:84%
and then it's going to pass
the rest of this stuff.

00:08:48.820 --> 00:08:51.750 align:middle line:90%


00:08:51.750 --> 00:08:52.250 align:middle line:90%
OK.

00:08:52.250 --> 00:08:57.580 align:middle line:90%


00:08:57.580 --> 00:08:59.560 align:middle line:90%
Neat.

00:08:59.560 --> 00:09:04.840 align:middle line:84%
We could go through and figure
out how to use this manually,

00:09:04.840 --> 00:09:08.620 align:middle line:90%
or there was a Metasploit one.

00:09:08.620 --> 00:09:10.640 align:middle line:84%
We've got a whole
course on Metasploit.

00:09:10.640 --> 00:09:13.900 align:middle line:84%
Alexi took you through how
Metasploit works, why it works,

00:09:13.900 --> 00:09:15.100 align:middle line:90%
lots of great stuff.

00:09:15.100 --> 00:09:16.520 align:middle line:90%
There's an exploit for it.

00:09:16.520 --> 00:09:19.900 align:middle line:84%
So we could find this
module and run it.

00:09:19.900 --> 00:09:24.250 align:middle line:84%
While we're here, let's read
about it and see what it means,

00:09:24.250 --> 00:09:27.590 align:middle line:90%
see what it does.

00:09:27.590 --> 00:09:29.660 align:middle line:84%
Metasploit modules
are written in Ruby.

00:09:29.660 --> 00:09:33.560 align:middle line:84%
I don't know Ruby either,
as in I couldn't write Ruby.

00:09:33.560 --> 00:09:36.800 align:middle line:84%
If you asked me to make this, I
could figure it out eventually.

00:09:36.800 --> 00:09:39.890 align:middle line:84%
But, again, it's in
English, so let's see

00:09:39.890 --> 00:09:43.310 align:middle line:84%
if there's some things
that make sense to us.

00:09:43.310 --> 00:09:46.640 align:middle line:90%
We've got classes, OK.

00:09:46.640 --> 00:09:50.960 align:middle line:84%
There's just a Metasploit
exploit for remote.

00:09:50.960 --> 00:09:53.840 align:middle line:84%
Great ranking-- that probably
means it works really well.

00:09:53.840 --> 00:09:57.560 align:middle line:84%
Note BadBlue doesn't give any
HTTP headers when requesting.

00:09:57.560 --> 00:09:58.760 align:middle line:90%
That's good to know.

00:09:58.760 --> 00:10:00.500 align:middle line:84%
However, a proper
server header is

00:10:00.500 --> 00:10:04.550 align:middle line:84%
returned when requesting
index.html or using HEAD.

00:10:04.550 --> 00:10:08.120 align:middle line:90%
Neat, OK.

00:10:08.120 --> 00:10:10.670 align:middle line:84%
What it's going to pass us--
this module exploits stack

00:10:10.670 --> 00:10:13.880 align:middle line:84%
buffer overflow in
2.72b and earlier.

00:10:13.880 --> 00:10:15.410 align:middle line:90%
That's good to know.

00:10:15.410 --> 00:10:23.920 align:middle line:84%
Same CVE that we've seen
before, and that same ID.

00:10:23.920 --> 00:10:26.320 align:middle line:90%
OK, we have some bad characters.

00:10:26.320 --> 00:10:26.950 align:middle line:90%
Neat.

00:10:26.950 --> 00:10:29.950 align:middle line:84%
We'll get into that,
again, later course.

00:10:29.950 --> 00:10:33.170 align:middle line:84%
Excited to talk about it,
but not going to do it here.

00:10:33.170 --> 00:10:35.170 align:middle line:84%
And then the exploit
does some stuff.

00:10:35.170 --> 00:10:42.310 align:middle line:84%
It offsets a lot of what
we saw in that Perl.

00:10:42.310 --> 00:10:44.800 align:middle line:84%
This stuff doesn't
make a ton of sense

00:10:44.800 --> 00:10:47.020 align:middle line:90%
unless it's been explained.

00:10:47.020 --> 00:10:48.130 align:middle line:90%
How is it passing it?

00:10:48.130 --> 00:10:50.260 align:middle line:90%
OK, it's got a URI.

00:10:50.260 --> 00:10:55.780 align:middle line:84%
Forward slash
ext.dll?mfcisapicommand

00:10:55.780 --> 00:10:57.070 align:middle line:90%
PassThru&.

00:10:57.070 --> 00:10:59.980 align:middle line:90%
OK, gotcha.

00:10:59.980 --> 00:11:02.680 align:middle line:84%
So it's going to do that
and all those things.

00:11:02.680 --> 00:11:05.963 align:middle line:90%


00:11:05.963 --> 00:11:06.880 align:middle line:90%
Let's go play with it.

00:11:06.880 --> 00:11:12.365 align:middle line:90%


00:11:12.365 --> 00:11:12.865 align:middle line:90%
There we go.

00:11:12.865 --> 00:11:18.220 align:middle line:90%


00:11:18.220 --> 00:11:19.585 align:middle line:90%
Lit up some MSF console.

00:11:19.585 --> 00:11:26.410 align:middle line:90%


00:11:26.410 --> 00:11:36.190 align:middle line:90%
Search for BadBlue 2.7.

00:11:36.190 --> 00:11:50.700 align:middle line:90%
And there it is.

00:11:50.700 --> 00:11:51.420 align:middle line:90%
Use 29.

00:11:51.420 --> 00:11:58.260 align:middle line:90%


00:11:58.260 --> 00:12:02.430 align:middle line:90%
Yep, targets BadBlue and 2.72.

00:12:02.430 --> 00:12:04.110 align:middle line:90%
Anything else in here?

00:12:04.110 --> 00:12:05.610 align:middle line:90%
Same exploit we just saw.

00:12:05.610 --> 00:12:09.800 align:middle line:90%


00:12:09.800 --> 00:12:11.810 align:middle line:90%
And we can set up proxy chains.

00:12:11.810 --> 00:12:12.455 align:middle line:90%
Don't need to.

00:12:12.455 --> 00:12:13.760 align:middle line:90%
We need an RHOST.

00:12:13.760 --> 00:12:17.180 align:middle line:90%
We need an RPORT.

00:12:17.180 --> 00:12:20.600 align:middle line:90%
Don't need SSL because HTTP.

00:12:20.600 --> 00:12:24.380 align:middle line:90%
And-- doo, doo, doo--

00:12:24.380 --> 00:12:26.010 align:middle line:90%
we need to set a payload.

00:12:26.010 --> 00:12:33.855 align:middle line:90%
So windows x64.

00:12:33.855 --> 00:12:39.900 align:middle line:90%


00:12:39.900 --> 00:12:40.400 align:middle line:90%
Nope.

00:12:40.400 --> 00:12:44.600 align:middle line:90%


00:12:44.600 --> 00:12:47.900 align:middle line:90%
Meterpreter reverse_tcp.

00:12:47.900 --> 00:12:52.510 align:middle line:84%
Sorry, Metasploit's
smarter than I am.

00:12:52.510 --> 00:12:58.505 align:middle line:84%
Set rhosts and
stuff that copied.

00:12:58.505 --> 00:12:59.005 align:middle line:90%
I don't.

00:12:59.005 --> 00:13:06.240 align:middle line:90%


00:13:06.240 --> 00:13:08.505 align:middle line:84%
Linux is neat when
you do the stuff.

00:13:08.505 --> 00:13:19.080 align:middle line:90%


00:13:19.080 --> 00:13:21.730 align:middle line:90%
Set lhost.

00:13:21.730 --> 00:13:28.060 align:middle line:90%
And eth1.

00:13:28.060 --> 00:13:32.800 align:middle line:90%


00:13:32.800 --> 00:13:34.180 align:middle line:90%
That LPORT works.

00:13:34.180 --> 00:13:36.700 align:middle line:90%
Everything with a yes has a yes.

00:13:36.700 --> 00:13:38.710 align:middle line:90%
Let's run it.

00:13:38.710 --> 00:13:40.630 align:middle line:90%
OK, so it's sending.

00:13:40.630 --> 00:13:42.010 align:middle line:90%
It's trying out the target.

00:13:42.010 --> 00:13:44.140 align:middle line:90%
Sends a stage.

00:13:44.140 --> 00:13:48.730 align:middle line:84%
Opens a meterpreter session,
and we are in the machine.

00:13:48.730 --> 00:13:54.400 align:middle line:84%
Hey, we are on that
Windows 2012 R2

00:13:54.400 --> 00:14:02.944 align:middle line:84%
and in a 32-bit
meterpreter shell.

00:14:02.944 --> 00:14:06.730 align:middle line:90%
Oh, no, shows 64.

00:14:06.730 --> 00:14:08.590 align:middle line:90%
From there, we can do a lot.

00:14:08.590 --> 00:14:10.750 align:middle line:84%
And Alexi goes into
details in what

00:14:10.750 --> 00:14:13.835 align:middle line:90%
you can do with Metasploit.

00:14:13.835 --> 00:14:18.100 align:middle line:84%
I was never-- auditing--
we will get into what else

00:14:18.100 --> 00:14:19.572 align:middle line:90%
we can find on this machine.

00:14:19.572 --> 00:14:20.530 align:middle line:90%
It's a Windows machine.

00:14:20.530 --> 00:14:22.750 align:middle line:84%
There's a bunch
of-- baked into it

00:14:22.750 --> 00:14:24.500 align:middle line:90%
that we can take advantage of.

00:14:24.500 --> 00:14:27.790 align:middle line:84%
And from there, we'll see
what else we can find.

00:14:27.790 --> 00:14:30.010 align:middle line:90%
But we found a vulnerability.

00:14:30.010 --> 00:14:34.330 align:middle line:84%
We found out that
we could exploit it.

00:14:34.330 --> 00:14:36.760 align:middle line:84%
Found a nice way
of running that.

00:14:36.760 --> 00:14:39.670 align:middle line:84%
Now, if you know
Perl, if you could

00:14:39.670 --> 00:14:44.530 align:middle line:84%
run the get request yourself,
if you knew Python or Ruby,

00:14:44.530 --> 00:14:46.912 align:middle line:90%
you could set this up yourself.

00:14:46.912 --> 00:14:48.370 align:middle line:84%
I didn't want to
get into all that.

00:14:48.370 --> 00:14:50.020 align:middle line:90%
We had a Metasploit module.

00:14:50.020 --> 00:14:51.790 align:middle line:84%
Take advantage of that
Metasploit module.

00:14:51.790 --> 00:14:52.910 align:middle line:90%
And it works.

00:14:52.910 --> 00:14:55.990 align:middle line:84%
So however you want to skin the
cat, we found a vulnerability.

00:14:55.990 --> 00:14:59.140 align:middle line:84%
We found out that this
machine is exploitable.

00:14:59.140 --> 00:15:04.270 align:middle line:84%
And we can now go
into more, enumerate,

00:15:04.270 --> 00:15:05.900 align:middle line:84%
finish out the rest
of our pen test.

00:15:05.900 --> 00:15:08.067 align:middle line:84%
This is something that we
can include in our report.

00:15:08.067 --> 00:15:13.900 align:middle line:84%
You had a server running this
software that is vulnerable.

00:15:13.900 --> 00:15:16.360 align:middle line:84%
Now, there's other
versions of software.

00:15:16.360 --> 00:15:18.280 align:middle line:84%
There's other ways of
serving up those files.

00:15:18.280 --> 00:15:20.740 align:middle line:90%
There's other options.

00:15:20.740 --> 00:15:21.970 align:middle line:90%
And this might be internal.

00:15:21.970 --> 00:15:24.970 align:middle line:84%
It might be-- it should
probably be firewalled.

00:15:24.970 --> 00:15:26.110 align:middle line:90%
It might be firewalled.

00:15:26.110 --> 00:15:30.310 align:middle line:84%
But if it's HTTP, then
anything going across the wire,

00:15:30.310 --> 00:15:32.350 align:middle line:84%
if there is a man
in the middle, they

00:15:32.350 --> 00:15:36.490 align:middle line:84%
could read and pull out any
objects from those packets.

00:15:36.490 --> 00:15:39.160 align:middle line:84%
There's just a lot in
there that is worth

00:15:39.160 --> 00:15:42.370 align:middle line:84%
noting and worth bringing
up to your client,

00:15:42.370 --> 00:15:45.010 align:middle line:84%
and a lot of remediation
possibilities.

00:15:45.010 --> 00:15:47.800 align:middle line:84%
Now, then, they could
decide, OK, that's fine.

00:15:47.800 --> 00:15:48.580 align:middle line:90%
This is internal.

00:15:48.580 --> 00:15:49.990 align:middle line:90%
We have it firewalled.

00:15:49.990 --> 00:15:58.590 align:middle line:84%
Maybe that server is firewalled,
so only internal machines

00:15:58.590 --> 00:15:59.380 align:middle line:90%
can get to it.

00:15:59.380 --> 00:16:02.640 align:middle line:84%
And since we were VPNed
in, we have access.

00:16:02.640 --> 00:16:03.210 align:middle line:90%
I don't know.

00:16:03.210 --> 00:16:06.120 align:middle line:84%
But you bring it up, you
identify it, you highlight it,

00:16:06.120 --> 00:16:09.840 align:middle line:84%
and then it's up to your
client to decide how they want

00:16:09.840 --> 00:16:11.460 align:middle line:90%
to mitigate or remediate it.

00:16:11.460 --> 00:16:13.500 align:middle line:90%
All we do is find and report.

00:16:13.500 --> 00:16:14.190 align:middle line:90%
All right.

00:16:14.190 --> 00:16:17.520 align:middle line:84%
With that, we're going
to close out this one

00:16:17.520 --> 00:16:20.420 align:middle line:90%
and move on to the next course.

00:16:20.420 --> 00:16:22.000 align:middle line:90%