MITM Labs/Dsniffing Over Wifi - Revision history

Admin: /* Failure */

2017-09-09T08:11:49Z

Failure

← Older revision		Revision as of 08:11, 9 September 2017
Line 205:		Line 205:
	==Failure==		==Failure==

	~~I have no clue~~ why this attack failed.		Not exactly sure why this attack failed.

	The services I use day-to-day, and most websites of Fortune 1000 companies, use HTTPS. A decade or so ago, when the dsniff toolkit was more popular, HTTPS was much less common and only used for websites that really needed it, like banks. Due to the rise of tools like dsniff, and more powerful computers, encryption is not such a computational burden, so HTTPS is more commonly deployed.		The services I use day-to-day, and most websites of Fortune 1000 companies, use HTTPS. A decade or so ago, when the dsniff toolkit was more popular, HTTPS was much less common and only used for websites that really needed it, like banks. Due to the rise of tools like dsniff, and more powerful computers, encryption is not such a computational burden, so HTTPS is more commonly deployed.

Admin: /* Failure */

2017-09-05T11:25:09Z

Failure

← Older revision		Revision as of 11:25, 5 September 2017
Line 207:		Line 207:
	I have no clue why this attack failed.		I have no clue why this attack failed.

	~~Honestly~~, ~~looking around at~~ most of the ~~services I use~~, it~~'s actually difficult~~ to ~~find~~ a ~~non-~~HTTPS ~~service~~. Not sure how far this type of attack will take you if your aim is to monitor traffic - ~~this neglects a large amount~~ of interesting traffic.		The services I use day-to-day, and most websites of Fortune 1000 companies, use HTTPS. A decade or so ago, when the dsniff toolkit was more popular, HTTPS was much less common and only used for websites that really needed it, like banks. Due to the rise of tools like dsniff, and more powerful computers, encryption is not such a computational burden, so HTTPS is more commonly deployed.

			Not sure how far this type of attack will take you if your aim is to monitor traffic - missing HTTPS traffic means missing most (if not all) of the interesting traffic. However, many insecure apps and web pages are still slow to jump on the HTTPS bandwagon, and a simple experiment with Firefox's "HTTPS Everywhere" extension can quickly reveal sites that do not implement HTTPS at all, or at least do not implement it by default.

	==Sheep Experiences The Slows==		==Sheep Experiences The Slows==

Admin at 10:24, 23 August 2016

2016-08-23T10:24:13Z

← Older revision		Revision as of 10:24, 23 August 2016
Line 220:		Line 220:

	=Flags=		=Flags=

			{{MITMFlag}}

	{{MITMLabsFlag}}		{{MITMLabsFlag}}

Admin: /* Step 3: ARP Poisoning Attack */

2016-08-21T08:17:05Z

Step 3: ARP Poisoning Attack

← Older revision		Revision as of 08:17, 21 August 2016
Line 142:		Line 142:

	When you run the program, the output will inform you of each faked ARP reply packet that is sent out: it will specify the MAC the faked ARP response was sent to, and what the faked ARP response says.		When you run the program, the output will inform you of each faked ARP reply packet that is sent out: it will specify the MAC the faked ARP response was sent to, and what the faked ARP response says.

			===Error===

			<pre>
			$ arpspoof -i wlan1 -t 192.168.0.7 -r 192.168.0.1 &> /dev/null
			$ arpspoof -i wlan1 -t 192.168.0.1 -r 192.168.0.7 &> /dev/null
			</pre>

	==Step 4: Run Dsniff==		==Step 4: Run Dsniff==

Admin: /* Sheep Experience */

2016-08-21T08:15:25Z

Sheep Experience

