WEBVTT

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


00:00:10.260 --> 00:00:12.420 align:middle line:90%
We're going to revisit Nessus.

00:00:12.420 --> 00:00:15.240 align:middle line:84%
And in this case, we're going
to look at it and actually dive

00:00:15.240 --> 00:00:16.620 align:middle line:84%
into some of the
vulnerabilities,

00:00:16.620 --> 00:00:19.020 align:middle line:84%
rather than just looking
at what the scans are

00:00:19.020 --> 00:00:22.680 align:middle line:90%
and what the reports look like.

00:00:22.680 --> 00:00:27.120 align:middle line:84%
We have our Nessus
on this environment.

00:00:27.120 --> 00:00:29.280 align:middle line:84%
And we've done all
these scans before.

00:00:29.280 --> 00:00:30.990 align:middle line:84%
If you don't remember
doing the scans,

00:00:30.990 --> 00:00:34.440 align:middle line:84%
maybe you missed the initial
lab in auditing fundamentals.

00:00:34.440 --> 00:00:37.830 align:middle line:84%
I suggest you go back there and
see how to get through these.

00:00:37.830 --> 00:00:41.820 align:middle line:84%
Otherwise, the directions are
in the instructions for the lab,

00:00:41.820 --> 00:00:45.300 align:middle line:84%
but we're going to dive into
some of the important aspects.

00:00:45.300 --> 00:00:50.730 align:middle line:84%
Now, not make the
same lab video twice.

00:00:50.730 --> 00:00:56.640 align:middle line:84%
In our advanced network scan,
we scanned demo.ine.local

00:00:56.640 --> 00:01:00.480 align:middle line:90%
with a web app scan.

00:01:00.480 --> 00:01:04.230 align:middle line:84%
And in here we've
got this CGI abuses.

00:01:04.230 --> 00:01:10.090 align:middle line:84%
And a phpMyAdmin prior to
4.8 SQLi vulnerability.

00:01:10.090 --> 00:01:13.680 align:middle line:84%
So there's SQL
injection vulnerability

00:01:13.680 --> 00:01:22.090 align:middle line:84%
due to the fact that this is
an old version prior to 4.8.6.

00:01:22.090 --> 00:01:24.370 align:middle line:84%
And the solution is
fairly straightforward

00:01:24.370 --> 00:01:29.430 align:middle line:84%
here-- upgrade to
4.8.6 or later,

00:01:29.430 --> 00:01:34.020 align:middle line:84%
or apply patches referenced
in the vendor advisories.

00:01:34.020 --> 00:01:35.610 align:middle line:90%
And we can look down.

00:01:35.610 --> 00:01:41.940 align:middle line:90%
There is CVE-2019-11768.

00:01:41.940 --> 00:01:47.880 align:middle line:84%
And this is from 2019 when
that vulnerability came about.

00:01:47.880 --> 00:01:52.170 align:middle line:84%
Now, we went and looked to the
National Vulnerability Database

00:01:52.170 --> 00:02:01.120 align:middle line:84%
for other vulnerabilities
in the past video,

00:02:01.120 --> 00:02:02.950 align:middle line:84%
and now we're going
to go look at it

00:02:02.950 --> 00:02:05.830 align:middle line:84%
in something that
we found in Nessus.

00:02:05.830 --> 00:02:07.603 align:middle line:90%
So Nessus is a great tool.

00:02:07.603 --> 00:02:09.520 align:middle line:84%
You could use it on a
pen test if it's allowed

00:02:09.520 --> 00:02:10.810 align:middle line:90%
and it's in scope.

00:02:10.810 --> 00:02:13.630 align:middle line:84%
And then you want
to proof of concept

00:02:13.630 --> 00:02:17.590 align:middle line:84%
those things if that is
also part of the expectation

00:02:17.590 --> 00:02:20.020 align:middle line:90%
for your pen test.

00:02:20.020 --> 00:02:26.530 align:middle line:84%
So now we have CVE-2019-11768,
same thing, phpMyAdmin

00:02:26.530 --> 00:02:32.410 align:middle line:84%
before 4.9.0.1 instead of that
4.8.6, probably very similar,

00:02:32.410 --> 00:02:35.770 align:middle line:90%
again from June of 2019.

