Repository navigation
State the bug bounty scope where reporters read it - #514
Merged
Merged
Conversation
SECURITY.md is what GitHub shows a reporter, and it said how to report but not what is in scope. The ground rules said the sanitizer is the target and the project's infrastructure is out of bounds, but not that other OWASP repositories are, nor that public-by-design data such as commit author addresses is not a disclosure. A Bugcrowd submission filed the GitHub commits API of another OWASP repository as PII leakage against this engagement. Add a Scope section to SECURITY.md that names the target, lists what is out of scope, and says a report with no example input is closed as not applicable. Say the same in the ground rules' Out of Bounds section so the two stay in step. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.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.
SECURITY.mdis what GitHub shows a reporter, and it said how to report but not what is in scope. The ground rules said the sanitizer is the target and the project's infrastructure is out of bounds, but not that other OWASP repositories are, nor that public-by-design data such as commit author addresses is not a disclosure. A Bugcrowd submission filed the GitHub commits API of another OWASP repository as PII leakage against this engagement.This adds a Scope section to
SECURITY.mdthat names the target, lists what is out of scope, and says a report with no example input is closed as not applicable, and says the same in the ground rules' Out of Bounds section so the two stay in step.Documentation only. No code or test changes, and no change log entry, as with #511.
🤖 Generated with Claude Code