<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Typical Injection Points in a Web Application</title>
	<atom:link href="http://startupsecurity.info/blog/2008/11/06/typical-injection-points-in-a-web-application/feed/" rel="self" type="application/rss+xml" />
	<link>http://startupsecurity.info/blog/2008/11/06/typical-injection-points-in-a-web-application/</link>
	<description>Security, for Startups</description>
	<lastBuildDate>Mon, 21 Sep 2009 16:57:21 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jason Likert</title>
		<link>http://startupsecurity.info/blog/2008/11/06/typical-injection-points-in-a-web-application/comment-page-1/#comment-14</link>
		<dc:creator>Jason Likert</dc:creator>
		<pubDate>Fri, 07 Nov 2008 21:32:01 +0000</pubDate>
		<guid isPermaLink="false">http://startupsecurity.info/?p=79#comment-14</guid>
		<description>I&#039;ve seen some patterns of using Contact Forms to exploit shoddy application logic or to execute denial of service attacks.  In both cases an unprotected, or abysmally protected, Contact Form (without hidden form manipulation) was used to display customer data or use the form to generate thousands of spam messages to inundate the application.</description>
		<content:encoded><![CDATA[<p>I&#8217;ve seen some patterns of using Contact Forms to exploit shoddy application logic or to execute denial of service attacks.  In both cases an unprotected, or abysmally protected, Contact Form (without hidden form manipulation) was used to display customer data or use the form to generate thousands of spam messages to inundate the application.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
