WEBVTT - This file was automatically generated by VIMEO

0
00:00:06.800 --> 00:00:09.200
It's time for the second demo.

1
00:00:09.800 --> 00:00:12.900
Let me show you how you can use Google hacking

2
00:00:12.900 --> 00:00:16.400
 to find sensitive information in SQL

3
00:00:15.400 --> 00:00:17.500
 syntax errors.

4
00:00:19.200 --> 00:00:22.900
The four most popular databases are Microsoft

5
00:00:22.900 --> 00:00:26.500
 SQL MySQL postgresql and

6
00:00:26.500 --> 00:00:27.400
 Oracle.

7
00:00:28.300 --> 00:00:31.700
On this screen, you can see Google search engine

8
00:00:31.700 --> 00:00:34.700
 queries that can be used for finding

9
00:00:34.700 --> 00:00:38.200
 SQL syntax errors in this databases.

10
00:00:39.500 --> 00:00:43.400
All these queries start with site hacking

11
00:00:42.400 --> 00:00:46.500
 web applications.com because the

12
00:00:45.500 --> 00:00:48.400
 web application is hosted on this

13
00:00:48.400 --> 00:00:48.700
 domain.

14
00:00:49.900 --> 00:00:52.200
After the domain name, you can

15
00:00:52.200 --> 00:00:55.900
 see the logical operator and together with

16
00:00:55.900 --> 00:00:59.200
 the strings indicating SQL syntax

17
00:00:58.200 --> 00:01:02.300
 errors in this databases. The

18
00:01:01.300 --> 00:01:04.200
 strings are put in between

19
00:01:04.200 --> 00:01:07.300
 round brackets, and there are separated by

20
00:01:07.300 --> 00:01:09.000
 The Logical operator or

21
00:01:11.100 --> 00:01:14.800
SQL syntax errors are different for different

22
00:01:14.800 --> 00:01:17.100
 databases. And I don't

23
00:01:17.100 --> 00:01:20.300
 know which database is used by the web

24
00:01:20.300 --> 00:01:23.600
 application hosted on the domain hacking web

25
00:01:23.600 --> 00:01:26.800
 applications.com. That's why

26
00:01:26.800 --> 00:01:29.800
 I will use this for Google search engine

27
00:01:29.800 --> 00:01:32.200
 queries one by one and I

28
00:01:32.200 --> 00:01:35.300
 hope to see that Google indexed a

29
00:01:35.300 --> 00:01:38.300
 web page with a string indicating and

30
00:01:38.300 --> 00:01:41.600
 SQL syntax error in one of these four

31
00:01:41.600 --> 00:01:43.600
 most popular databases.

32
00:01:45.400 --> 00:01:47.300
Okay, so far so good.

33
00:01:48.500 --> 00:01:51.500
Let me first copy the Google search engine

34
00:01:51.500 --> 00:01:53.700
 query for MySQL.

35
00:01:54.700 --> 00:01:58.300
Let me paste it in Google search and

36
00:01:57.300 --> 00:02:00.700
 let's see if Google indexed

37
00:02:00.700 --> 00:02:04.300
 a web page with a string indicating and

38
00:02:03.300 --> 00:02:06.600
 MySQL syntax error on

39
00:02:06.600 --> 00:02:09.400
 the domain hacking web applications Comm.

40
00:02:11.700 --> 00:02:15.100
As you can see Google didn't index

41
00:02:14.100 --> 00:02:17.500
 anything related to my search

42
00:02:17.500 --> 00:02:17.800
 query.

43
00:02:19.100 --> 00:02:22.300
Okay, next I will go to

44
00:02:22.300 --> 00:02:24.300
 my list of search queries.

45
00:02:25.300 --> 00:02:28.100
I will take the second query from this list.

46
00:02:28.900 --> 00:02:31.600
It will be Google search engine query

47
00:02:31.600 --> 00:02:33.800
 for Microsoft SQL Server.

48
00:02:35.100 --> 00:02:36.600
I will copy this query.

49
00:02:37.400 --> 00:02:40.600
I will paste it in Google search and I

50
00:02:40.600 --> 00:02:43.400
 will check if Google indexed a

51
00:02:43.400 --> 00:02:46.900
 web page with a string indicating a

52
00:02:46.900 --> 00:02:49.800
 Microsoft SQL Server syntax error

53
00:02:49.800 --> 00:02:53.000
 on the domain hacking web applications Comm.

54
00:02:56.500 --> 00:02:59.300
As you can see one web page has

55
00:02:59.300 --> 00:03:00.900
 been indexed by Google.

56
00:03:01.900 --> 00:03:03.800
Let's check what is inside?

57
00:03:05.200 --> 00:03:08.500
The Source error and stock Trace are presented

58
00:03:08.500 --> 00:03:09.700
 on this web page.

59
00:03:10.400 --> 00:03:12.700
Let's focus on the source error.

60
00:03:13.400 --> 00:03:17.000
There are five lines of the source code and in

61
00:03:16.100 --> 00:03:20.000
 the line number 47 the connection

62
00:03:19.500 --> 00:03:22.400
 string to the database is defined.

63
00:03:23.400 --> 00:03:26.400
Let's analyze the details of this connection

64
00:03:26.400 --> 00:03:27.000
 string.

65
00:03:28.300 --> 00:03:31.400
As you can see there are credentials to the

66
00:03:31.400 --> 00:03:34.800
 database and it clearly shows how easily

67
00:03:34.800 --> 00:03:37.300
 you can use Google hacking to find

68
00:03:37.300 --> 00:03:40.900
 SQL syntax errors with sensitive data

69
00:03:40.900 --> 00:03:43.800
 in publicly exposed web pages.

70
00:03:45.200 --> 00:03:48.700
Okay. Now we are done with this demo. So

71
00:03:48.700 --> 00:03:51.200
 let me jump to the next one and let me

72
00:03:51.200 --> 00:03:54.400
 show you how Google hacking can be used for

73
00:03:54.400 --> 00:03:57.500
 finding publicly exposed backup files.
