admin: SECURITY.md updates#5311
Merged
Merged
Conversation
- Add recently published security advisories to SECURITY.md - Revision of security policy and definitions of vulnerability. - Also some minor forward-ports and adjustments of CHANGES. The substantive change is explaining that our policy is to only consider vulnerabilities if they (a) allow remote code execution, privilege escalation, and other very severe problems (not crashes, OOM, or most "DoS" scenaries), and (b) are exploitable in practice by untrusted actors merely by presenting malicious routine input such as image files (misuse of APIs, for example, is not a vulnerability). Everything else should be reported through the usual Issue/PR mechanism, and not use the security vulnerability reporting regime, which is massively more overhead for the maintainers. Signed-off-by: Larry Gritz <lg@larrygritz.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The substantive change is explaining that our policy is to only consider vulnerabilities if they (a) allow remote code execution, privilege escalation, and other very severe problems (not crashes, OOM, or most "DoS" scenaries), and (b) are exploitable in practice by untrusted actors merely by presenting malicious routine input such as image files (misuse of APIs, for example, is not a vulnerability).
Everything else should be reported through the usual Issue/PR mechanism, and not use the security vulnerability reporting regime, which is massively more overhead for the maintainers.