WEBVTT - This file was automatically generated by VIMEO

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

1
00:00:07.600 --> 00:00:10.400
 this video we are going to see the scan type

2
00:00:10.400 --> 00:00:11.800
 which is null scan.

3
00:00:12.400 --> 00:00:15.700
So the syntax of doing the null scan is and map

4
00:00:15.700 --> 00:00:18.500
 hyphen SN the target IP address

5
00:00:18.500 --> 00:00:19.700
 and the port number.

6
00:00:20.700 --> 00:00:23.600
This is one of the very still these scan that

7
00:00:23.600 --> 00:00:26.400
 sets all the TCP had a Flags to off

8
00:00:26.400 --> 00:00:29.200
 or null. That's why this is called as

9
00:00:29.200 --> 00:00:30.200
 anal scan.

10
00:00:30.800 --> 00:00:33.300
This is not normally a valid packet

11
00:00:33.300 --> 00:00:36.300
 and some host will not know what to

12
00:00:36.300 --> 00:00:37.600
 do with this type of scan.

13
00:00:38.300 --> 00:00:41.400
Windows operating systems are in this group and scanning

14
00:00:41.400 --> 00:00:44.500
 them with Nils scans will produce unreliable results.

15
00:00:45.400 --> 00:00:48.100
However for non Windows servers protected by

16
00:00:48.100 --> 00:00:51.200
 firewalls, this can be a best way to get

17
00:00:51.200 --> 00:00:51.500
 through.

18
00:00:52.800 --> 00:00:55.500
Remember Nils scans. No flex

19
00:00:55.500 --> 00:00:57.300
 TCP are set

20
00:01:00.900 --> 00:01:03.500
So whenever you scan any

21
00:01:03.500 --> 00:01:07.000
 Target machine using null scan are if

22
00:01:06.400 --> 00:01:09.700
 a reset packet is received then

23
00:01:09.700 --> 00:01:11.400
 the port is considered as closed.

24
00:01:12.200 --> 00:01:15.000
While if no response is received then it is

25
00:01:15.600 --> 00:01:17.400
 considered as open or filtered.

26
00:01:17.900 --> 00:01:20.500
The port is generally marked filter

27
00:01:20.500 --> 00:01:23.900
 if an icmp unreachable error

28
00:01:23.900 --> 00:01:24.800
 is generated.

29
00:01:25.700 --> 00:01:28.500
So take a note if Port is

30
00:01:28.500 --> 00:01:31.200
 closed. It replies with resetac and if it

31
00:01:31.200 --> 00:01:32.600
 is open, it does not reply.

32
00:01:34.500 --> 00:01:37.900
So what actually happens when you run and null

33
00:01:37.900 --> 00:01:38.200
 scan?

34
00:01:39.400 --> 00:01:42.600
So as you can see on the left hand side is the nmap machine

35
00:01:42.600 --> 00:01:45.300
 and on the right hand side is the server which we

36
00:01:45.300 --> 00:01:46.000
 are going to scan.

37
00:01:47.200 --> 00:01:51.700
So the first request that has been sent is a TCP null

38
00:01:50.700 --> 00:01:53.500
 flag are set. So

39
00:01:53.500 --> 00:01:55.900
 no flags are set over here.

40
00:01:57.600 --> 00:02:01.100
So if we get a reply with reset or

41
00:02:00.100 --> 00:02:04.400
 AC that means that that

42
00:02:03.400 --> 00:02:06.500
 Port is considered if you

43
00:02:06.500 --> 00:02:09.200
 do not receive a reply or

44
00:02:09.200 --> 00:02:12.500
 response, then we consider it as the port is

45
00:02:12.500 --> 00:02:14.000
 open or filtered.

46
00:02:15.800 --> 00:02:18.600
So, let's see a Wireshark packet breakdown of

47
00:02:18.600 --> 00:02:22.500
 this type of scan. So as you can see a nun

48
00:02:22.500 --> 00:02:25.700
 packet was sent for the port 23 and

49
00:02:25.700 --> 00:02:28.400
 a reset was received which means

50
00:02:28.400 --> 00:02:29.600
 the port is closed.

51
00:02:30.300 --> 00:02:33.400
Similarly again a nun packet was sent

52
00:02:33.400 --> 00:02:36.500
 for 22 and it was again same for 22. If

53
00:02:36.500 --> 00:02:39.400
 we do not receive a reset. That means that

54
00:02:39.400 --> 00:02:42.100
 particular Port is either open or filtered.

55
00:02:45.200 --> 00:02:48.300
So what are the advantages and disadvantages of null scan?

56
00:02:48.900 --> 00:02:51.000
The advantage is it is still

57
00:02:51.300 --> 00:02:53.700
 the and can bypass some of the firewalls.

58
00:02:54.300 --> 00:02:57.400
What is the disadvantage it is unreliable at

59
00:02:57.400 --> 00:03:00.200
 many times because we cannot identify the

60
00:03:00.200 --> 00:03:02.100
 exact status of the port.

61
00:03:03.900 --> 00:03:06.500
So now it is the Practical time and let's see

62
00:03:06.500 --> 00:03:08.900
 how we can perform null scan.

63
00:03:11.600 --> 00:03:13.000
So as you can see over here.

64
00:03:14.500 --> 00:03:18.800
I have written the command on my terminal as nmap. -sn.

65
00:03:19.400 --> 00:03:22.600
And the target server I want to scan and hyphen V.

66
00:03:29.300 --> 00:03:32.900
As you can see the scan has initiated successfully and

67
00:03:32.900 --> 00:03:35.500
 you can read over here. This is unnul scan.

68
00:03:37.400 --> 00:03:41.200
You can see the host is up, but we have not identified

69
00:03:40.200 --> 00:03:43.600
 the exact status of any port.

70
00:03:44.700 --> 00:03:47.300
You can see 500 ports are

71
00:03:47.300 --> 00:03:49.600
 closed or open or filtered.

72
00:03:50.600 --> 00:03:52.000
This means we

73
00:03:53.400 --> 00:03:56.400
Did not receive an empty response for

74
00:03:56.400 --> 00:03:59.900
 any of the port we have received a reset

75
00:03:59.900 --> 00:04:03.000
 for all the ports as

76
00:04:02.300 --> 00:04:05.100
 you can see over here. None has been

77
00:04:05.100 --> 00:04:09.400
 sent for all the ports, but we have received reset

78
00:04:08.400 --> 00:04:12.600
 for all the ports simultaneously

79
00:04:11.600 --> 00:04:14.800
 that means and map

80
00:04:14.800 --> 00:04:18.200
 has failed to identify the correct Port status.

81
00:04:25.300 --> 00:04:28.100
So I hope you guys understood how we can

82
00:04:28.100 --> 00:04:31.900
 perform null scan and how it can be unreliable at

83
00:04:31.900 --> 00:04:34.600
 some times, but it is all also helpful.

84
00:04:34.600 --> 00:04:37.600
 Sometimes in bypassing the firewalls. Thank you.
