<?xml version="1.0" encoding="ISO-8859-1" ?>
<rss version="2.0">
<channel>
	<title>Etomite Security Announcements</title>
	<description>Etomite Security Announcements Forum</description>
	<link>http://www.etomite.com/index.php</link>
	<pubDate>Mon, 18 Feb 2008 20:36:55 +0000</pubDate>
	<ttl>5</ttl>
	<image>
		<title>Etomite Security Announcements</title>
		<url>http://www.etomite.com/skin_acp/IPB2_Standard/images/rss.png</url>
		<link>http://www.etomite.com/index.php</link>
	</image>
	<item>
		<title>Reported Potential XSS Exploit</title>
		<link>http://www.etomite.com/topic/7647-reported-potential-xss-exploit/</link>
		<description><![CDATA[Before anyone starts getting worked into a panic over a recent security alert, allow me to remark on allegations that this is an Etomite-specific exploit... I have no problems with resolving what is a true Etomite-specific threat but I do not appreciate having Etomite being made out to be <em class='bbc'>THE</em> threat... If the server that Etomite is running on has proper security measures in place then there is no threat... If, however, the server doesn't have proper security measures in place then many PHP scripts are potentially exploitable...<br />
<br />
The threat itself was inaccurately described and it took me a while to figure out exactly what was going on... Alerts were stating that the <strong class='bbc'>$_SERVER['PHP_INFO']</strong> variable, which doesn't even exist, is the culprit... The variable in question is actually <strong class='bbc'>$_SERVER['PHP_SELF']</strong>... If anyone wants to insure that their system is not vulnerable to exploit attempts they can do so be simply adding the following line into their <strong class='bbc'>index.php</strong> parser file... I have tested Etomite with this line both as the first line of code, directly below the opening <strong class='bbc'>&lt;?php</strong> tag as well as at the bottom of the script, directly above the comment line <strong class='bbc'>// first, set some settings, and do some stuff</strong> and both work equally well... At the top of the script is probably the easiest...<br />
<br />
<pre class='prettyprint'>$_SERVER&#91;&#34;PHP_SELF&#34;&#93; = htmlentities&#40;$_SERVER&#91;&#34;PHP_SELF&#34;&#93;&#41;;</pre><br />
<br />
 While the potential for Cross Server Scripting is somewhat remote, it can't hurt to have this extra line of code in place... The link to the best, yet still inaccurate, explanation is located at <a rel='nofollow' href="http://www.securityfocus.com/archive/1/488122" target="_blank"><a href='http://www.securityfocus.com/archive/1/488122' class='bbc_url' title='External link' rel='nofollow external'>http://www.securityfocus.com/archive/1/488122</a></a> for anyone interested...<br />
<br />
While only a remote possibility, I cannot assure anyone that this patch will not have potentially adverse effects on snippet functionality... I have been running tests on my development sites, only one of which is open to the vulnerability, and have had no problems as of yet...]]></description>
		<pubDate>Mon, 18 Feb 2008 20:36:55 +0000</pubDate>
		<guid>http://www.etomite.com/topic/7647-reported-potential-xss-exploit/</guid>
	</item>
	<item>
		<title>Subscribe to Announcements</title>
		<link>http://www.etomite.com/topic/6300-subscribe-to-announcements/</link>
		<description><![CDATA[We have now set up Outputting of the Security Announcements (only) Forum via RSS, and you can be sent an e-Mail when an item is posted there - for this reason, the announcements forum will be set to read-only.<br />
<br />
To Subscribe,<br />
<a rel='nofollow' href="http://www.feedburner.com/fb/a/emailverifySubmit?feedId=562454" target="_blank">Click Here to Subscribe to Etomite Security Announcements by Email</a><br />
<a rel='nofollow' href="http://feeds.feedburner.com/etomiteannouncements" target="_blank">Click Here to Subscribe to Etomite Security Announcements by RSS</a>]]></description>
		<pubDate>Tue, 07 Nov 2006 09:00:38 +0000</pubDate>
		<guid>http://www.etomite.com/topic/6300-subscribe-to-announcements/</guid>
	</item>
</channel>
</rss>