← Older revision		Revision as of 08:15, 21 August 2016
Line 202:		Line 202:
	Honestly, looking around at most of the services I use, it's actually difficult to find a non-HTTPS service. Not sure how far this type of attack will take you if your aim is to monitor traffic - this neglects a large amount of interesting traffic.		Honestly, looking around at most of the services I use, it's actually difficult to find a non-HTTPS service. Not sure how far this type of attack will take you if your aim is to monitor traffic - this neglects a large amount of interesting traffic.

	==Sheep ~~Experience~~==		==Sheep Experiences The Slows==

	The sheep experiences a very slow wifi connection - to the point where it's clear something fishy is happening. The sheep will either lose their patience or attempt to reconnect to the wifi, causing the entire attack to have to start again.		The sheep experiences a very slow wifi connection - to the point where it's clear something fishy is happening. The sheep will either lose their patience or attempt to reconnect to the wifi, causing the entire attack to have to start again.

			Looking at the packets, I see ah unge number of TCP retransmissions, missing ACK packets, and so on, so the requests are simply getting lost en route and/or droppd.

			Possible to look into this? What's causing TCP Dup ACK/TCP Suprious Transmission/TCP ACK unseen segment/etc...

			Increase packet transmission rates?

	=Flags=		=Flags=

	{{MITMLabsFlag}}		{{MITMLabsFlag}}

Admin: /* Failure */

2016-08-21T07:57:33Z

Failure

← Older revision		Revision as of 07:57, 21 August 2016
Line 198:		Line 198:
	==Failure==		==Failure==

	I have no clue why this attack failed~~, but honestly~~, looking around at most of the services I use, it's actually difficult to find a non-HTTPS service.		I have no clue why this attack failed.

			Honestly, looking around at most of the services I use, it's actually difficult to find a non-HTTPS service. Not sure how far this type of attack will take you if your aim is to monitor traffic - this neglects a large amount of interesting traffic.

	==Sheep Experience==		==Sheep Experience==

Admin: /* Sheep Experience */

2016-08-21T07:56:54Z

Sheep Experience

← Older revision		Revision as of 07:56, 21 August 2016
Line 195:		Line 195:

	=Debrief=		=Debrief=

			==Failure==

			I have no clue why this attack failed, but honestly, looking around at most of the services I use, it's actually difficult to find a non-HTTPS service.

	==Sheep Experience==		==Sheep Experience==

Admin: /* Failure */

2016-08-21T07:51:42Z

Failure

← Older revision		Revision as of 07:51, 21 August 2016
Line 192:		Line 192:

	Nope. Logging in with insecure nytimes.com login page on the sheep. MITM traffic passing through attacker. dsniff running. But absolutely zero results shown in the output.		Nope. Logging in with insecure nytimes.com login page on the sheep. MITM traffic passing through attacker. dsniff running. But absolutely zero results shown in the output.


			=Debrief=

			==Sheep Experience==

			The sheep experiences a very slow wifi connection - to the point where it's clear something fishy is happening. The sheep will either lose their patience or attempt to reconnect to the wifi, causing the entire attack to have to start again.

	=Flags=		=Flags=

	{{MITMLabsFlag}}		{{MITMLabsFlag}}

Admin: /* Step 5: Sheep Does Stuff and We Capture Booty */

2016-08-21T07:50:43Z

Step 5: Sheep Does Stuff and We Capture Booty

← Older revision		Revision as of 07:50, 21 August 2016
Line 188:		Line 188:

	Now visit a site that doesn't implement https, like the NYTimes. Log in while monitoring dsniff.		Now visit a site that doesn't implement https, like the NYTimes. Log in while monitoring dsniff.

			===Failure===

			Nope. Logging in with insecure nytimes.com login page on the sheep. MITM traffic passing through attacker. dsniff running. But absolutely zero results shown in the output.

	=Flags=		=Flags=

	{{MITMLabsFlag}}		{{MITMLabsFlag}}

Admin: /* Step 4: Run Dsniff */

2016-08-21T07:46:06Z

Step 4: Run Dsniff

← Older revision		Revision as of 07:46, 21 August 2016
Line 169:		Line 169:
	</pre>		</pre>

	It's probably better to run this specifying an output file~~, but this is not working. The output file has a line in it after I log in, but I can't actually show or display the credentials in the file, and they're encoded~~:		It's probably better to run this specifying an output file:

	<pre>		<pre>
	$ dsniff -i wlan1 -w goodies.txt		$ dsniff -i wlan1 -w goodies.txt
	</pre>		</pre>

			but this is not working. The output file has a line in it after I log in, but I can't actually show or display the credentials in the file, and they're encoded.

	==Step 5: Sheep Does Stuff and We Capture Booty==		==Step 5: Sheep Does Stuff and We Capture Booty==