<?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, 20 Jun 2013 06:01:29 -0500</pubDate>
    <ttl>30</ttl>
    <item>
      <title><![CDATA[Ed Finkler's Blog: So what is the state of secure development in PHP?]]></title>
      <guid>http://www.phpdeveloper.org/news/7450</guid>
      <link>http://www.phpdeveloper.org/news/7450</link>
      <description><![CDATA[<p>
Sometimes, a picture is worth a thousand words - check out the one included with <a href="http://funkatron.com/wp/archives/php/so-what-is-the-state-of-secure-development-in-php/">this new post</a> on <i>Ed Finkler</i>'s blog today, a graph of the NIST NVD data showing where most of the security-related PHP issues lie.
</p>
<blockquote>
PHP Applications by themselves account for over 40% of all NIST NVD entries in 2006. We need more than new frameworks. We need new paradigms for PHP development.
</blockquote>
<p>
These new paradigms of PHP development have been a long time coming (it's all been jokes about it thus far), but there's already forces at work to help make things simpler and better for those developing applications. Frameworks, while not new in themselves, are making writing applications easier than ever before when using their built-in tools. 
</p>]]></description>
      <pubDate>Mon, 19 Mar 2007 08:23:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Community News: DreamStats "rootpath" File Inclusion Vulnerability Identified]]></title>
      <guid>http://www.phpdeveloper.org/news/7231</guid>
      <link>http://www.phpdeveloper.org/news/7231</link>
      <description><![CDATA[<p>
As the International PHP Maagzine <a href="http://www.php-mag.net/magphpde/magphpde_news/psecom,id,26852,nodeid,5.html">reports today</a> there's been a file inclusion vulnerability found (from Secunia) in the DreamStats package:
</p>
<blockquote>
Secunia's latest advisory points out a vulnerability in DreamStats, which could be exploited by remote attackers to execute arbitrary commands. This issue is due to an input validation error in the "index.php" script that does not validate the "rootpath" parameter, which could be exploited by remote attackers to include malicious PHP scripts and execute arbitrary commands with the privileges of the web server.
</blockquote>
<p>
Those at risk are systems running versions 4.2 and prior and should <a href="http://www.mnprojects.com/dreamstats/downloads_ds.php">update immediately</a>. DreamStats is a package for displaying the statistics for Call of Duty related games on a website.
</p>]]></description>
      <pubDate>Tue, 06 Feb 2007 11:37:00 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[LWN.net: Remote file inclusion vulnerabilities]]></title>
      <guid>http://www.phpdeveloper.org/news/6489</guid>
      <link>http://www.phpdeveloper.org/news/6489</link>
      <description><![CDATA[<p>
According to <a href="http://lwn.net/SubscriberLink/203904/c450f7af16f34584/">this article</a> from LWN.net, you might need to be a bit wary of how you use the allow_url_fopen configuration parameter on your server. Apparently there are some remote file inclusion issues that could cause problems for calls to include or require already in your code.
</p>
<blockquote>
An attacker's fondest wish is to be able to run their code on the target system; an RFI exploit does just that. By exploiting two very dubious 'features' of the PHP language, an attacker can inject their code into a PHP program on the server.
</blockquote>
<p>
Basically, if the potential hacker can manage to get in on a varaible that's inside of an include and use it (in)correctly, they can get the script to jump out and run the code from their server instead of the local copy. Turning off regiter_globals will provide some protection, put poor programming and not performing any input validation can poke holes in the script's security without the need for globals.
</p>
<p>
Check out <a href="http://lwn.net/SubscriberLink/203904/c450f7af16f34584/">the rest of the article</a> for more information on this (potentially) serious issue and check your code/configuration doubly to make sure you're not at risk.
</p>]]></description>
      <pubDate>Thu, 12 Oct 2006 10:27:00 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[FrSIRT: Vivvo Article Management CMS SQL Injection and PHP File Inclusion Vulnerabilities]]></title>
      <guid>http://www.phpdeveloper.org/news/6298</guid>
      <link>http://www.phpdeveloper.org/news/6298</link>
      <description><![CDATA[<p>
The FrSIRT site has posted <a href="http://www.frsirt.com/english/advisories/2006/3548">a new advisory</a> for users of the Vivvo Article Management CMS software about potential holes that could allow for some very large-scale damage to be done.
</p>
<blockquote>
<p>
Multiple vulnerabilities have been identified in Vivvo Article Management CMS, which could be exploited by remote attackers to compromise a vulnerable server.
</p>
<p>
The first issue is due to an input validation error in the "pdf_version.php" script that does not validate the "id" parameter before being used in SQL statements, which could be exploited by malicious people to conduct SQL injection attacks.
</p>
<p>
The second vulnerability is due to an input validation error in the "index.php" script that do not validate the "classified_path" parameter, which may be exploited by remote attackers to include local or remote scripts with the privileges of the web server.
</p>
</blockquote>
<p>
Versions 3.2 and higher of the software are effected, and, unfortunately, there has been no patch issued for the issue.
</p>]]></description>
      <pubDate>Mon, 18 Sep 2006 14:08:57 -0500</pubDate>
    </item>
    <item>
      <title><![CDATA[Justin Silverton's Blog:  PHP Security Mistakes - Part 2]]></title>
      <guid>http://www.phpdeveloper.org/news/5022</guid>
      <link>http://www.phpdeveloper.org/news/5022</link>
      <description><![CDATA[<i>Justin Silverton</i> continues his "PHP Security Mistakes" series with <a href="http://blinduser.blogspot.com/2006/03/php-security-mistakes-part-2.html">this new post</a>, looking at issues surrounding system calls, file uploads, and including files into your scripts.
<p>
<quote>
<i>
In one of my previous articles, I mentioned the top 5 security mistakes made in PHP. This article is a follow-up, with some more common security mistakes.
</i>
</quote>
<p>
For the <a href="http://blinduser.blogspot.com/2006/03/php-security-mistakes-part-2.html">three topics</a> he describes the functionality PHP offers for them as well as a suggestion or two as to how you can prevent these issues from showing up in your scripts. ]]></description>
      <pubDate>Tue, 21 Mar 2006 06:56:49 -0600</pubDate>
    </item>
    <item>
      <title><![CDATA[Mike Wallner's Blog: imap_savebody()]]></title>
      <guid>http://www.phpdeveloper.org/news/4751</guid>
      <link>http://www.phpdeveloper.org/news/4751</link>
      <description><![CDATA[There's a <a href="http://blog.iworks.at/?/archives/37-imap_savebody.html">quick post</a> from <i>Mike Wallner</i> today with a helpful IMAP hint for those working with attachments - and his solution.
<p>
<quote>
<i>
If you -like me- were suffering from being unable to load big attachments through ext/imap because of PHPs memory limit, the new imap_savebody() function should be what you were looking for. It adds the ability to save any section (full mail, too) of a mail message to a file or stream.
</i>
</quote>
<p>
You can see the proposal for the functionality on <a href="http://www.zend.com/zend/week/week255.php#Heading9">this Zend page</a>, including some of the suggestions others made and its inclusion into <a href="http://www.zend.com/zend/week/pat/index.php">The PAT direectory</a>. You can <a href="http://www.zend.com/zend/week/pat/pat50.txt">view the source here</a>...]]></description>
      <pubDate>Mon, 30 Jan 2006 07:20:47 -0600</pubDate>
    </item>
  </channel>
</rss>
