Today's PHP Security Release, and How We're Strengthening PHP Security (PHP Foundation)
The PHP Foundation has put out a blog entry explaining how the vulnerabilities disclosed today came about and why they took so long to fix. To fix the OOM problem, the PHP security team developed several competing approaches, but each came with its own trade-offs: backward compatibility breaks, new denial-of-service potential, or requiring changes to many third-party extensions which seemed…
The PHP Foundation has recently released a blog post detailing the recent security vulnerabilities discovered in PHP and the challenges faced in resolving them. The team responsible for PHP's security had to consider several potential solutions, each with its own set of drawbacks. These included potential compatibility issues, the risk of new denial-of-service attacks, and the need for modifications to a large number of third-party extensions.
The consensus-based decision-making process within the PHP security team made it difficult to select the most suitable solution, as they were wary of the consequences of implementing the wrong choice. Additionally, the limited availability of core developers with the required expertise to address the issue further exacerbated the situation, leading to repeated delays in the development and implementation of a fix.
The PHP Foundation acknowledges that this delay was a structural failure, attributable to both the decision-making process of the security team and its limited resources.
Written by urgent.news from LWN's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
This story
This is one outlet's version. Read the fullest account.
- Today's PHP Security Release, and How We're Strengthening PHP Security thephp.foundation
- Today's PHP Security Release, and How We're Strengthening PHP Security simonwillison.net