<?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>Tue, 18 Jun 2013 15:31:35 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[PHPBuilder: Pro PHP Security  /  Preventing SQL Injection, Part 2]]></title>
      <guid>http://www.phpdeveloper.org/news/6672</guid>
      <link>http://www.phpdeveloper.org/news/6672</link>
      <description><![CDATA[<p>
PHPBuilder is back with <a href="http://www.phpbuilder.com/columns/ProPHPSecurity_excerpt_part2.php3">the second part</a> of their excerpt from the book <a href="http://www.apress.com/book/bookDisplay.html?bID=437">Pro PHP Security</a> (Apress)looking at finding and preventing SQL injections in your applications.
</p>
<p>
Topics it's broken out into include:
<ul>
<li>Kinds of Injection Attacks
<li>Multiple-query Injection
<li>INVISION POWER BOARD SQL INJECTION VULNERABILITY
<li>Demarcate Every Value in Your Queries
</ul>
They start off pretty basic - watch what you're directly including in your SQL statement - and move on to how attackers can end your SQL and push in their own and more. The Invision vulnerability is a more real-world example of what can go wrong when filtering isn't done right. The tutorial's rounded off with some of the functions and methods you can use to check the input and filter out the bad from the good.
</p>]]></description>
      <pubDate>Thu, 09 Nov 2006 07:49:00 -0600</pubDate>
    </item>
  </channel>
</rss>
