WEBVTT - This file was automatically generated by VIMEO

0
00:00:03.800 --> 00:00:06.900
In this lesson, we are going to understand about the

1
00:00:06.900 --> 00:00:09.300
 third fuzzing technique, which is known

2
00:00:09.300 --> 00:00:10.600
 as battering ram.

3
00:00:11.600 --> 00:00:13.000
So what is battering ram?

4
00:00:13.700 --> 00:00:17.400
This fuzzing technique only supplies or

5
00:00:17.400 --> 00:00:20.400
 only supports a single payload set.

6
00:00:21.500 --> 00:00:24.400
When you supply that payload using a word list,

7
00:00:24.400 --> 00:00:27.500
 it uses the same payload for all the positions that

8
00:00:27.500 --> 00:00:30.800
 have been added in our custom template.

9
00:00:32.900 --> 00:00:35.200
So it is the Practical time and let's see

10
00:00:35.200 --> 00:00:39.200
 how you can use the technique which is battering ram.

11
00:00:41.400 --> 00:00:45.100
So you can see over here. I have written a yml

12
00:00:44.100 --> 00:00:48.100
 template which is a nuclei template named

13
00:00:47.100 --> 00:00:50.800
 as fuzzing underscore battering ram

14
00:00:50.800 --> 00:00:53.200
 dot. Yml, which can also be

15
00:00:53.200 --> 00:00:57.200
 seen in the ID block. This is the information block. Let's

16
00:00:56.200 --> 00:00:59.200
 see the request block. This is

17
00:00:59.200 --> 00:01:01.000
 a HTTP raw request.

18
00:01:01.800 --> 00:01:02.700
We can see over here.

19
00:01:03.400 --> 00:01:06.800
This is a post request here as we

20
00:01:06.800 --> 00:01:09.400
 are using a battering ram fuzzing Technique.

21
00:01:09.400 --> 00:01:12.600
 We can only specify one payload position.

22
00:01:13.700 --> 00:01:16.900
So let's assume I already know the username for

23
00:01:16.900 --> 00:01:19.600
 this web application. The username is

24
00:01:19.600 --> 00:01:22.300
 admin. I don't know the password. So I'm

25
00:01:22.300 --> 00:01:25.400
 going to specify a parameter underscore a

26
00:01:25.400 --> 00:01:25.900
 over here.

27
00:01:26.600 --> 00:01:28.400
And rest are the headers.

28
00:01:29.300 --> 00:01:32.400
You can also see the host has been supplied to the host name.

29
00:01:33.200 --> 00:01:36.300
Let's scroll down to the payloads part in the

30
00:01:36.300 --> 00:01:39.100
 payloads block. We can see we have supplied and

31
00:01:39.100 --> 00:01:43.600
 said parameter a is password.txt

32
00:01:42.600 --> 00:01:46.000
 word list which means each

33
00:01:45.600 --> 00:01:48.300
 password from the word list should be

34
00:01:48.300 --> 00:01:51.100
 replaced automatically at this position, which is

35
00:01:51.100 --> 00:01:55.000
 parameter a and we have said already that parameter

36
00:01:54.100 --> 00:01:58.300
 a is the value of the password parameter.

37
00:01:58.900 --> 00:02:01.700
The matches condition Remains the Same that

38
00:02:01.700 --> 00:02:04.000
 we want to match success as a word

39
00:02:04.400 --> 00:02:08.600
 in the body and we also want to match and Status

40
00:02:07.600 --> 00:02:10.200
 which is 200, okay.

41
00:02:11.300 --> 00:02:14.600
So let's run this template and let us see the output

42
00:02:14.600 --> 00:02:17.100
 so I'm going to go to my terminal quickly.

43
00:02:26.200 --> 00:02:29.700
And I'm going to specify battering ram Dot. Yml.

44
00:02:30.800 --> 00:02:32.900
I'm also going to specify hyphen V.

45
00:02:33.700 --> 00:02:36.700
To show what exactly is happening behind?

46
00:02:37.700 --> 00:02:41.000
You can see over here the first request contains

47
00:02:40.100 --> 00:02:43.600
 the username as admin and password as

48
00:02:43.600 --> 00:02:44.100
 demo.

49
00:02:44.800 --> 00:02:47.400
The second password is Tomcat. The third password

50
00:02:47.400 --> 00:02:50.500
 is hackedify for this password. And so

51
00:02:50.500 --> 00:02:53.600
 on here in this specific request. We

52
00:02:53.600 --> 00:02:56.700
 are able to successfully identify the correct username

53
00:02:56.700 --> 00:03:00.000
 that we already knew and supplied but

54
00:02:59.400 --> 00:03:03.000
 the password was found using fuzzing

55
00:03:02.400 --> 00:03:05.700
 technique using this specific technique

56
00:03:05.700 --> 00:03:08.700
 and you can see the parameter a equals to

57
00:03:08.700 --> 00:03:11.200
 admin is the correct one and hence. We

58
00:03:11.200 --> 00:03:12.800
 are able to get this output.

59
00:03:14.300 --> 00:03:16.500
You can also examine the same thing.

60
00:03:17.900 --> 00:03:20.300
In these requests as

61
00:03:20.300 --> 00:03:23.700
 well. You can see this is the specific request

62
00:03:23.700 --> 00:03:26.900
 that was sent in which the admin username

63
00:03:26.900 --> 00:03:29.400
 was already known and was

64
00:03:29.400 --> 00:03:32.500
 hardcoded in the template, but we first for this

65
00:03:32.500 --> 00:03:36.100
 specific position, which is password equals

66
00:03:35.100 --> 00:03:38.600
 to and we successfully got a success

67
00:03:38.600 --> 00:03:39.300
 message.

68
00:03:40.200 --> 00:03:43.300
So I hope you guys understood that how you can

69
00:03:43.300 --> 00:03:46.200
 use battering ram fuzzing technique to

70
00:03:46.200 --> 00:03:47.700
 First Target. Thank you.
