<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>PHPDeveloper.org</title>
    <link>http://www.phpdeveloper.org</link>
    <description>Up-to-the Minute PHP News, views and community</description>
    <language>en-us</language>
    <pubDate>Thu, 08 Jan 2009 02:50:56 -0600</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPro.org: PHP Security]]></title>
      <guid>http://www.phpdeveloper.org/news/11040</guid>
      <link>http://www.phpdeveloper.org/news/11040</link>
      <description><![CDATA[<p>
<i>Kevin Waterson</i> has posted <a href="http://www.phpro.org/tutorials/PHP-Security.html">a new article</a> to his site today - an introductory look at security in your PHP applications.
</p>
<blockquote>
One of the great benefits of PHP is its ease of access to new-comers. Its entry level is minimal and so attracts those looking for simple scripts to their sites. It is this same ease of access that becomes a problem as the new-comers begin to deal with input from users. Failure to adequately validate and sanitize data is the leading cause of security problems when dealing with PHP.
</blockquote>
<p>
He looks at a few different areas that developers need to focus on (and be sure to filter on) like PHP_SELF, protection from email header injections, file inclusion and the use of error reporting to make handling user-generated errors "more correct".
</p>]]></description>
      <pubDate>Thu, 18 Sep 2008 12:04:31 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Gareth Heyes' Blog: Exploiting PHP SELF]]></title>
      <guid>http://www.phpdeveloper.org/news/9413</guid>
      <link>http://www.phpdeveloper.org/news/9413</link>
      <description><![CDATA[<p>
<i>Gareth Heyes</i> has a <a href="http://www.thespanner.co.uk/2008/01/14/exploiting-php-self/">new post</a> today talking about one of the vulnerable values in the $_SERVER superglobal - PHP_SELF.
</p>
<blockquote>
I thought it might be a good idea to gather a few test cases demonstrating the problem. Why PHP allows these URL's is beyond me and it wouldn't take much work to filter out these malicious URL's in the PHP code.
</blockquote>
<p>
He <a href="http://www.thespanner.co.uk/2008/01/14/exploiting-php-self/">provides</a> four test cases to show how simple it is to abuse - one using a HTTP header, another pushing XSS through, the third mentions search pages and the fourth a direct code injection.
</p>
<p>
You can <a href="http://www.thespanner.co.uk/wp-content/uploads/2008/01/php_selfphp.zip">download the code here</a>.
</p>]]></description>
      <pubDate>Mon, 14 Jan 2008 07:54:00 -0600</pubDate>
    </item>
  </channel>
</rss>