00:02:35.770 --> 00:02:38.620 align:middle line:90%
And this has a high criticality.

00:02:38.620 --> 00:02:42.610 align:middle line:90%
And let's dive into that.

00:02:42.610 --> 00:02:46.030 align:middle line:84%
This takes unauthenticated
users and gives them

00:02:46.030 --> 00:02:47.690 align:middle line:90%
access to the database.

00:02:47.690 --> 00:02:50.320 align:middle line:84%
So it's a network attack
with low complexity.

00:02:50.320 --> 00:02:51.610 align:middle line:90%
No privileges are required.

00:02:51.610 --> 00:02:55.160 align:middle line:84%
No user interaction is required
with high confidentiality,

00:02:55.160 --> 00:02:57.410 align:middle line:90%
integrity, and availability.

00:02:57.410 --> 00:03:03.490 align:middle line:84%
It makes for a pretty beastly
kind of vulnerability.

00:03:03.490 --> 00:03:05.770 align:middle line:84%
It's quite a good
one for them to have

00:03:05.770 --> 00:03:09.400 align:middle line:90%
included in this web app.

00:03:09.400 --> 00:03:12.250 align:middle line:90%


00:03:12.250 --> 00:03:16.000 align:middle line:84%
It was made vulnerable so
we have things to look at.

00:03:16.000 --> 00:03:20.150 align:middle line:90%


00:03:20.150 --> 00:03:25.760 align:middle line:84%
We can look at the links and
see exactly what phpMyAdmin

00:03:25.760 --> 00:03:28.760 align:middle line:90%
recommends.

00:03:28.760 --> 00:03:30.860 align:middle line:84%
There's the weaknesses,
and then the CPE,

00:03:30.860 --> 00:03:38.450 align:middle line:84%
and what Nessus utilized to
identify the vulnerability.

00:03:38.450 --> 00:03:43.580 align:middle line:84%
Now, it is very useful once you
find a vulnerability like this

00:03:43.580 --> 00:03:47.450 align:middle line:84%
to go ahead and do a proof
of concept if it's within--

00:03:47.450 --> 00:03:49.430 align:middle line:84%
if it makes sense, if
it's within the time

00:03:49.430 --> 00:03:53.345 align:middle line:84%
limit, and it's within the
scope of your pen test.

00:03:53.345 --> 00:03:55.890 align:middle line:90%


00:03:55.890 --> 00:03:59.150 align:middle line:84%
So back in this environment,
Nessus makes it easy for us.

00:03:59.150 --> 00:04:01.160 align:middle line:90%
It gives us the URL.

00:04:01.160 --> 00:04:03.830 align:middle line:84%
It's this
demo.ine.local/phpmyadmin.

00:04:03.830 --> 00:04:07.340 align:middle line:90%


00:04:07.340 --> 00:04:14.000 align:middle line:84%
So if we visit that page,
which we didn't have to log in

00:04:14.000 --> 00:04:17.959 align:middle line:84%
or anything, we
just put that in.

00:04:17.959 --> 00:04:20.750 align:middle line:90%
It gave us access.

00:04:20.750 --> 00:04:23.750 align:middle line:84%
If we look at some
of the tables,

00:04:23.750 --> 00:04:27.980 align:middle line:90%
there's a utility table.

00:04:27.980 --> 00:04:30.185 align:middle line:90%
And in here there is accounts.

00:04:30.185 --> 00:04:32.890 align:middle line:90%


00:04:32.890 --> 00:04:36.800 align:middle line:84%
And so it ran this,
select all from accounts,

00:04:36.800 --> 00:04:42.380 align:middle line:84%
and it's sharing that without
us ever authenticating.

00:04:42.380 --> 00:04:44.908 align:middle line:84%
You want these things
hidden behind authentication

00:04:44.908 --> 00:04:45.950 align:middle line:90%
so people have to log in.

00:04:45.950 --> 00:04:48.380 align:middle line:84%
So people who need them
get access to people

00:04:48.380 --> 00:04:50.570 align:middle line:90%
who don't don't get access.

00:04:50.570 --> 00:04:56.070 align:middle line:84%
Just because the
version of this web app,

