<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>Security</title><link>http://www.michaelfalconer.co.uk/category/18.aspx</link><description>Security</description><managingEditor>Michael Falconer</managingEditor><dc:language>en-GB</dc:language><generator>.Text Version 0.95.2004.102</generator><item><dc:creator>Michael Falconer</dc:creator><title>Threat Modeling Web Applications</title><link>http://www.michaelfalconer.co.uk/archive/2005/05/18/227.aspx</link><pubDate>Wed, 18 May 2005 13:28:00 GMT</pubDate><guid>http://www.michaelfalconer.co.uk/archive/2005/05/18/227.aspx</guid><description>&lt;P&gt;Well, felt it was finally time to start posting again. I've been working on quite a few interesting applications over the past few months, so I hope to add some useful posts soon.&lt;/P&gt;
&lt;P&gt;In the meantime there's an &lt;A href="http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag2/html/tmwa.asp"&gt;interesting new series of posts&lt;/A&gt; on &lt;A title="Microsoft Developer Network" href="http://msdn.microsoft.com" target=_blank&gt;MSDN&lt;/A&gt; about developing threat models for web applications. While you may be aware of most of the threats, and the steps to prevent them becoming attacks, it's always good to review your knowledge, and to read about formalising the processes you hopefully already go through.&lt;/P&gt;&lt;img src ="http://www.michaelfalconer.co.uk/aggbug/227.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Michael Falconer</dc:creator><title>ViewStateUserKey</title><link>http://www.michaelfalconer.co.uk/archive/2005/02/13/220.aspx</link><pubDate>Sun, 13 Feb 2005 12:04:00 GMT</pubDate><guid>http://www.michaelfalconer.co.uk/archive/2005/02/13/220.aspx</guid><description>&lt;P&gt;While reading through an article titled '&lt;A href="http://msdn.microsoft.com/asp.net/default.aspx?pull=/library/en-us/dnaspp/html/securitybarriers.asp"&gt;Take Advantage of &lt;a title="ASP.NET" href="http://www.asp.net" target="_blank"&gt;ASP.NET&lt;/a&gt; Built-in Features to Fend Off Web Attacks&lt;/A&gt;' on &lt;a title="Microsoft Developer Network" href="http://msdn.microsoft.com" target="_blank"&gt;MSDN&lt;/a&gt; recently, I came across a new property for the Page class I'd never noticed before: ViewStateUserKey. The documentation for this property states:&lt;/P&gt;
&lt;BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px"&gt;
&lt;P&gt;Assigns an identifier to an individual user in the view state variable associated with the current page&lt;/P&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;It turns out what this can be used for is to add a user specific string to the ViewState of a Page which can be verified on PostBack. Why? This means you can be sure that any form information submitted came from the same user who requested the original page, thus preventing one-click attacks.&lt;/P&gt;
&lt;P&gt;I highly recommend you read &lt;A href="http://msdn.microsoft.com/asp.net/default.aspx?pull=/library/en-us/dnaspp/html/securitybarriers.asp"&gt;the article above&lt;/A&gt;&amp;nbsp;for more information, and for techniques to prevent other common attacks...&lt;/P&gt;&lt;img src ="http://www.michaelfalconer.co.uk/aggbug/220.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Michael Falconer</dc:creator><title>ASP.NET security vulnerability</title><link>http://www.michaelfalconer.co.uk/archive/2004/10/07/204.aspx</link><pubDate>Thu, 07 Oct 2004 10:57:00 GMT</pubDate><guid>http://www.michaelfalconer.co.uk/archive/2004/10/07/204.aspx</guid><description>&lt;P&gt;As everyone by now hopefully knows, there is a &lt;A href="http://www.microsoft.com/security/incident/aspnet.mspx"&gt;vulnerability in &lt;a title="ASP.NET" href="http://www.asp.net" target="_blank"&gt;ASP.NET&lt;/a&gt;&lt;/A&gt; that could allow an attacker to bypass security and access secured content.&lt;/P&gt;
&lt;P&gt;&lt;A href="http://support.microsoft.com/?kbid=887459"&gt;The fix&lt;/A&gt; is relatively straightforward, and there will hopefully be a proper patch from MS soon...&lt;/P&gt;&lt;img src ="http://www.michaelfalconer.co.uk/aggbug/204.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Michael D. Falconer</dc:creator><title>MSDN Lab : SQL injection protection</title><link>http://www.michaelfalconer.co.uk/archive/2004/07/12/189.aspx</link><pubDate>Mon, 12 Jul 2004 13:16:00 GMT</pubDate><guid>http://www.michaelfalconer.co.uk/archive/2004/07/12/189.aspx</guid><description>&lt;P&gt;I was just reading &lt;A href="http://www.mostlylucid.co.uk/archive/2004/07/10/1195.aspx" target=_blank&gt;Scott's post&lt;/A&gt; on &lt;A href="http://dotnetjunkies.com/WebLog/stefandemetz/" target=_blank&gt;Stefan Demetz's&lt;/A&gt; suggestion to change the default behavious of textboxes to only allow AlphaNumeric charcters by default. Personally, this is a shockingly bad idea, as I posted in &lt;A href="http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx?feedbackid=25d26b9a-11b4-49fe-be42-ca38ad0d1256" target=_blank&gt;my comment on the &lt;A title="Microsoft Developer Network" href="http://msdn.microsoft.com" target=_blank&gt;MSDN&lt;/A&gt; Lab site&lt;/A&gt;:&lt;/P&gt;
&lt;P&gt;'This is a really bad idea. So suddenly, by default, a user cannot complete an online form if their name contains and apostrophe of a dash. No more Peter O'Toole, or Camilla Parker-Bowles. If you want this functionality, why not just create a custom validator. Or create a new inherited TextBox object that strips out unwanted characters as required and/or throws an exception.'&lt;/P&gt;
&lt;P&gt;As Scott rightly says, a developer should be aware of these issues, and address them accordingly. To change such a fundamental feature of one of the most basic form&amp;nbsp;building blocks&amp;nbsp;is bound to end up causing massive headaches, particularly when there are simple steps to follow&amp;nbsp;to prevent SQL injection attacks.&lt;/P&gt;&lt;img src ="http://www.michaelfalconer.co.uk/aggbug/189.aspx" width = "1" height = "1" /&gt;</description></item><item><dc:creator>Michael D. Falconer</dc:creator><title>Microsoft post patch for Download.Ject</title><link>http://www.michaelfalconer.co.uk/archive/2004/07/02/187.aspx</link><pubDate>Fri, 02 Jul 2004 21:25:00 GMT</pubDate><guid>http://www.michaelfalconer.co.uk/archive/2004/07/02/187.aspx</guid><description>&lt;P&gt;Everyone has (hopefully) heard about the Download.Ject security issue that affect both IIS and IE. Microsoft have just released a patch which work by disabling ADODB.Stream.&lt;/P&gt;
&lt;P&gt;So, go to the &lt;A href=http://www.microsoft.com/security/default.mspx target="_blank"&gt;Microsoft Security Site&lt;/A&gt; to read more and &lt;A href=http://www.microsoft.com/security/incident/download_ject.mspx target="_blank"&gt;get more details&lt;/A&gt;, or just go to directly to the &lt;A href=http://windowsupdate.microsoft.com/ target="_blank"&gt;Windows Update Site&lt;/A&gt; to download the patch.&lt;/P&gt;&lt;img src ="http://www.michaelfalconer.co.uk/aggbug/187.aspx" width = "1" height = "1" /&gt;</description></item></channel></rss>