<?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"
	>
<channel>
	<title>Comments on: Holes in Embedded Devices: Authentication bypass (pt 1)</title>
	<atom:link href="http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1/</link>
	<description>Cutting-edge Think tank &#124; Ethical Hacker Outfit</description>
	<pubDate>Sun, 20 Jul 2008 22:09:52 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: spenser</title>
		<link>http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1/#comment-122861</link>
		<dc:creator>spenser</dc:creator>
		<pubDate>Sun, 06 Jul 2008 07:45:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1#comment-122861</guid>
		<description>Never mind a ups.

There is a $30K+ "enterprise unified threat management" appliance that seems to have a hard coded backdoor super admin account that is not documented to purchasers. It certainly is not mentioned in the documentation. But, it can be seen plain as day to anyone looking at the firmware.

As a matter of fact, in recent years, the newsgroups are rife with complaints from admins that the first thing support wants when called is to be granted admin access from outside the perimeter. Naturally, due to the fact that firewall admins are likely to be somewhat aware of security, this tendency has raised a great deal of derision. The existence of a secret "super admin" account would certainly explain the desire of first level support techs to gain permission to logon.</description>
		<content:encoded><![CDATA[<p>Never mind a ups.</p>
<p>There is a $30K+ &#8220;enterprise unified threat management&#8221; appliance that seems to have a hard coded backdoor super admin account that is not documented to purchasers. It certainly is not mentioned in the documentation. But, it can be seen plain as day to anyone looking at the firmware.</p>
<p>As a matter of fact, in recent years, the newsgroups are rife with complaints from admins that the first thing support wants when called is to be granted admin access from outside the perimeter. Naturally, due to the fact that firewall admins are likely to be somewhat aware of security, this tendency has raised a great deal of derision. The existence of a secret &#8220;super admin&#8221; account would certainly explain the desire of first level support techs to gain permission to logon.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: joephantom</title>
		<link>http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1/#comment-115769</link>
		<dc:creator>joephantom</dc:creator>
		<pubDate>Sun, 02 Mar 2008 22:47:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1#comment-115769</guid>
		<description>nice photo. differential equations and gauss's divergence are your best friends.</description>
		<content:encoded><![CDATA[<p>nice photo. differential equations and gauss&#8217;s divergence are your best friends.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: NurBo</title>
		<link>http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1/#comment-115470</link>
		<dc:creator>NurBo</dc:creator>
		<pubDate>Sat, 23 Feb 2008 01:23:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1#comment-115470</guid>
		<description>good shez Adrian Pastor keep it up I like all 3 parts!</description>
		<content:encoded><![CDATA[<p>good shez Adrian Pastor keep it up I like all 3 parts!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Holes in Embedded Devices: Authentication bypass (pt 3) &#187; Inking&#8217;s Security Blog</title>
		<link>http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1/#comment-114907</link>
		<dc:creator>Holes in Embedded Devices: Authentication bypass (pt 3) &#187; Inking&#8217;s Security Blog</dc:creator>
		<pubDate>Sat, 16 Feb 2008 11:30:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1#comment-114907</guid>
		<description>[...] of authentication bypass bug. You may want to familiarize yourself with the previous two entries here and here, before you [...]</description>
		<content:encoded><![CDATA[<p>[...] of authentication bypass bug. You may want to familiarize yourself with the previous two entries here and here, before you [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Holes in Embedded Devices: Authentication bypass (pt 3) &#124; GNUCITIZEN</title>
		<link>http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1/#comment-114887</link>
		<dc:creator>Holes in Embedded Devices: Authentication bypass (pt 3) &#124; GNUCITIZEN</dc:creator>
		<pubDate>Sat, 16 Feb 2008 08:08:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1#comment-114887</guid>
		<description>[...] of authentication bypass bug. You may want to familiarize yourself with the previous two entries here and here, before you [...]</description>
		<content:encoded><![CDATA[<p>[...] of authentication bypass bug. You may want to familiarize yourself with the previous two entries here and here, before you [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ap</title>
		<link>http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1/#comment-114772</link>
		<dc:creator>ap</dc:creator>
		<pubDate>Fri, 15 Feb 2008 00:17:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1#comment-114772</guid>
		<description>correction: "that we shouldn't just rely" -&#62; "we shouldn't just rely"</description>
		<content:encoded><![CDATA[<p>correction: &#8220;that we shouldn&#8217;t just rely&#8221; -&gt; &#8220;we shouldn&#8217;t just rely&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adrian Pastor</title>
		<link>http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1/#comment-114771</link>
		<dc:creator>Adrian Pastor</dc:creator>
		<pubDate>Fri, 15 Feb 2008 00:13:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1#comment-114771</guid>
		<description>hey nexact, thanks for your feedback! just for the record the BT Home Hub auth bypass mentioned as an example was published in Oct 2007 (http://www.gnucitizen.org/blog/bt-home-flub-pwnin-the-bt-home-hub) and found a month before that. 

Needless to say, URL fuzzying is nothing new. The point of this post series is to show that embedded devices can be susceptible to *very* trivial auth bypass bugs.

You're so right, that we shouldn't just rely on documented default accounts when trying to find a valid username/password combination. Reverse-engineering the firmware is definitely the way forward!</description>
		<content:encoded><![CDATA[<p>hey nexact, thanks for your feedback! just for the record the BT Home Hub auth bypass mentioned as an example was published in Oct 2007 (http://www.gnucitizen.org/blog/bt-home-flub-pwnin-the-bt-home-hub) and found a month before that. </p>
<p>Needless to say, URL fuzzying is nothing new. The point of this post series is to show that embedded devices can be susceptible to *very* trivial auth bypass bugs.</p>
<p>You&#8217;re so right, that we shouldn&#8217;t just rely on documented default accounts when trying to find a valid username/password combination. Reverse-engineering the firmware is definitely the way forward!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Analyzing Web Interfaces of Embedded Devices &#171; Cyberphobia</title>
		<link>http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1/#comment-114748</link>
		<dc:creator>Analyzing Web Interfaces of Embedded Devices &#171; Cyberphobia</dc:creator>
		<pubDate>Thu, 14 Feb 2008 20:06:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1#comment-114748</guid>
		<description>[...] I&#8217;m referencing GnuCitizen again. This time their article is about analyzing web interfaces in embedded [...]</description>
		<content:encoded><![CDATA[<p>[...] I&#8217;m referencing GnuCitizen again. This time their article is about analyzing web interfaces in embedded [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nexact</title>
		<link>http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1/#comment-114733</link>
		<dc:creator>nexact</dc:creator>
		<pubDate>Thu, 14 Feb 2008 17:10:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1#comment-114733</guid>
		<description>s/pdp/ap/ in the last comments</description>
		<content:encoded><![CDATA[<p>s/pdp/ap/ in the last comments</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: nexact</title>
		<link>http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1/#comment-114723</link>
		<dc:creator>nexact</dc:creator>
		<pubDate>Thu, 14 Feb 2008 15:38:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.gnucitizen.org/blog/holes-in-embedded-devices-authentication-bypass-pt-1#comment-114723</guid>
		<description>hey pdp!

did I gave you some idea with my auth bypass for airspan prost antenna ? heheh ;)

good posts. ;-)

btw.. if your able to put your hand on a device with port 23 open and you have the firmware.. disassemble it, check if you can't find a default login/passwd account in it.. i made a found during a pentest, apc battery had a backdoor account.. I've been able to go in debug mode and dump the eeprom then gain access to web interface. gg. :)

i know theres a couple of websites around there that giving out default password but you can be *really* surprised if u take a look by yourself.</description>
		<content:encoded><![CDATA[<p>hey pdp!</p>
<p>did I gave you some idea with my auth bypass for airspan prost antenna ? heheh ;)</p>
<p>good posts. ;-)</p>
<p>btw.. if your able to put your hand on a device with port 23 open and you have the firmware.. disassemble it, check if you can&#8217;t find a default login/passwd account in it.. i made a found during a pentest, apc battery had a backdoor account.. I&#8217;ve been able to go in debug mode and dump the eeprom then gain access to web interface. gg. :)</p>
<p>i know theres a couple of websites around there that giving out default password but you can be *really* surprised if u take a look by yourself.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