00:04:56.070 --> 00:04:59.600 align:middle line:84%
it gives unauthenticated access
once you know what the page is.

00:04:59.600 --> 00:05:02.600 align:middle line:84%
This is like
vulnerabilities from 1999.

00:05:02.600 --> 00:05:05.600 align:middle line:84%
These are just security
through obscurity,

00:05:05.600 --> 00:05:07.828 align:middle line:84%
where if you don't know
what the website is,

00:05:07.828 --> 00:05:09.120 align:middle line:90%
you won't be able to get to it.

00:05:09.120 --> 00:05:10.490 align:middle line:90%
You won't get access.

00:05:10.490 --> 00:05:13.460 align:middle line:90%
We want better security now.

00:05:13.460 --> 00:05:17.870 align:middle line:84%
So this is not good, because
what you can see here

00:05:17.870 --> 00:05:23.750 align:middle line:84%
is we've got usernames,
passwords, signatures,

00:05:23.750 --> 00:05:24.800 align:middle line:90%
first name, last name.

00:05:24.800 --> 00:05:31.010 align:middle line:84%
It even tells us if they
are admins, SoSecret.

00:05:31.010 --> 00:05:34.070 align:middle line:90%


00:05:34.070 --> 00:05:34.950 align:middle line:90%
This is just bad.

00:05:34.950 --> 00:05:35.820 align:middle line:90%
This is really bad.

00:05:35.820 --> 00:05:38.090 align:middle line:90%
So we would want to share this.

00:05:38.090 --> 00:05:40.910 align:middle line:84%
We would want to
make copies of this

00:05:40.910 --> 00:05:44.010 align:middle line:84%
during the pen test for use
throughout the rest of the pen

00:05:44.010 --> 00:05:44.510 align:middle line:90%
test.

00:05:44.510 --> 00:05:47.120 align:middle line:90%


00:05:47.120 --> 00:05:49.130 align:middle line:84%
And this is one of those
things where you want--

00:05:49.130 --> 00:05:50.390 align:middle line:90%
it's a critical finding.

00:05:50.390 --> 00:05:53.550 align:middle line:84%
You're going to
want it highlighted.

00:05:53.550 --> 00:05:55.310 align:middle line:90%
And they need it remediated.

00:05:55.310 --> 00:05:57.750 align:middle line:84%
It doesn't necessarily
mean they need it patched.

00:05:57.750 --> 00:05:59.450 align:middle line:84%
It doesn't mean they
need to upgrade.

00:05:59.450 --> 00:06:01.370 align:middle line:84%
It means they need
to find some solution

00:06:01.370 --> 00:06:05.660 align:middle line:84%
or accept the risk
as an organization.

00:06:05.660 --> 00:06:06.750 align:middle line:90%
That's up to them.

00:06:06.750 --> 00:06:11.510 align:middle line:84%
But you can give them options,
like patch, upgrade, hide,

00:06:11.510 --> 00:06:13.500 align:middle line:90%
get rid of this page.

00:06:13.500 --> 00:06:16.730 align:middle line:84%
You can have phpMyAdmin
in the back end

00:06:16.730 --> 00:06:18.230 align:middle line:90%
without it being public.

00:06:18.230 --> 00:06:24.080 align:middle line:84%
Those are all options,
all decent things.

00:06:24.080 --> 00:06:26.960 align:middle line:84%
But it's about making
your suggestions

00:06:26.960 --> 00:06:29.730 align:middle line:90%
useful to your client.

00:06:29.730 --> 00:06:36.270 align:middle line:84%
Now, that's going to
be it for this lesson.

00:06:36.270 --> 00:06:38.600 align:middle line:84%
We'll get into another way
of looking at things not

00:06:38.600 --> 00:06:39.950 align:middle line:90%
with a vulnerability scanner.

00:06:39.950 --> 00:06:42.050 align:middle line:84%
We have scanned
with Nmap before.

00:06:42.050 --> 00:06:43.430 align:middle line:84%
Let's go take a
look at what that

00:06:43.430 --> 00:06:47.360 align:middle line:84%
looks like if we use
it searching just

00:06:47.360 --> 00:06:49.960 align:middle line:90%
for vulnerabilities.

00:06:49.960 --> 00:06:51.063 align:middle line:90%