WEBVTT - This file was automatically generated by VIMEO

0
00:00:04.800 --> 00:00:08.300
Hello everyone. So in

1
00:00:07.300 --> 00:00:10.700
 the previous video we saw how can

2
00:00:10.700 --> 00:00:13.400
 you identify sensitive directories on

3
00:00:13.400 --> 00:00:16.000
 any Target for your penetration testing?

4
00:00:16.700 --> 00:00:17.400
in this video

5
00:00:18.300 --> 00:00:21.900
How can we not use diss search to identify the

6
00:00:21.900 --> 00:00:24.600
 websites which contains sensitive directories?

7
00:00:24.600 --> 00:00:27.700
 This is one of the most used tools which

8
00:00:27.700 --> 00:00:30.400
 is used for brute forcing the

9
00:00:30.400 --> 00:00:33.800
 directories and identifying the sensitive directories and

10
00:00:33.800 --> 00:00:36.600
 getting sensitive data from those territories.

11
00:00:37.300 --> 00:00:39.100
So the format of doing this particular

12
00:00:41.300 --> 00:00:44.300
scan is python dissearch dot Pi

13
00:00:44.900 --> 00:00:47.500
 - U stands for the URL and you can give the URL

14
00:00:47.500 --> 00:00:48.400
 that you want to scan.

15
00:00:49.200 --> 00:00:52.400
One interesting thing about dir search is you have

16
00:00:52.400 --> 00:00:55.400
 to add hyphen e - e stands for

17
00:00:55.400 --> 00:00:58.700
 the extensions that you want to look for. So it

18
00:00:58.700 --> 00:01:02.000
 will also look for the extension PHP zip

19
00:01:01.600 --> 00:01:02.900
 in case of

20
00:01:04.100 --> 00:01:07.300
there are some files of source code which are

21
00:01:07.300 --> 00:01:09.600
 zipped by the developer.

22
00:01:10.500 --> 00:01:14.500
We can also get those and download those aspx dot

23
00:01:13.500 --> 00:01:16.600
 EnV files the environment files.

24
00:01:17.500 --> 00:01:20.300
Sometimes XML files because the developer

25
00:01:20.300 --> 00:01:23.500
 may have stored some sensitive username password

26
00:01:23.500 --> 00:01:26.300
 credentials tokens API Keys Etc

27
00:01:26.300 --> 00:01:29.100
 backup files. Sometimes they tend to

28
00:01:29.100 --> 00:01:33.100
 make backups of their logs and configuration

29
00:01:32.100 --> 00:01:35.200
 files. So we are going to search for

30
00:01:35.200 --> 00:01:37.700
 these menu files onto this particular Target.

31
00:01:38.600 --> 00:01:41.600
So once I hit enter you can see diar search

32
00:01:41.600 --> 00:01:44.500
 will start on to this particular Target. So

33
00:01:44.500 --> 00:01:45.900
 as you can see, this is the output.

34
00:01:47.300 --> 00:01:51.600
4 0 3 stands for the request was forbidden 3

35
00:01:50.600 --> 00:01:53.300
 0 1 stands for it was

36
00:01:53.300 --> 00:01:57.200
 a redirect for that particular request and

37
00:01:56.200 --> 00:02:00.000
 200. Okay is the server

38
00:01:59.400 --> 00:02:02.600
 is able to fulfill our request so

39
00:02:02.600 --> 00:02:05.200
 we did not got anything sensitive over

40
00:02:05.200 --> 00:02:08.600
 here. No problem. Let's go to the next Target.

41
00:02:08.600 --> 00:02:11.200
 So in as you can see over here in the

42
00:02:11.200 --> 00:02:13.600
 next Target we have mirror Dot.

43
00:02:14.500 --> 00:02:16.200
Macomb net Dot

44
00:02:16.600 --> 00:02:17.000
net

45
00:02:18.200 --> 00:02:20.600
Over here we see that.

46
00:02:22.700 --> 00:02:25.600
We got some of the interesting results over

47
00:02:25.600 --> 00:02:28.300
 here as you can see 200 OK for

48
00:02:28.900 --> 00:02:31.600
 ETC past WD and you all know

49
00:02:31.300 --> 00:02:35.100
 Etc passed WD is a very very sensitive

50
00:02:34.100 --> 00:02:37.300
 directory into our Linux machine.

51
00:02:38.100 --> 00:02:42.100
Where it contains all the information about our

52
00:02:41.100 --> 00:02:43.900
 users which we have created.

53
00:02:45.600 --> 00:02:48.700
So in my computer, I'm just going to read this file. You can

54
00:02:48.700 --> 00:02:51.400
 only read this file. Once you are a

55
00:02:51.400 --> 00:02:54.300
 super user or a root user. So I quickly switch to the

56
00:02:54.300 --> 00:02:57.500
 super user. And now when I'm reading this file you

57
00:02:57.500 --> 00:02:57.700
 can see

58
00:02:59.100 --> 00:03:02.900
The users which are created into my computer. So

59
00:03:02.900 --> 00:03:05.300
 these are all the users which are running right

60
00:03:05.300 --> 00:03:06.300
 now into my computer.

61
00:03:11.300 --> 00:03:14.400
Yes. All right. So what I did I quickly went

62
00:03:14.400 --> 00:03:16.100
 to that particular link.

63
00:03:17.100 --> 00:03:20.400
That we got from the dir search. And once I

64
00:03:20.400 --> 00:03:23.600
 click that link, you can see here. I can see the past WD file.

65
00:03:23.600 --> 00:03:26.400
 I will just download this file. You can

66
00:03:26.400 --> 00:03:29.000
 see it is downloaded. Let me just open up and check.

67
00:03:30.100 --> 00:03:33.500
So I will just right click open with text edit to

68
00:03:33.500 --> 00:03:36.200
 see what is there inside and you can see over here.

69
00:03:36.200 --> 00:03:37.200
 I'll just zoom it.

70
00:03:37.900 --> 00:03:40.500
We can see the server which is running is.

71
00:03:42.400 --> 00:03:46.000
Free BSD you can see the machine is by the name of Peter.

72
00:03:46.700 --> 00:03:49.600
You can see these are the users which are created into that

73
00:03:49.600 --> 00:03:51.100
 particular machine.

74
00:03:52.100 --> 00:03:55.900
So this is enough information for any program to

75
00:03:55.900 --> 00:03:58.600
 send to show the severity because this

76
00:03:58.600 --> 00:04:01.100
 file is considered very very sensitive.

77
00:04:01.900 --> 00:04:04.700
So how I hope you guys understood this video. Thank you.
