This is an old revision of the document!
PHP RFC: Security Issue Classification
- Version: 1.0
- Date: 2016-11-10
- Authors: Release Managers
- Status: Voting
- First Published at: http://wiki.php.net/rfc/security-classification
Current any issue that is in theory exploitable with security implications, must be treated as a security issue, even if the exploit requires nonsensical settings for a production environment, or some other special circumstances. This means that only a few people are able to handle the issue, it means that the fix needs to be merged out of band (from a separate secure repository), this results in considerable potential for further mistakes, and exerts disproportionate pressure on a few contributors.
In short, all the security issues can be split into three groups with high, medium and low severity. The essential idea of such classification definitions is to allow different handling depending on the issue severity. In practice, the big part of security issues are rather pure theoretical or quite hard to trigger. As the risk on such issues is quite low, they can be handled directly in the mainstream repository, thus allowing for a quality improvement through the usual open QA process.
The suggested security issue classifications are in first place directed to standardize the use cases in PHP. Nevertheless, the best practices taking place in various other OSS projects was taken into account.
Before we can seek to implement changes in the process that handles security issues, we should seek ratification of the reformed classification.
Please take the time to read the classification document if you haven't already, and consider your vote seriously, it is better for everyone if mistakes and inconsistencies (that are likely to be a problem) are dealt with now.
We are hoping this classification opens the door for more contributors, reduces the workload on a select few contributors, and eases our reform of the process that handles genuine security issues.
Voting opened November 10th for one week, closing November 17th:
There is no change to the language, however, since this is an important issue, we are going to require a super majority of 2/3+1.
Should the proposal fail to get the required votes, the classification will be reviewed and reformed before the vote is opened again: Consider this notice that there may not be two weeks between the first and subsequent vote.
Note: Should we discover, during the course of our work that the classification requires amendment, we will once again hold a vote.