, SecurityFocus 2006-12-18
Story continued from Page 1
Yet, mistakes are still being made and in record numbers.
A search of the National Vulnerability Database revealed that, as of December 15, out of the 6,198 vulnerabilities recorded in 2006, as many as 2,690--or 43 percent--had the word "PHP" in the description. A random sampling of the flagged flaws showed that the search appeared to only reveal issues in PHP applications. A search of the database using "PHP" as a vendor flagged some 84 vulnerabilities for 2006 (including in optional components of the language, such as PEAR), while a search using "PHP" as the product returned 33 bug, ostensibly in the core functions.
The vast numbers of bugs attributed to PHP applications is not surprising given that many amateur developers create their Web sites using the language, said NIST's Mell.
"I think it is tough for the general public to write secure dynamic Web applications," he said. "As much as possible scripting languages for Web sites should be dummy proof. In many incidences, I, a security professional, wondered how to code some bit securely. I wanted to, but how to do it was not immediately obvious."
Flaws in PHP applications have caused headaches for many webmasters. A year ago, the Lupper worm spread among vulnerable applications that used the PHP extensions for extensible markup language (XML), or RPC-XML. Other worms have utilized flaws in popular PHP bulletin board programs as well.
Continuing to educate PHP developers on the latest techniques to secure their applications is extremely important, said Chris Shiflett, a manager in the Web application security practice at OmniTI and author of O'Reilly's Essential PHP Security.
"To say PHP has a security problem suggests that it's impossible to develop a secure PHP application, but to say PHP doesn't have a security problem suggests that everything is perfect--neither is true," Shiflett said. "Web application security is a rapidly evolving discipline, and it's difficult for the average developer to keep up with the pace."
Developers need to start thinking about security as soon as start designing their applications, he said. Moreover, the focus on securing code needs to continue throughout the life of the Web site, he added.
"Over time, web application security should start to mature just as other security disciplines have, but that only means the pace of evolution will slow down, not stop," Shiflett said.