<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: WiFi Ownage</title>
	<atom:link href="http://www.gnucitizen.org/blog/wifi-ownage/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gnucitizen.org/blog/wifi-ownage/</link>
	<description>Information Security Think Tank</description>
	<lastBuildDate>Mon, 12 Dec 2011 19:56:03 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: pdp</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-126136</link>
		<dc:creator>pdp</dc:creator>
		<pubDate>Wed, 25 Feb 2009 10:10:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-126136</guid>
		<description>you are right! I guess the intention was to write something that runs without too much configuration.</description>
		<content:encoded><![CDATA[<p>you are right! I guess the intention was to write something that runs without too much configuration.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lljkrieg</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-126102</link>
		<dc:creator>lljkrieg</dc:creator>
		<pubDate>Tue, 24 Feb 2009 12:59:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-126102</guid>
		<description>DNS hijacking is certainly an interesting and potentially catastrophic issue for internet users but why reinvent the wheel to exploit the results?

It is possible for an attacker controlled DNS server that supports wildcards, such as bind, to force all domains to resolve to the attacker&#039;s web server. The web server can then proxy the real hostname and inject data into the stream, or load phishing pages for specific sites (sites which don&#039;t allow proxies perhaps?), or launch malware, etc.

This way user HTTP requests can easily be logged and a simple script on the web server could immediately change the payload without having to worry about DNS lease length.</description>
		<content:encoded><![CDATA[<p>DNS hijacking is certainly an interesting and potentially catastrophic issue for internet users but why reinvent the wheel to exploit the results?</p>
<p>It is possible for an attacker controlled DNS server that supports wildcards, such as bind, to force all domains to resolve to the attacker&#8217;s web server. The web server can then proxy the real hostname and inject data into the stream, or load phishing pages for specific sites (sites which don&#8217;t allow proxies perhaps?), or launch malware, etc.</p>
<p>This way user HTTP requests can easily be logged and a simple script on the web server could immediately change the payload without having to worry about DNS lease length.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: CoffeeAddict &#187; 3 keer kloppen&#8230;</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-122895</link>
		<dc:creator>CoffeeAddict &#187; 3 keer kloppen&#8230;</dc:creator>
		<pubDate>Wed, 09 Jul 2008 08:48:30 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-122895</guid>
		<description>[...] Door het &#8220;nieuwe&#8221; en gapende gat in UPnP kan een slimme hacker op je router de DNS instellingen wijzigingen om naar haar eigen DNS te wijzen die mijn.postbank.nl resolved naar een perfecte look-a-like op de eigen server van onze vriendelijke hacker. De rest van de DNS requests worden keurig netjes uitbesteed zodat google ook echt google is. (Meer info hier) [...]</description>
		<content:encoded><![CDATA[<p>[...] Door het &#8220;nieuwe&#8221; en gapende gat in UPnP kan een slimme hacker op je router de DNS instellingen wijzigingen om naar haar eigen DNS te wijzen die mijn.postbank.nl resolved naar een perfecte look-a-like op de eigen server van onze vriendelijke hacker. De rest van de DNS requests worden keurig netjes uitbesteed zodat google ook echt google is. (Meer info hier) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rezn</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-113189</link>
		<dc:creator>rezn</dc:creator>
		<pubDate>Mon, 11 Feb 2008 16:14:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-113189</guid>
		<description>This code may be helpful in further exploring malicious DNS server creation: 

http://www.dnspython.org/</description>
		<content:encoded><![CDATA[<p>This code may be helpful in further exploring malicious DNS server creation: </p>
<p><a href="http://www.dnspython.org/" rel="nofollow">http://www.dnspython.org/</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: fazed</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-112851</link>
		<dc:creator>fazed</dc:creator>
		<pubDate>Mon, 11 Feb 2008 01:21:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-112851</guid>
		<description>@squid:
what is meant is that I went through both being a script kiddie and as I learned more a blackhat.

thanks for the comments everyone

@Adrian:
I was thinking about creating a more complex script which can also redirect different entered urls to different IP&#039;s/vHost&#039;s and let any that are not listed in this &quot;host&quot; file go to the correct location but this script is just a PoC.</description>
		<content:encoded><![CDATA[<p>@squid:<br />
what is meant is that I went through both being a script kiddie and as I learned more a blackhat.</p>
<p>thanks for the comments everyone</p>
<p>@Adrian:<br />
I was thinking about creating a more complex script which can also redirect different entered urls to different IP&#8217;s/vHost&#8217;s and let any that are not listed in this &#8220;host&#8221; file go to the correct location but this script is just a PoC.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Kecoak Elektronik Indonesia &#187; Blog Archive &#187; DNS, the betrayer!</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-112680</link>
		<dc:creator>Kecoak Elektronik Indonesia &#187; Blog Archive &#187; DNS, the betrayer!</dc:creator>
		<pubDate>Sun, 10 Feb 2008 17:23:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-112680</guid>
		<description>[...] juga jika melihat tulisan fazed di blog GNUCITIZEN berikut ini, memainkan informasi DNS untuk menguasai WIFI connection (yeah&#8230;yeah&#8230;wifi-ownage, [...]</description>
		<content:encoded><![CDATA[<p>[...] juga jika melihat tulisan fazed di blog GNUCITIZEN berikut ini, memainkan informasi DNS untuk menguasai WIFI connection (yeah&#8230;yeah&#8230;wifi-ownage, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sid</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-111612</link>
		<dc:creator>Sid</dc:creator>
		<pubDate>Fri, 08 Feb 2008 07:46:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-111612</guid>
		<description>@Christopher: traffic injection attacks on WiFi work like a charm on WEP networks too, as long as you know the key. Not a big requirement after all ;)

I could have Wifitap work on a WDS link as well, with an ugly hack I&#039;m not really proud of.

Getting back to the script, this attack is very like airpwn. This tool, demonstrated at Defcon 2004, catches HTTP requests for pictures and injects arbitrary replies. Very handy when you have... Let&#039;s say... A JPEG or PNG buffer overflow  on browser :) You can also reply &quot;GET /&quot; requests with a 301 or 302 that will redirect browser anywhere you want, like a metasploit loaded with whatever client side exploit you may like.

Check http://sid.rstack.org/pres/0608_BCS_OpenWireless.pdf slides 33 to 47.</description>
		<content:encoded><![CDATA[<p>@Christopher: traffic injection attacks on WiFi work like a charm on WEP networks too, as long as you know the key. Not a big requirement after all ;)</p>
<p>I could have Wifitap work on a WDS link as well, with an ugly hack I&#8217;m not really proud of.</p>
<p>Getting back to the script, this attack is very like airpwn. This tool, demonstrated at Defcon 2004, catches HTTP requests for pictures and injects arbitrary replies. Very handy when you have&#8230; Let&#8217;s say&#8230; A JPEG or PNG buffer overflow  on browser :) You can also reply &#8220;GET /&#8221; requests with a 301 or 302 that will redirect browser anywhere you want, like a metasploit loaded with whatever client side exploit you may like.</p>
<p>Check <a href="http://sid.rstack.org/pres/0608_BCS_OpenWireless.pdf" rel="nofollow">http://sid.rstack.org/pres/060.....reless.pdf</a> slides 33 to 47.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pdp</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-111607</link>
		<dc:creator>pdp</dc:creator>
		<pubDate>Fri, 08 Feb 2008 07:29:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-111607</guid>
		<description>sqid, it should have been blackhat script kiddie (no slash). And yes it makes a perfect sense. Blackhat can be used as a noun or adjective. Cheers.</description>
		<content:encoded><![CDATA[<p>sqid, it should have been blackhat script kiddie (no slash). And yes it makes a perfect sense. Blackhat can be used as a noun or adjective. Cheers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Christopher Haney</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-111542</link>
		<dc:creator>Christopher Haney</dc:creator>
		<pubDate>Fri, 08 Feb 2008 03:28:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-111542</guid>
		<description>Would this attack also work is you simply used (for example) a WRT54G with DD-WRT as a repeater and simply acted as a second access point to the WEP free AP?</description>
		<content:encoded><![CDATA[<p>Would this attack also work is you simply used (for example) a WRT54G with DD-WRT as a repeater and simply acted as a second access point to the WEP free AP?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sqid</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-111502</link>
		<dc:creator>sqid</dc:creator>
		<pubDate>Fri, 08 Feb 2008 01:26:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-111502</guid>
		<description>&quot;Sam started as a blackhat/script kiddie but soon he has learned a life lesson when he broke into a big football(soccer) leagues site. Sam did not serve any sentence but he had to pay a hefty fine. This is how he turned into a whitehat...&quot;

You make it sounds like Gnucitizen is similar to Alcoholics Anonymous for blackhats. Also, by grouping blackhat and script-kiddie together, you make it sound like they are related to another, when, in fact, they are not. Could you give me some good reasoning on that?</description>
		<content:encoded><![CDATA[<p>&#8220;Sam started as a blackhat/script kiddie but soon he has learned a life lesson when he broke into a big football(soccer) leagues site. Sam did not serve any sentence but he had to pay a hefty fine. This is how he turned into a whitehat&#8230;&#8221;</p>
<p>You make it sounds like Gnucitizen is similar to Alcoholics Anonymous for blackhats. Also, by grouping blackhat and script-kiddie together, you make it sound like they are related to another, when, in fact, they are not. Could you give me some good reasoning on that?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Pastor</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-111479</link>
		<dc:creator>Adrian Pastor</dc:creator>
		<pubDate>Thu, 07 Feb 2008 21:14:03 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-111479</guid>
		<description>@Sid - sounds interesting!.</description>
		<content:encoded><![CDATA[<p>@Sid &#8211; sounds interesting!.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sid</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-111335</link>
		<dc:creator>Sid</dc:creator>
		<pubDate>Thu, 07 Feb 2008 15:48:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-111335</guid>
		<description>I wrote 3 scripts in the same spirit aside of Wifitap that can be foudn in the same tarball:

wifiping.py is just a PoC that answers ping requests on the fly
wifiarp.py that poisons ARP requests on the fly
wifidns.py that roughly does the same as yours

Everything based on Scapy.</description>
		<content:encoded><![CDATA[<p>I wrote 3 scripts in the same spirit aside of Wifitap that can be foudn in the same tarball:</p>
<p>wifiping.py is just a PoC that answers ping requests on the fly<br />
wifiarp.py that poisons ARP requests on the fly<br />
wifidns.py that roughly does the same as yours</p>
<p>Everything based on Scapy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Pastor</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-111289</link>
		<dc:creator>Adrian Pastor</dc:creator>
		<pubDate>Thu, 07 Feb 2008 13:42:49 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-111289</guid>
		<description>The script works like a charm, just tested it. The idea is that any domain names resolve to one IP address chosen by the attacker.

It&#039;d also be useful to write a variation of the tool that only makes certain domain names resolve to the evil IP address, and simply query a public DNS server for all other IPs. For instance, maybe the attacker is only interested in poisoning www.trustedbank.foo and wants all other domain names to resolve to legitimate IP addresses.</description>
		<content:encoded><![CDATA[<p>The script works like a charm, just tested it. The idea is that any domain names resolve to one IP address chosen by the attacker.</p>
<p>It&#8217;d also be useful to write a variation of the tool that only makes certain domain names resolve to the evil IP address, and simply query a public DNS server for all other IPs. For instance, maybe the attacker is only interested in poisoning <a href="http://www.trustedbank.foo" rel="nofollow">http://www.trustedbank.foo</a> and wants all other domain names to resolve to legitimate IP addresses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Pastor</title>
		<link>http://www.gnucitizen.org/blog/wifi-ownage/comment-page-1/#comment-111284</link>
		<dc:creator>Adrian Pastor</dc:creator>
		<pubDate>Thu, 07 Feb 2008 13:30:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/wifi-ownage#comment-111284</guid>
		<description>That&#039;s a quite handy script, I will play around with it later on today!</description>
		<content:encoded><![CDATA[<p>That&#8217;s a quite handy script, I will play around with it later on today!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

