Question: 1 3 6 5 1 0 9 . 7 9 6 3 8 0 1 0 . 2 5 2 . 1 7 4 .

1365109.79638010.252.174.18823.20.23.147 SSHv2105 Server: Protocol SSH-2.0-OpenssH_1367109.79842023.20.23.14710.252.174.188 SSHV287 Client: Protocol (SSH-2.0-OpenSSH_1369109.80044310.252.174.18823.20.23.147SSHV21050 Server: Key Exchange Init1370109.80261823.20.23.14710.252.174.188 SSHV2626 Client: Key Exchange Init1372109.84312123.20.23.14710.252.174.188 SSHV290 Client:Diffie-Hellman Group Exchar1374109.84499910.252.174.18823.20.23.147 SSHv2218 Server: Diffie-Hellman Group Exchal1375109.85024923.20.23.14710.252.174.188 SSHV2210 Client: Diffie-Hellman Group Exchal1376109.85279110.252.174.18823.20.23.147 SSHv2786 Server: Diffie-Hellman Group Exchal1377109.85838123.20.23.14710.252.174.188 SSHV290 Client:New Keys1379109.89878523.20.23.14710.252.174.188 SSHV2118 Client: Encrypted packet (len=52)1381109.89887410.252.174.18823.20.23.147SSHv2118 Server:Encryptedpacket (len=52)1382109.90084023.20.23.14710.252.174.188 SSHV2150 Client:Encrypted packet(Len=84)1383109.91510310.252.174.18823.20.23.147SSHV2102 Server:Encrypted packet (len=36)1384109.91739623.20.23.14710.252.174.188 SSHV2134 Client:Encryptedpacket (len=68)1386110.44316910.252.174.18823.20.23.147SSHV2118 Server:Encryptedpacket(Len=52)1387110.44547823.20.23.14710.252.174.188 SSHV2118 Client:Encryptedpacket (len=52)1389110.44689410.252.174.18823.20.23.147SSHV2154 Server:Encryptedpacket (len=88)1390110.45355710.252.174.18823.20.23.147SSHv2198 Server:Encryptedpacket (len=132)1391110.45407210.252.174.18823.20.23.147SSHv2166 Server:Encryptedpacket (len=100)1392110.45474310.252.174.18823.20.23.147SSHv2102 Server:Encrypted packet (len=36)1393110.45488010.252.174.18823.20.23.147SSHv2238 Server:Encrypted packet (len=172)1396110.45736923.20.23.14710.252.174.188 SSHV2186 Client:Encryptedpacket (len=120)1397110.45759710.252.174.18823.20.23.147SSHv2118 Server:Encryptedpacket(Len=52)1398110.45941223.20.23.14710.252.174.188 SSHV2134 Client: Encrypted packet (len=68)1399110.46071810.252.174.18823.20.23.147 SSHV2154 Server: Encrypted packet (len=88)1400110.46437410.252.174.18823.20.23.147SSHV2198 Server: Encryptedpacket (len=132)1402110.46686710.252.174.18823.20.23.147SSHv2230 Server:Encryptedpacket(Len=164)1403110.46775410.252.174.18823.20.23.147SSHV2102 Server: Encrypted packet (len=36)1404110.46794210.252.174.18823.20.23.147SSHv2238 Server:Encryptedpacket (len=172)
1Identify the Brute Force Attempt:Look for multiple failed login attempts. These can be identified by repeated SSH packets with the same source and destination IP addresses.Note the time intervals between these attempts. Brute force attacks often have very short intervals between login attempts.2Analyze the Source and Destination:Identify the source IP address of the attacker.Identify the destination IP address of the target server.3Examine the Payload:Right-click on a packet and select Follow->TCP Stream to view the payload data.Look for patterns or repeated attempts in the payload that indicate a brute force attack.4Answer the Following Questions:Q1: What is the source IP address of the attacker?Q2: What is the destination IP address of the target server?Q3: How many login attempts were made?Q4: What is the time interval between each login attempt?Q5: Based on the packet data, what can you infer about the attackers strategy?5Document Your Findings:Summarize your findings in a report.Include screenshots of relevant Wireshark windows and packet details.

Step by Step Solution

There are 3 Steps involved in it

1 Expert Approved Answer
Step: 1 Unlock blur-text-image
Question Has Been Solved by an Expert!

Get step-by-step solutions from verified subject matter experts

Step: 2 Unlock
Step: 3 Unlock

Students Have Also Explored These Related Programming Questions!