WEBVTT - This file was automatically generated by VIMEO

0
00:00:06.700 --> 00:00:09.800
In this clip. I will mention one report

1
00:00:09.800 --> 00:00:12.500
 that clearly shows the power of Google

2
00:00:12.500 --> 00:00:13.100
 hacking.

3
00:00:14.200 --> 00:00:18.500
Sometime ago a researcher discovered that access

4
00:00:17.500 --> 00:00:20.600
 tokens to Microsoft the

5
00:00:20.600 --> 00:00:23.200
 armor social network where indexed by

6
00:00:23.200 --> 00:00:26.500
 Google and Google hacking could be

7
00:00:26.500 --> 00:00:29.300
 used to learn this very sensitive data.

8
00:00:30.500 --> 00:00:34.100
Yes, it was that simple the attacker

9
00:00:33.100 --> 00:00:37.000
 could create a Google search engine query

10
00:00:36.600 --> 00:00:39.700
 that the returns access tokens

11
00:00:39.700 --> 00:00:42.400
 to Microsoft Yammer and then

12
00:00:42.400 --> 00:00:46.200
 using this access tokens the attacker

13
00:00:45.200 --> 00:00:48.400
 could gain an authorized access

14
00:00:48.400 --> 00:00:50.300
 to the user's accounts.

15
00:00:51.500 --> 00:00:54.800
This critical vulnerability was detected by

16
00:00:54.800 --> 00:00:58.900
 a tick Khan from vulnerability laboratory

17
00:00:57.900 --> 00:01:01.700
 research team attic Khan

18
00:01:01.700 --> 00:01:04.900
 reported this vulnerability to Microsoft

19
00:01:04.900 --> 00:01:07.500
 security Response Center, and now

20
00:01:07.500 --> 00:01:09.800
 this vulnerability is fixed.

21
00:01:11.100 --> 00:01:15.400
It clearly shows the power of Google hacking and

22
00:01:14.400 --> 00:01:17.100
 I recommend you to take a look

23
00:01:17.100 --> 00:01:20.400
 at this report to see the details of

24
00:01:20.400 --> 00:01:21.600
 this vulnerability.

25
00:01:22.900 --> 00:01:25.400
Okay. Now we are done with this

26
00:01:25.400 --> 00:01:28.200
 clip and in the next one. I will

27
00:01:28.200 --> 00:01:31.600
 tell you how to prevent Google indexing from

28
00:01:31.600 --> 00:01:32.400
 happening.
