PHP Security Specialist (Stefan Esser) Resigns

Your website & network are Hackable


This is sad news as PHP hasn’t particularly had a good security record in the past.

He has voiced his frustrations with the internal workings of the PHP team and the development process, he has been working hard to make PHP inherently more secure…But from the look of things it seems like he was having a tough time.

Stefan Esser, PHP security specialist and member of the official PHP Security Response Team has, he says, had enough – in his blog he has announced his immediate resignation from the PHP Security Response Team. He states that he has various reasons for doing so, the most important of which is that his attempt to make PHP safer “from the inside” is futile. According to Esser, as soon as you try to criticise PHP security, you become persona-non-grata in the security team. In addition many of his suggestions were ignored because the developers considered Esser’s choice of words, too abrasive. He says that he had stopped counting the number of times he was called a traitor when he published a bug report on a vulnerability in PHP.

Too abrasive? It’s security for goodness sake, it’s an important matter..Can’t they just suck up their egos for once and admit they are wrong and make the freaking thing more secure.

Esser wants to continue to publish his reports without worrying about whether or not a patch is available. He no longer wishes to cover up the slowness of the reaction time between discovery of a vulnerability and publication of this information. It is reasonable to expect that he will be publishing substantially more vulnerabilities in PHP in the future.

The disagreement between Esser and the PHP team seems to be particularly inflamed by the matter of how best to improve the security of PHP. While Esser feels that certain PHP functions are intrinsically unsafe (for example allow_url_fopen/allow_url_include) and should therefore be revised, many developers, including PHP specialists Zend, think that the security problems in PHP applications have simply been caused by inexperienced programmers.

I have to admit that is the wrong attitude, the language should make it as hard as possible for inexperienced programmers to make the application insecure.

That’s why Typesafe languages came about..

Source: Heise Security


Posted in: Exploits/Vulnerabilities, General News, Web Hacking

, , , , , ,

Recent in Exploits/Vulnerabilities:
- Intel Hidden Management Engine – x86 Security Risk?
- TeamViewer Hacked? It Certainly Looks Like It
- Serious ImageMagick Zero-Day Vulnerabilities – ImageTragick?

Related Posts:

Most Read in Exploits/Vulnerabilities:
- Learn to use Metasploit – Tutorials, Docs & Videos - 234,729 views
- AJAX: Is your application secure enough? - 120,088 views
- eEye Launches 0-Day Exploit Tracker - 85,535 views

Malwarebytes Anti-Exploit Premium | 1 Year 1 PC for $24.95


Trackbacks/Pingbacks

  1. q!Bang Solutions » Blog Archive » Stefan Esser quits PHP Security Response Team - January 19, 2007

    […] Although this announcement was made last year, I did not catch it until today on darknet. This is sad news, and in my opinion, a big blow to PHP’s developer’s community. There are other efforts out there trying to improve PHP’s inherently weaker security model, such as PHPSec.org. For those of you who know me well, you know that I although I use PHP, I am not a huge fan of it. For some reason, some people argue that this is an easy language to pick up for beginners. I can only guess that it is because PHP is very “graphical” and users can generate web pages with ease. But as far as a language goes, I would think that python is a much easier language to pick up for beginners. […]