<?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: ColdFusion shared hosting security and internals</title>
	<atom:link href="http://jochem.vandieten.net/2008/12/15/coldfusion-shared-hosting-security-and-internals/feed/" rel="self" type="application/rss+xml" />
	<link>http://jochem.vandieten.net/2008/12/15/coldfusion-shared-hosting-security-and-internals/</link>
	<description>Jochem's tech exploits</description>
	<pubDate>Tue, 09 Jun 2026 10:22:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jonathan van Zuijlekom</title>
		<link>http://jochem.vandieten.net/2008/12/15/coldfusion-shared-hosting-security-and-internals/comment-page-1/#comment-125</link>
		<dc:creator>Jonathan van Zuijlekom</dc:creator>
		<pubDate>Tue, 16 Dec 2008 09:15:21 +0000</pubDate>
		<guid isPermaLink="false">http://jochem.vandieten.net/2008/12/15/coldfusion-shared-hosting-security-and-internals/#comment-125</guid>
		<description>@Bradley: You're right, using an empty Application.cfc lets you dump (and edit) all application variables.

Shouldn't this "feature" be fixed?</description>
		<content:encoded><![CDATA[<p>@Bradley: You&#8217;re right, using an empty Application.cfc lets you dump (and edit) all application variables.</p>
<p>Shouldn&#8217;t this &#8220;feature&#8221; be fixed?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bradley Moore</title>
		<link>http://jochem.vandieten.net/2008/12/15/coldfusion-shared-hosting-security-and-internals/comment-page-1/#comment-119</link>
		<dc:creator>Bradley Moore</dc:creator>
		<pubDate>Mon, 15 Dec 2008 20:04:23 +0000</pubDate>
		<guid isPermaLink="false">http://jochem.vandieten.net/2008/12/15/coldfusion-shared-hosting-security-and-internals/#comment-119</guid>
		<description>Yarr, Application.cfc code should be &#60;cfcomponent&#62;&#60;/cfcomponent&#62;</description>
		<content:encoded><![CDATA[<p>Yarr, Application.cfc code should be &lt;cfcomponent&gt;&lt;/cfcomponent&gt;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bradley Moore</title>
		<link>http://jochem.vandieten.net/2008/12/15/coldfusion-shared-hosting-security-and-internals/comment-page-1/#comment-118</link>
		<dc:creator>Bradley Moore</dc:creator>
		<pubDate>Mon, 15 Dec 2008 20:02:48 +0000</pubDate>
		<guid isPermaLink="false">http://jochem.vandieten.net/2008/12/15/coldfusion-shared-hosting-security-and-internals/#comment-118</guid>
		<description>Giving your application uncommon/hard to guess names is helpful, but it only prevents accidental access to your application scope.  Targeted/Blanket attacks are possible without the knowledge of your application name.

Quick Attack Explaination: 
// This works on any application on the same CF instance.  Attacking my dev machine from itself!  Oh, noes.

- Startup a few CF applications
- Create a new directory on the same CF instance.
- Create a new application named an empty string or be lazy and let ColdFusion default the value for you.
Application.cfc code:

- Create a new page and 
- Don't Panic

There is a bunch of stuff you could careless about, but you will also see every application name and variable stored within the application scope.  The amusing bit is these are pointers, so we can also modify them.  =(

This means anyone else on your shared CF instance can see/modify your application variables.  This means you should not store your dsn login information, encryption keys, ssn, credit card data, etc in the application scope.

Similarly, if you do know another application name, then you can name your application to the same thing and access their application scope variables.</description>
		<content:encoded><![CDATA[<p>Giving your application uncommon/hard to guess names is helpful, but it only prevents accidental access to your application scope.  Targeted/Blanket attacks are possible without the knowledge of your application name.</p>
<p>Quick Attack Explaination:<br />
// This works on any application on the same CF instance.  Attacking my dev machine from itself!  Oh, noes.</p>
<p>- Startup a few CF applications<br />
- Create a new directory on the same CF instance.<br />
- Create a new application named an empty string or be lazy and let ColdFusion default the value for you.<br />
Application.cfc code:</p>
<p>- Create a new page and<br />
- Don&#8217;t Panic</p>
<p>There is a bunch of stuff you could careless about, but you will also see every application name and variable stored within the application scope.  The amusing bit is these are pointers, so we can also modify them.  =(</p>
<p>This means anyone else on your shared CF instance can see/modify your application variables.  This means you should not store your dsn login information, encryption keys, ssn, credit card data, etc in the application scope.</p>
<p>Similarly, if you do know another application name, then you can name your application to the same thing and access their application scope variables.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jonathan van Zuijlekom</title>
		<link>http://jochem.vandieten.net/2008/12/15/coldfusion-shared-hosting-security-and-internals/comment-page-1/#comment-116</link>
		<dc:creator>Jonathan van Zuijlekom</dc:creator>
		<pubDate>Mon, 15 Dec 2008 15:35:31 +0000</pubDate>
		<guid isPermaLink="false">http://jochem.vandieten.net/2008/12/15/coldfusion-shared-hosting-security-and-internals/#comment-116</guid>
		<description>The application scope variables are only accessible across applications if the application name is the same. I would advise to use a hard to guess application name

</description>
		<content:encoded><![CDATA[<p>The application scope variables are only accessible across applications if the application name is the same. I would advise to use a hard to guess application name</p>
]]></content:encoded>
	</item>
</channel>
</rss>
