WEBVTT - This file was automatically generated by VIMEO

0
00:00:06.800 --> 00:00:10.000
It's time for the 6th demo. Let

1
00:00:09.200 --> 00:00:12.900
 me show you how you can use Google hacking to

2
00:00:12.900 --> 00:00:15.500
 find insecure HTTP web

3
00:00:15.500 --> 00:00:15.800
 pages.

4
00:00:17.700 --> 00:00:20.200
The web application is hosted on the

5
00:00:20.200 --> 00:00:22.700
 domain hacking web applications.com.

6
00:00:23.800 --> 00:00:27.500
I want to check if Google indexed insecure

7
00:00:26.500 --> 00:00:29.600
 HTTP web pages in

8
00:00:29.600 --> 00:00:30.700
 this web application.

9
00:00:31.800 --> 00:00:34.600
For this purpose. I will use the following

10
00:00:34.600 --> 00:00:36.700
 Google search engine query.

11
00:00:37.900 --> 00:00:40.600
site hacking web applications.com

12
00:00:41.400 --> 00:00:45.200
and minus sign in URL

13
00:00:44.200 --> 00:00:46.700
 https

14
00:00:47.900 --> 00:00:50.800
The queries starts with site hacking

15
00:00:50.800 --> 00:00:53.300
 web applications.com because the

16
00:00:53.300 --> 00:00:56.100
 web application is hosted on this domain.

17
00:00:57.100 --> 00:01:00.800
Next you can see the logical operator and

18
00:01:00.800 --> 00:01:03.800
 after The Logical operator

19
00:01:03.800 --> 00:01:06.900
 and there is minus sign

20
00:01:06.900 --> 00:01:09.500
 in URL https.

21
00:01:10.600 --> 00:01:14.100
This way I'm asking Google to return

22
00:01:13.100 --> 00:01:16.800
 index the web pages that

23
00:01:16.800 --> 00:01:20.500
 are not protected by secure https.

24
00:01:21.700 --> 00:01:24.900
In other words, I'm asking Google to

25
00:01:24.900 --> 00:01:27.500
 return indexed web pages

26
00:01:27.500 --> 00:01:31.500
 that are available over insecure http.

27
00:01:33.300 --> 00:01:36.400
Okay. Now you understand how this Google

28
00:01:36.400 --> 00:01:38.300
 search engine query works.

29
00:01:39.400 --> 00:01:40.900
So let me copy this query.

30
00:01:42.400 --> 00:01:45.600
Let me paste it in Google search and let's see

31
00:01:45.600 --> 00:01:48.500
 if Google indexed web pages

32
00:01:48.500 --> 00:01:51.600
 available over insecure HTTP

33
00:01:51.600 --> 00:01:55.200
 on the domain hacking web applications.com.

34
00:01:58.300 --> 00:02:01.900
Please notice that one insecure HTTP

35
00:02:01.900 --> 00:02:04.300
 web page has been indexed by

36
00:02:04.300 --> 00:02:04.700
 Google.

37
00:02:05.700 --> 00:02:07.300
Let's see this web page.

38
00:02:09.900 --> 00:02:12.600
There is an HTML form with

39
00:02:12.600 --> 00:02:15.700
 sensitive data and the sensitive

40
00:02:15.700 --> 00:02:17.400
 data is as follows.

41
00:02:18.100 --> 00:02:21.600
full name email phone and password

42
00:02:22.900 --> 00:02:25.700
What's more in the URL bar?

43
00:02:25.700 --> 00:02:29.000
 You can see a padlock crossed out

44
00:02:28.200 --> 00:02:31.600
 with a red line and it means

45
00:02:31.600 --> 00:02:34.600
 that this web page is available over

46
00:02:34.600 --> 00:02:37.900
 insecure HTTP. That's why

47
00:02:37.900 --> 00:02:40.600
 the sensitive data entered into

48
00:02:40.600 --> 00:02:43.100
 this HTML form will be

49
00:02:43.100 --> 00:02:46.300
 sent over insecure HTTP, which is

50
00:02:46.300 --> 00:02:49.600
 just plain text. And obviously this is

51
00:02:49.600 --> 00:02:52.000
 not good from security point of view.

52
00:02:53.100 --> 00:02:56.600
So as you can see Google hacking can help

53
00:02:56.600 --> 00:02:59.500
 you find insecure HTTP web

54
00:02:59.500 --> 00:03:02.300
 pages and this is what I presented to

55
00:03:02.300 --> 00:03:03.700
 you in this demo.

56
00:03:04.800 --> 00:03:07.500
Okay, now we are done with

57
00:03:07.500 --> 00:03:10.200
 this demo. So let me jump to the

58
00:03:10.200 --> 00:03:14.100
 next clip and let me tell you about Google hacking

59
00:03:13.100 --> 00:03:14.800
 database.
