<?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>ashleyknowles &#187; flaw</title>
	<atom:link href="http://www.ashleyknowles.net/tag/flaw/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ashleyknowles.net</link>
	<description>IT professional, Formula 1 addict, security/hacking enthusiast, I love LAMP</description>
	<lastBuildDate>Tue, 07 Feb 2012 01:17:09 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
		<item>
		<title>iPhone Lock Screen Security Flaw</title>
		<link>http://www.ashleyknowles.net/2010/10/iphone-lock-screen-security-flaw/</link>
		<comments>http://www.ashleyknowles.net/2010/10/iphone-lock-screen-security-flaw/#comments</comments>
		<pubDate>Tue, 26 Oct 2010 02:07:53 +0000</pubDate>
		<dc:creator>Ashley Knowles</dc:creator>
				<category><![CDATA[Apple]]></category>
		<category><![CDATA[Computers and IT]]></category>
		<category><![CDATA[Featured]]></category>
		<category><![CDATA[Headlines]]></category>
		<category><![CDATA[iPhone]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[flaw]]></category>
		<category><![CDATA[iphone]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://www.ashleyknowles.net/?p=452</guid>
		<description><![CDATA[wired.com posted an article moments ago with a funny little flaw, allowing you to bypass the &#8220;lock code&#8221; configured on an iPhone. The discovery by some Brazilian dude (read the article here &#8211; www.wired.com/threatlevel/2010/10/iphone-snoop/), notes the following procedure: 1. Press &#8230; Continue reading &#8594;]]></description>
			<content:encoded><![CDATA[<p><a href="http://wired.com"  class="autohyperlink aga aga_2" title="http://wired.com" target="_blank">wired.com</a> posted an article moments ago with a funny little flaw, allowing you to bypass the &#8220;lock code&#8221; configured on an iPhone. </p>
<p>The discovery by some Brazilian dude (read the article here &#8211; <a href="http://www.wired.com/threatlevel/2010/10/iphone-snoop/)"  class="autohyperlink aga aga_3" title="http://www.wired.com/threatlevel/2010/10/iphone-snoop/)" target="_blank">www.wired.com/threatlevel/2010/10/iphone-snoop/)</a>, notes the following procedure:</p>
<p>1. Press the emergency call buton<br />
2. Dial ###<br />
3. Push the call button, and immediately hit the &#8220;lock&#8221; button (power button, whatever you want to call the button on top of the phone)</p>
<p>This launches the &#8220;phone&#8221; application, allowing you to see recent call history, contacts, and the ability to call any number you want. </p>
<p>Pressing the home key doesn&#8217;t work in this mode, so you can&#8217;t get much further then that, but it&#8217;s an interesting security flaw!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ashleyknowles.net/2010/10/iphone-lock-screen-security-flaw/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Exchange 2003 SMTP DATA command bug</title>
		<link>http://www.ashleyknowles.net/2009/10/exchange-2003-smtp-data-command-bug/</link>
		<comments>http://www.ashleyknowles.net/2009/10/exchange-2003-smtp-data-command-bug/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 23:14:33 +0000</pubDate>
		<dc:creator>Ashley Knowles</dc:creator>
				<category><![CDATA[Administration]]></category>
		<category><![CDATA[Computers and IT]]></category>
		<category><![CDATA[Exchange Server]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Security]]></category>
		<category><![CDATA[bug]]></category>
		<category><![CDATA[exchange 2003]]></category>
		<category><![CDATA[flaw]]></category>
		<category><![CDATA[linkedin]]></category>
		<category><![CDATA[smtp service]]></category>

		<guid isPermaLink="false">http://www.ashleyknowles.net/?p=75</guid>
		<description><![CDATA[This is an extract from a log file I&#8217;m looking at right now for an Exchange 2003 SMTP service&#8230; I sure as hell hope there&#8217;s just a patch missing, otherwise, this could be one NASTY bug. It appears as if &#8230; Continue reading &#8594;]]></description>
			<content:encoded><![CDATA[<p>This is an extract from a log file I&#8217;m looking at right now for an Exchange 2003 SMTP service&#8230; I sure as hell hope there&#8217;s just a patch missing, otherwise, this could be one NASTY bug. It appears as if the DATA section of the SMTP session has been escaped, possibly by inclusion of the escape sequence used by SMTP to exit the DATA block, thus tacking the rest of the email straight to the SMTP service for processing&#8230; Anyone who knows anything about SMTP should be able to see the implications of this&#8230; And hopefully, I&#8217;m not just making an ass of myself <img src='http://www.ashleyknowles.net/wp-includes/images/smilies/icon_razz.gif' alt=':P' class='wp-smiley' /> </p>
<p>13:13:30 124.61.182.49 EHLO &#8211; 250<br />
13:13:30 124.61.182.49 MAIL &#8211; 250<br />
13:13:30 124.61.182.49 RCPT &#8211; 250<br />
13:13:32 124.61.182.49 DATA &#8211; 250<br />
13:13:32 124.61.182.49 so &#8211; 500<br />
13:13:32 124.61.182.49 &#8212;&#8212;=_nextpart_000_0007_01ca4ccf.fc799c50 &#8211; 500<br />
13:13:32 124.61.182.49 content-type: &#8211; 500<br />
13:13:32 124.61.182.49 <span style="white-space: pre;"> </span>charset=&#8221;iso-8859-1&#8243; &#8211; 500<br />
13:13:32 124.61.182.49 content-transfer-encoding: &#8211; 500<br />
13:13:32 124.61.182.49 &lt;!doctype &#8211; 500<br />
13:13:32 124.61.182.49 &lt;html&gt;&lt;head&gt; &#8211; 500<br />
13:13:32 124.61.182.49 &lt;meta &#8211; 500<br />
13:13:32 124.61.182.49 &gt; &#8211; 500<br />
13:13:32 124.61.182.49 &lt;meta &#8211; 500<br />
13:13:32 124.61.182.49 &lt;style&gt;&lt;/style&gt; &#8211; 500<br />
13:13:32 124.61.182.49 &lt;/head&gt; &#8211; 500<br />
13:13:32 124.61.182.49 &lt;body&gt; &#8211; 500<br />
13:13:32 124.61.182.49 &lt;html&gt; &#8211; 500<br />
13:13:32 124.61.182.49 &lt;head&gt; &#8211; 500<br />
13:13:32 124.61.182.49 &lt;title&gt;&lt;/title&gt; &#8211; 500<br />
13:13:32 124.61.182.49 &lt;/head&gt; &#8211; 500<br />
13:13:32 124.61.182.49 &lt;body &#8211; 500<br />
13:13:32 124.61.182.49 &#8220;&gt; &#8211; 500<br />
13:13:32 124.61.182.49 &lt;table &#8211; 500<br />
13:13:32 124.61.182.49 &lt;tr&gt; &#8211; 500<br />
13:13:32 124.61.182.49 &lt;td&gt; &#8211; 500<br />
13:13:32 124.61.182.49 &lt;center&gt;&lt;a &#8211; 500<br />
13:13:32 124.61.182.49 QUIT &#8211; 240</p>
]]></content:encoded>
			<wfw:commentRss>http://www.ashleyknowles.net/2009/10/exchange-2003-smtp-data-command-bug/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

