WEBVTT

00:01.600 --> 00:09.370
Scanning for vulnerabilities in web applications Welcome to the video enumerating Web sites.

00:09.420 --> 00:15.600
In this video we will review how we can use and map to identify sites running Web services within our

00:15.600 --> 00:16.400
network.

00:17.430 --> 00:22.900
Use a free tool called whap Gleiser to figure out what technologies are running on a given Web site

00:23.970 --> 00:29.580
and we also look at a few internet resources that are useful for identifying this type of port and service

00:29.580 --> 00:30.720
information.

00:32.190 --> 00:37.590
In this final section of the course I wanted to expand upon what we've been learning about network and

00:37.590 --> 00:44.040
vulnerabilities scanning by putting us a little deeper into the mindset of a penetration tester.

00:44.180 --> 00:50.080
For example you might end up working for a security firm that does web application penetration tests.

00:50.210 --> 00:56.060
And so one skill you should have is the ability to identify what various technologies are running on

00:56.060 --> 01:01.140
a Web site so that you can better gauge what kind of attacks you want to run against it.

01:01.340 --> 01:07.160
Before we start down that path though let's back up and do a little review in some of the past videos

01:07.220 --> 01:13.120
we covered how we can use and map to output results into three different formats.

01:13.130 --> 01:14.720
Let's review that command again.

01:15.790 --> 01:22.480
First I'm going to look at my subnet stop T6 t to make sure it contains all the targets in scope for

01:22.480 --> 01:25.390
eventual penetration testing.

01:25.570 --> 01:34.530
Then I'm going to run and map space TAC lowercase i capital L and reference the subnet statics t file

01:35.840 --> 01:42.470
then I'm going to add a tack lower lowercase o capital A and then the name of what the output file will

01:42.470 --> 01:42.980
be.

01:43.830 --> 01:50.880
I'll just call this targets because and map will automatically add the appropriate extensions of SML

01:51.450 --> 01:56.210
and map and G and map next.

01:56.210 --> 02:02.910
Let's review how we used the SML output in combination with a tool like eyewitness to take screenshots

02:02.990 --> 02:08.380
of any webservices found in our and map scan to do that.

02:08.540 --> 02:11.280
We call eyewitness by its full path.

02:11.780 --> 02:20.800
And for me that's in the slash Opt. slash eyewitness folder and then we add a TAC X followed by the

02:20.800 --> 02:27.650
SML file we just created and then we add a tak tak web to the end.

02:30.010 --> 02:35.550
When eyewitness's done doing its operation we'll be asked if we want to open the report.

02:35.800 --> 02:39.210
So we'll type Y and press enter.

02:39.400 --> 02:46.270
And here we can see I-Witness has taken a screenshot of what looks to be an Apache Tomcat server and

02:46.300 --> 02:48.790
a link router.

02:48.860 --> 02:54.890
Now along the left side here we get a little bit of additional information such as the page title and

02:54.890 --> 02:56.630
potential server version.

02:58.460 --> 03:03.860
We've also covered a bit of the unmap script engine and how we can leverage those scripts to really

03:03.860 --> 03:09.850
dig deep into a host's services for detailed information.

03:09.950 --> 03:22.610
For example I'll run and map plus TAC tax script space HTP TAC in-room NSC Plus the IP of the target

03:22.610 --> 03:34.620
host followed by TAC P 1880 which specifies the port the services running on this HTP noom script does

03:34.620 --> 03:39.330
some fingerprinting of the web service and gives us a little more information about it.

03:40.900 --> 03:47.860
And again as we've covered in the past and map has many scripts you can run both for H TDP as well as

03:47.860 --> 03:55.070
a whole slew of other services to probe your host for a trove of information.

03:55.090 --> 04:00.360
However when it comes to assignments you might receive as a penetration tester you're likely going to

04:00.360 --> 04:05.670
be testing applications in the cloud and you will probably want to do some initial recon on the site

04:06.030 --> 04:09.200
to learn about the technologies that the applications use.

