ZDNet UK


Skip to Main Content

ZDNet.co.uk - Winner of Best Business Website 2007
  1. Home
  2. News
  3. Blogs
  4. Reviews
  5. Prices
  6. Resources
  7. Community
  8. My ZDNet

 

ZDNet UK RSS Feeds


IT Jobs

Security threats Toolkit

Researcher kicks off 'Month of PHP Bugs'

Joris Evers CNET News.com

Published: 05 Mar 2007 09:31 GMT

  • Email
  • Trackback
  • Clip Link
  • Print friendly
  • Post Comment

A security researcher has kicked off a project to put the spotlight on flaws in the widely used PHP scripting language.

The initiative, dubbed "Month of PHP Bugs", started on Thursday. Five vulnerabilities have so far been disclosed, several of which could allow a system running PHP to be compromised, according to the project website.

"This initiative is an effort to improve the security of PHP," Stefan Esser, a noted PHP security expert, wrote on the project website. The bug releases will focus on vulnerabilities in the PHP core, not on problems in the PHP language that might result in insecure PHP applications, he wrote.

PHP, which originally stood for Personal Home Page, is a popular scripting language used to create dynamic web pages. Applications written in PHP accounted for 43 percent of the total vulnerabilities reported in 2006, according to a tally by Security Focus, a security news website.

The Month of PHP Bugs is backed by the Hardened-PHP Project, which was launched by three German security researchers in 2004. "You should consider the Month of PHP Bugs a result report for just another audit we did on PHP," Esser wrote.

Contrary to other "month of" bug projects that have been launched over the past months, the PHP effort will not feature only new bugs; some may have been patched already, according to the project website. Also, many of the bugs will already have been reported to the PHP security team, the site notes.

The Month of PHP Bugs follows similar projects that highlighted bugs in software for Macs, kernel-level software and web browsers. In all cases, the researchers behind the efforts said they wanted to improve security. Flaws that are publicly disclosed will get fixed quickly, they assert.

  • Email
  • Trackback
  • Clip Link
  • Print friendly Print with HP

Did you find this article useful?
4 out of 4 people found this useful


Full Talkback thread

0 comments

Company/Topic Alerts

Create a new alert from the list below:




Related Jobs

.NET Architect Contract - Stoke-on-Trent

NET Platform knowledge - Web architecture experience - Security procedures experience with large scale Websites and their vulnerabilities Please ...

Systems Administrator

Ascertain the cause of software and process failures, fixing bugs, (in coordination with the Product Development team) updating configuration, ...

Security Consultant Ethical Hacking / Penetration Testing - London

Responsibilities: - Deliver security assessment services including network scanning, vulnerability testing, penetration testing, search engine ...

Sentry Posts Blog

Mobile Linux Better For Mobile Busines...

Mobile Linux Better For Mobile Business Apps? Author: Eric Everson, MyMobiSafe.com As mobile Linux is carving it’s footprint on the future of mobile application development, the... More

Post a comment

DWP downplays security breach

The Department for Work and Pensions (DWP) has admitted that some of its staff have been forwarding passwords with password protected material. An email that was leaked on the 'Dizzy... More

Post a comment

How many headshots does one chairperso...

We got a strange request last week from the head of PR from Russian security experts Kaspersky. It seems although the company was very happy with the interview we recently carried with... More

Post a comment

Featured Talkback

On the contrary, if vendors were forced to stand behind their products it should increase innovation. It would force more, and better , testing before hitting the sales floor, resulting in fewer updates and less downtime for the consumer. At present the EULA removes responsibility from the vendor, and moves it to the user, which is a step backward. Make the vendor responsibility for their code.

By: ator1940

Read full story:
RSA: Vendor liability may stifle innovation