<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>SourceSec Security Research &#187; Routers</title>
	<atom:link href="http://www.sourcesec.com/tag/routers/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.sourcesec.com</link>
	<description>Security research and vulnerability assesment</description>
	<lastBuildDate>Tue, 19 Jan 2010 05:15:53 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Which Routers Are Vulnerable to the D-Link HNAP Exploit?</title>
		<link>http://www.sourcesec.com/2010/01/18/which-routers-are-vulnerable-to-the-d-link-hnap-exploit/</link>
		<comments>http://www.sourcesec.com/2010/01/18/which-routers-are-vulnerable-to-the-d-link-hnap-exploit/#comments</comments>
		<pubDate>Mon, 18 Jan 2010 22:50:34 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Vulnerabilities]]></category>
		<category><![CDATA[d-link]]></category>
		<category><![CDATA[HNAP]]></category>
		<category><![CDATA[Routers]]></category>

		<guid isPermaLink="false">http://www.sourcesec.com/?p=204</guid>
		<description><![CDATA[ZDNet and PCWorld have both run articles regarding our recent disclosure of the D-Link HNAP vulnerability. As with other postings and reports, there seems to be some confusion as to which routers and models are affected. 
D-Link has made some statements that we&#8217;d like to offer rebuttals to, as we either suspect them to be [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://news.zdnet.co.uk/security/0,1000000189,39994509,00.htm">ZDNet</a> and <a href="http://www.pcworld.com/businesscenter/article/186996/dlink_issues_fixes_for_router_vulnerabilities.html">PCWorld</a> have both run articles regarding our recent <a href="http://www.sourcesec.com/2010/01/09/d-link-routers-one-hack-to-own-them-all/">disclosure</a> of the D-Link HNAP vulnerability. As with other postings and reports, there seems to be some confusion as to which routers and models are affected. </p>
<p>D-Link has made some statements that we&#8217;d like to offer rebuttals to, as we either suspect them to be incorrect or find them to be downright confusing. The below quotations are from the ZDNet article:</p>
<blockquote><p>The model that D-Link said is not in the European market is DI-524 (C1). In addition, that model does not support HNAP, the company noted.</p></blockquote>
<p>Yes, the DI-524 hardware version C1 does in fact support HNAP. It was one of the first D-Link routers to do so. Install the most recent firmware release (version 3.23). HNAP is clearly there and vulnerable.</p>
<blockquote><p>The non-existent model is DIR-628 (B2), as only A hardware has ever been released for that device.</p></blockquote>
<p>Correct, the DIR-628 hardware version B2 does not exist; that&#8217;s bad on us. The version we tested was actually A2 not B2 as we erroneously reported. I find it odd that D-Link doesn&#8217;t seem to have even tested their A-series DIR-628s though. If they had, they would have found that they were vulnerable.</p>
<blockquote><p>Finally, model DIR-655 (A1, firmware 1.30EA) runs a restricted firmware version related to East Asia and therefore irrelevant for Europe.</p></blockquote>
<p>There seems to be some expectation from D-Link and others that we have tested every firmware version for every D-Link router in existence. That is simply not possible for us to do. We tested three different D-Link routers with four different firmware versions that spanned a period of three years and two continents, and they were all vulnerable. But that is all that we have tested, and therefore all that we can confirm. Just because we didn&#8217;t test European firmware doesn&#8217;t mean that it is or isn&#8217;t vulnerable. It just means that we didn&#8217;t test it.</p>
<blockquote><p>The networking company said on Monday that the problem, discovered by security researchers SourceSec, affects three of its wireless routers: DIR-855 (hardware version A2), DIR-655 (versions A1 to A4) and DIR-635 (version B).</p></blockquote>
<p>Interestingly, D-Link told PCWorld that there were five routers affected: the DIR-855, DIR-655, DIR-635, DIR-615, and the DI-634. </p>
<p>Now, we <em>know</em> that the DI-524 and DIR-628 are vulnerable. We have also had reports that the DIR-300 is vulnerable (though we can&#8217;t confirm this). Yet D-Link does not mention any of them in their list of vulnerable routers. So are there three router models affected? Or five? Or more? Has D-Link performed comprehensive testing on their routers? Or are these just the ones that they&#8217;ve tested so far? I can assure you that the DIR-628 and DI-524 need to be added to this list; which others are missing?</p>
<blockquote><p>In addition, just running the exploit code was not enough to compromise D-Link routers, it said. &#8220;It is important to note that running the code on its own is not sufficient to hack into the router: only the software tool provided seems to achieve this result,&#8221; said the D-Link statement.</p></blockquote>
<p>OK, now<em> I&#8217;m</em> confused &#8211; running the code won&#8217;t hack the router, but running the software will? It&#8217;s a bash script: the code <em>is</em> the software (Einhorn is Finkle&#8230;Finkle is Einhorn&#8230;). Any piece of software that can make Web requests can be used to exploit the vulnerability. Web browser? Check. Netcat? Yup. Wget? Sure! Curl? Definitely! I&#8217;m not sure what D-Link is trying to say here.</p>
<p>And finally, there&#8217;s the inevitable passing of the buck:</p>
<blockquote><p>
&#8220;By publicising their tool, and giving specific instructions, the authors of the report have publicly outlined how the security can be breached, which could have had serious repercussions for our customers,&#8221; said the D-Link statement.</p></blockquote>
<p>Yes, of course. It&#8217;s not D-Link&#8217;s fault for selling vulnerable routers to their customers. It&#8217;s obviously our fault for informing their customers of the vulnerability. Shame on us.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sourcesec.com/2010/01/18/which-routers-are-vulnerable-to-the-d-link-hnap-exploit/feed/</wfw:commentRss>
		<slash:comments>26</slash:comments>
		</item>
		<item>
		<title>D-Link Routers: One Hack to Own Them All</title>
		<link>http://www.sourcesec.com/2010/01/09/d-link-routers-one-hack-to-own-them-all/</link>
		<comments>http://www.sourcesec.com/2010/01/09/d-link-routers-one-hack-to-own-them-all/#comments</comments>
		<pubDate>Sat, 09 Jan 2010 16:49:08 +0000</pubDate>
		<dc:creator>cheffner</dc:creator>
				<category><![CDATA[Code]]></category>
		<category><![CDATA[Papers]]></category>
		<category><![CDATA[Vulnerabilities]]></category>
		<category><![CDATA[d-link]]></category>
		<category><![CDATA[hack]]></category>
		<category><![CDATA[HNAP]]></category>
		<category><![CDATA[Routers]]></category>

		<guid isPermaLink="false">http://www.sourcesec.com/?p=195</guid>
		<description><![CDATA[We&#8217;ve been on hiatus over the past few months working on other projects, but last week we re-focused on D-Link routers. While we previously found a flaw in D-Link&#8217;s CAPTCHA implementation, this time around we&#8217;ve found a way to view and edit D-Link router settings without any administrative credentials.
The short story is that D-Link routers [...]]]></description>
			<content:encoded><![CDATA[<p>We&#8217;ve been on hiatus over the past few months working on other projects, but last week we re-focused on D-Link routers. While we previously found a <a href="http://www.sourcesec.com/2009/05/12/d-link-captcha-partially-broken/">flaw</a> in D-Link&#8217;s CAPTCHA implementation, this time around we&#8217;ve found a way to view and edit D-Link router settings without any administrative credentials.</p>
<p>The short story is that D-Link routers have a second administrative interface, which uses the Home Network Administration Protocol. While HNAP does require basic authentication, the mere existence of HNAP on D-Link routers allows attackers and malware to bypass CAPTCHA &#8220;security&#8221;. Further, HNAP authentication is not properly implemented, allowing anyone to view and edit administrative settings on the router.</p>
<p>HNAP appears to have been implemented in D-Link routers since 2006, and cannot be disabled. We have verified that vulnerabilities exist in the HNAP implementations of the DI-524, DIR-628 and DIR-655 routers, and suspect that most, if not all, D-Link routers since 2006 are vulnerable.</p>
<p>You can read our full write-up <a href="http://www.sourcesec.com/Lab/dlink_hnap_captcha.pdf">here</a>, and download our POC tool, HNAP0wn, <a href="http://www.sourcesec.com/Lab/hnap0wn.tar.gz">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sourcesec.com/2010/01/09/d-link-routers-one-hack-to-own-them-all/feed/</wfw:commentRss>
		<slash:comments>68</slash:comments>
		</item>
		<item>
		<title>ChicagoCon 2009s</title>
		<link>http://www.sourcesec.com/2009/04/29/chicagocon-2009s/</link>
		<comments>http://www.sourcesec.com/2009/04/29/chicagocon-2009s/#comments</comments>
		<pubDate>Thu, 30 Apr 2009 01:36:58 +0000</pubDate>
		<dc:creator>craig</dc:creator>
				<category><![CDATA[News]]></category>
		<category><![CDATA[Techniques]]></category>
		<category><![CDATA[Tools]]></category>
		<category><![CDATA[chicagocon]]></category>
		<category><![CDATA[EthicalHacker]]></category>
		<category><![CDATA[hacking]]></category>
		<category><![CDATA[Routers]]></category>

		<guid isPermaLink="false">http://www.sourcesec.com/?p=64</guid>
		<description><![CDATA[We&#8217;re just now putting the finishing touches on our presentation for the ChicagoCon 2009s security conference coming up next week. We will be discussing some of the &#8220;more serious issues&#8221; that we mentioned when we released our Hacking SOHO Routers paper late last year. In addition to releasing some new tools, our presentation topics include [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.chicagocon.com"><img class="alignright" title="ChicagoCon 2009s" src="http://www.chicagocon.com/images/stories/3monitors_rotate_ccw.png" alt="" width="168" height="63" /></a>We&#8217;re just now putting the finishing touches on our presentation for the <a href="http://www.chicagocon.com/2009s/conference.html">ChicagoCon</a> 2009s security conference coming up next week. We will be discussing some of the &#8220;more serious issues&#8221; that we mentioned when we released our <a href="http://www.sourcesec.com/2008/11/09/hacking-the-routers-soho-router-security/">Hacking SOHO Routers</a> paper late last year. In addition to releasing some new tools, our presentation topics include router reconnaissance, alternative attacks against WPA/WEP encryption, and how to hack a router with a stick of gum.</p>
<p>As always, there are going to be a lot of other great talks there too; tickets are still available and are only $100 for the conference, so if you&#8217;re going to be in the Chicago area May 8th and 9th, we hope you&#8217;ll stop by!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sourcesec.com/2009/04/29/chicagocon-2009s/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Hacking the Routers: SOHO Router Security</title>
		<link>http://www.sourcesec.com/2008/11/09/hacking-the-routers-soho-router-security/</link>
		<comments>http://www.sourcesec.com/2008/11/09/hacking-the-routers-soho-router-security/#comments</comments>
		<pubDate>Mon, 10 Nov 2008 04:50:29 +0000</pubDate>
		<dc:creator>cheffner</dc:creator>
				<category><![CDATA[Papers]]></category>
		<category><![CDATA[Research]]></category>
		<category><![CDATA[Routers]]></category>

		<guid isPermaLink="false">http://www.sourcesec.com/?p=43</guid>
		<description><![CDATA[We&#8217;ve been taking a close look at some popular SOHO routers lately, and have started to find some really interesting stuff. It&#8217;s actually a little disconcerting &#8211; I don&#8217;t think that we have seen a router that doesn&#8217;t contain some type of exploitable vulnerability. We&#8217;ve written up a preliminary paper detailing some of the issues [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://farm3.static.flickr.com/2191/2054390424_71068d839a.jpg"><img class="alignright" title="WRT54G configuration page, courtesy of Flickr" src="http://farm3.static.flickr.com/2191/2054390424_71068d839a.jpg" alt="" width="132" height="99" /></a>We&#8217;ve been taking a close look at some popular SOHO routers lately, and have started to find some really interesting stuff. It&#8217;s actually a little disconcerting &#8211; I don&#8217;t think that we have seen a router that doesn&#8217;t contain some type of exploitable vulnerability. We&#8217;ve written up a preliminary <a href="http://www.sourcesec.com/Lab/soho_router_report.pdf">paper</a> detailing some of the issues that we&#8217;ve discovered; there are some other, more serious issues that we&#8217;re still in the middle of investigating and we&#8217;ll hopefully have more information about those up here soon. An excerpt from the introduction:</p>
<blockquote><p>With embedded devices permeating today&#8217;s home networks, they have begun to attract a higher level of scrutiny from the security community than in previous years. In particular, the members of GNUCitizen have been relentlessly testing routers and wireless access points. Their discovery of multiple vulnerabilities in the BT Home Hub router affected a wide range of home networks in the UK [1], and their Router Hacking Challenge prompted a flurry of vulnerability reports against a variety of popular home routers, including the venerable Linksys WRT54G [2]. Specific vulnerabilities in home routers range from traditional Web attacks, such as XSS and CSRF, to authentication bypass attacks and buffer overflows; it is assumed that the reader has at least a passing knowledge of the attacks described in this paper.</p>
<p style="margin-bottom: 0in;">The purpose of this paper is to outline the security measures being taken by vendors to prevent such attacks in their home routing products, what those security measures accomplish, and where they fall short. We will use existing network tools to examine common vulnerabilities in a range of popular devices and demonstrate weaknesses in the security of those devices; additionally, we will examine common trends in security measures that have been duplicated across vendors, and examine how those trends help and hinder the security of their devices. In particular, we will examine the following home routers, which are some of the latest offerings from their respective vendors at the time of this writing:</p>
<p>&nbsp;</p>
<ul>
<li>Linksys WRT160N</li>
<li>D-Link DIR-615</li>
<li>Belkin F5D8233-4v3</li>
<li>ActionTec  MI424-WR</li>
</ul>
</blockquote>
<p>&nbsp;</p>
<p>Read the entire article <a href="http://www.sourcesec.com/Lab/soho_router_report.pdf">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.sourcesec.com/2008/11/09/hacking-the-routers-soho-router-security/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>
