WEBVTT - This file was automatically generated by VIMEO

0
00:00:07.900 --> 00:00:10.200
It's time for the second demo.

1
00:00:10.900 --> 00:00:14.000
Let me show you how you can use Google hacking

2
00:00:13.400 --> 00:00:17.500
 to find sensitive information in SQL

3
00:00:16.500 --> 00:00:18.600
 syntax errors.

4
00:00:20.100 --> 00:00:24.000
The four most popular databases are Microsoft

5
00:00:23.600 --> 00:00:27.500
 SQL MySQL postgresql and

6
00:00:27.500 --> 00:00:28.500
 Oracle.

7
00:00:29.400 --> 00:00:32.700
On this screen, you can see Google search engine

8
00:00:32.700 --> 00:00:35.700
 queries that can be used for finding

9
00:00:35.700 --> 00:00:38.300
 SQL syntax errors in this

10
00:00:38.300 --> 00:00:39.300
 databases.

11
00:00:40.600 --> 00:00:43.700
All these queries start with site

12
00:00:43.700 --> 00:00:47.500
 hacking web applications.com because the

13
00:00:46.500 --> 00:00:49.500
 web application is hosted on this

14
00:00:49.500 --> 00:00:49.800
 domain.

15
00:00:51.300 --> 00:00:55.100
After the domain name, you can see the logical operator

16
00:00:54.100 --> 00:00:57.800
 and together with the strings

17
00:00:57.800 --> 00:01:01.000
 indicating SQL syntax errors

18
00:01:00.200 --> 00:01:03.800
 in this databases. The strings

19
00:01:03.800 --> 00:01:06.900
 are put in between round brackets, and

20
00:01:06.900 --> 00:01:09.900
 there are separated by The Logical operator

21
00:01:09.900 --> 00:01:10.100
 or

22
00:01:12.200 --> 00:01:15.900
SQL syntax errors are different for different

23
00:01:15.900 --> 00:01:18.200
 databases. And I don't

24
00:01:18.200 --> 00:01:21.400
 know which database is used by the web

25
00:01:21.400 --> 00:01:24.700
 application hosted on the domain hacking web

26
00:01:24.700 --> 00:01:27.800
 applications.com. That's why

27
00:01:27.800 --> 00:01:30.500
 I will use this for Google search

28
00:01:30.500 --> 00:01:33.300
 engine queries one by one and I

29
00:01:33.300 --> 00:01:36.500
 hope to see that Google indexed a

30
00:01:36.500 --> 00:01:39.400
 web page with a string indicating an

31
00:01:39.400 --> 00:01:42.700
 SQL syntax error in one of these four

32
00:01:42.700 --> 00:01:44.600
 most popular databases.

33
00:01:46.500 --> 00:01:48.400
Okay, so far so good.

34
00:01:49.600 --> 00:01:52.600
Let me first copy the Google search engine

35
00:01:52.600 --> 00:01:54.700
 query for MySQL.

36
00:01:55.700 --> 00:01:59.300
Let me paste it in Google search and

37
00:01:58.300 --> 00:02:01.800
 let's see if Google indexed

38
00:02:01.800 --> 00:02:05.400
 a web page with a string indicating and

39
00:02:04.400 --> 00:02:07.700
 MySQL syntax error on

40
00:02:07.700 --> 00:02:10.400
 the domain hacking web applications Comm.

41
00:02:12.800 --> 00:02:16.100
As you can see Google didn't index

42
00:02:15.100 --> 00:02:18.500
 anything related to my search

43
00:02:18.500 --> 00:02:18.900
 query.

44
00:02:20.200 --> 00:02:23.300
Okay, next I will go to

45
00:02:23.300 --> 00:02:25.300
 my list of search queries.

46
00:02:26.100 --> 00:02:29.200
I will take the second query from this list.

47
00:02:29.900 --> 00:02:32.800
It will be Google search engine query

48
00:02:32.800 --> 00:02:34.900
 for Microsoft SQL Server.

49
00:02:36.100 --> 00:02:37.600
I will copy this query.

50
00:02:38.500 --> 00:02:41.400
I will paste it in Google search and I

51
00:02:41.400 --> 00:02:44.400
 will check if Google indexed a

52
00:02:44.400 --> 00:02:47.900
 web page with a string indicating a

53
00:02:47.900 --> 00:02:50.800
 Microsoft SQL Server syntax error

54
00:02:50.800 --> 00:02:53.900
 on the domain hacking web applications.com.

55
00:02:57.600 --> 00:03:00.400
As you can see one web page has

56
00:03:00.400 --> 00:03:02.000
 been indexed by Google.

57
00:03:03.400 --> 00:03:04.800
Let's check what is inside?

58
00:03:06.100 --> 00:03:09.600
The Source error and stock Trace are presented

59
00:03:09.600 --> 00:03:10.800
 on this web page.

60
00:03:11.400 --> 00:03:13.800
Let's focus on the source error.

61
00:03:14.500 --> 00:03:17.800
There are five lines of the source code and

62
00:03:17.800 --> 00:03:21.100
 in the line number 47 the connection

63
00:03:20.100 --> 00:03:23.500
 string to the database is defined.

64
00:03:24.400 --> 00:03:27.400
Let's analyze the details of this connection

65
00:03:27.400 --> 00:03:28.000
 string.

66
00:03:29.400 --> 00:03:32.200
As you can see there are credentials to

67
00:03:32.200 --> 00:03:35.900
 the database and it clearly shows how easily

68
00:03:35.900 --> 00:03:38.400
 you can use Google hacking to find

69
00:03:38.400 --> 00:03:42.000
 SQL syntax errors with sensitive data

70
00:03:41.500 --> 00:03:44.600
 in publicly exposed web

71
00:03:44.600 --> 00:03:44.900
 pages.

72
00:03:46.300 --> 00:03:49.700
Okay. Now we are done with this demo. So

73
00:03:49.700 --> 00:03:52.100
 let me jump to the next one and let

74
00:03:52.100 --> 00:03:55.400
 me show you how Google hacking can be used for

75
00:03:55.400 --> 00:03:58.600
 finding publicly exposed backup files.
