WEBVTT

00:02.190 --> 00:08.770
Finding and remediating system vulnerabilities in this video we will take the information we learned

00:08.770 --> 00:15.700
about our target hosts in the previous video and use a web resource called exploit D-B as well as a

00:15.700 --> 00:20.990
built in Cali tool called Search boyt to find potential vulnerabilities.

00:21.010 --> 00:26.890
We will also discuss at a high level some ways to remediate these vulnerabilities as you get more familiar

00:26.890 --> 00:32.860
with the scanning results and map at some point you'll naturally want to search for additional relevant

00:32.860 --> 00:39.010
information such as if the software and operating systems discovered on your network have known vulnerabilities

00:39.940 --> 00:40.840
in that respect.

00:40.840 --> 00:46.580
One of the best sources I can point you to is exploit D-B dotcom.

00:46.690 --> 00:48.670
It's maintained by offensive security.

00:48.700 --> 00:51.660
The same folks who managed the Kalli Linux distro.

00:51.850 --> 00:59.360
It's been around since 2009 and is updated regularly to get started on exploit D-B.

00:59.370 --> 01:03.040
You can just conduct a simple search with what you're looking for.

01:03.450 --> 01:08.280
If I use my end map results as a starting point I might be interested in what vulnerabilities are out

01:08.280 --> 01:15.120
there for DNS mask so I can just hit the search box and type in dnsmasq.

01:15.160 --> 01:20.750
However I've got to fill out some captions before that search completes which can be a bit annoying.

01:24.330 --> 01:30.300
But once the capture requirements are satisfied I can see the results of my search which contain a handful

01:30.300 --> 01:34.660
of vulnerabilities for various versions of DNS mask.

01:34.720 --> 01:35.370
That's cool.

01:35.380 --> 01:41.950
But notice if we try to do a search without checking the I'm not a robot box the exploit D-B site offers

01:41.950 --> 01:49.320
us an alternative way to find vulnerabilities via search split a command line to a built in the Kalli.

01:49.370 --> 01:52.300
Let's take a look at some of the basic features of search.

01:55.450 --> 02:04.910
First let's update search Blits database by running search space Takk you then we can conduct our first

02:04.910 --> 02:10.900
basic search which is just the search command plus the term you want to search for.

02:10.980 --> 02:16.590
Now notice in our results that we get the title of each vulnerability followed by the path to the script

02:16.620 --> 02:19.320
or program on our local harddrive.

02:19.520 --> 02:25.700
If we'd rather see the or L associated with each vulnerability we can repeat our search with the TAC

02:25.790 --> 02:26.780
w flag.

02:31.290 --> 02:36.860
And we can see now how the local path of each vulnerability lines up with its online counterpart

02:43.190 --> 02:49.250
another nice things search it can do is make it easy to launch an associated script by copying the file

02:49.250 --> 02:51.420
path into the clipboard for us.

02:52.270 --> 03:01.600
So if we do a search Boit search with the TAC P Flag and then specify a vulnerability like 4 2 9 4 6

03:02.470 --> 03:05.770
we'll see that the path is now copied to the clipboard.

03:05.770 --> 03:17.270
So now we can just type python and paste in the path of the exploit script and we're off and running.

03:17.350 --> 03:23.460
I want to show you one other handy search Boit feature that can leverage an output file from Unmap.

03:23.470 --> 03:28.660
Now don't worry if you're unfamiliar with the context of the map command you're seen as we'll go more

03:28.660 --> 03:32.650
into exporting data out of map in future videos.

03:32.650 --> 03:39.670
All you need to know for now is that I'm adding a flag here to export and SML output of my scan and

03:39.670 --> 03:46.000
then once that scan is complete I can run search ploy with the tac tac and map flag and then pointed

03:46.000 --> 03:48.600
to the output SML file that was created.

03:49.620 --> 03:56.100
Once we do that the output gives us specific search commands we can run to search for vulnerabilities

03:56.460 --> 04:01.060
based on the versions of software detected in our maps scan.

04:01.080 --> 04:06.000
So in the future you might want to write a script that scans and network with and map saves the output

04:06.000 --> 04:13.950
to a file then checks the file against search its database to find potential system vulnerabilities.

04:13.950 --> 04:19.920
This can help you identify unpatched or vulnerable systems more quickly and boost the overall security

04:19.920 --> 04:20.820
of your network.

04:22.300 --> 04:27.340
In our next video we will troubleshoot some common issues that can arise during our network scanning

04:27.340 --> 04:28.420
operations.