04:09.690 --> 04:11.960
But you want to tread carefully here.

04:12.090 --> 04:17.940
In my opinion you shouldn't actively scan a customer's site until the engagement formally begins.

04:18.390 --> 04:23.850
But the good news is you can gather a lot of good enumeration data either through Web sites that collect

04:23.850 --> 04:29.050
this information or plugins you can install in your browser.

04:29.100 --> 04:37.360
For example let's open up a browser and go to built with dotcom built with makes it easy for you to

04:37.360 --> 04:42.890
figure out naturally what technologies sites were built with.

04:42.900 --> 04:51.370
So I'm just going to type in 7 mins SEC here which is my corporate Web site and we can see that built

04:51.370 --> 04:58.420
with returns a ton of useful information including the type of analytics and tracking tools I use installed

04:58.420 --> 05:06.910
widgets the content management system javascript libraries and even some information about my DNS configuration

05:07.500 --> 05:16.390
email hosting and SSL certificate provider this information can be incredibly helpful not just for web

05:16.540 --> 05:22.420
penetration testing but a more broad engagement where you might be tasked with sending phishing emails

05:22.420 --> 05:24.440
to an organization.

05:24.500 --> 05:30.470
For example if someone was doing a fishing campaign against seven minute security users they could craft

05:30.470 --> 05:38.100
a realistic looking message that asks users to change their office 365 password and the attacker would

05:38.100 --> 05:44.520
likely have success because an average user could think oh I have Office 365 so I better click this

05:44.520 --> 05:46.160
link right now.

05:46.160 --> 05:48.850
Anyway back to Neumar raiding Web sites.

05:48.900 --> 05:56.540
Another good site I like for this type of info gathering is W3 TX dot com.

05:56.590 --> 05:58.750
It has the same kind of setup.

05:58.750 --> 06:07.420
We simply type in a URL click site info and W3 Tex spits out a nice table of information with the Web

06:07.460 --> 06:11.320
site's summary how long it has been online.

06:11.340 --> 06:15.260
The content management system it's using etc..

06:15.520 --> 06:21.250
Now I personally find it handy to be able to glean some of this web technology information with just

06:21.250 --> 06:24.320
a single click right from within my browser.

06:24.790 --> 06:28.660
So I want to show you a plugin called whap Elisir.

06:28.850 --> 06:35.320
You can find it pretty quickly by doing a search for Apple Isar on Google and then I'm just going to

06:35.320 --> 06:40.580
kind of follow the link trail here to get this installed for my browser.

06:50.070 --> 06:57.380
Once appetizer is installed it will passively gather information about every site we visit so let's

06:57.380 --> 07:07.850
Google for a wasp Jew shop which is one of my favorite tools for practicing web application pen testing.

07:07.870 --> 07:14.140
It looks like their main site is hosted over at a wasp dot org and now that the site is loaded in my

07:14.140 --> 07:21.310
browser Let's click this little icon in the far right of our address bar and will see that weap Lizer

07:21.310 --> 07:25.200
has identified this site as running media wiki.

07:25.270 --> 07:29.020
Version 1 2 7 2.

07:29.100 --> 07:31.430
It uses Google Analytics.

07:31.440 --> 07:39.720
It's running on an Apache server and is based in THP having the software version of 6:59.

07:40.000 --> 07:48.040
In this case can be really handy as we might then want to hop over to a site like exploit D-B like we

07:48.040 --> 07:54.460
have in past videos and we can search for any exploits that might be available for that specific version

07:54.520 --> 07:56.910
of Media wiki.

07:57.000 --> 08:02.490
I highly recommend you take some time and do your homework on your targets using these kind of sites

08:02.550 --> 08:07.530
and plugins so that you can have a more efficient and focused penetration test.

08:07.560 --> 08:14.810
Once it begins in our next video we'll look at a built in tool called nikto to find a low hanging Web

08:14.810 --> 08:15.940
site vulnerabilities.
