fix(fuzz): don't auto-file public GitHub issues from OSS-Fuzz findings (#1092) - #1118
Merged
Merged
Conversation
#1092) Flagged in review on the submission PR (google/oss-fuzz#15924) by a project maintainer: file_github_issue: true means OSS-Fuzz auto-files a *public* GitHub issue on this repo the instant it finds a crash. For a project whose entire reason for adding fuzzing is 15 externally reported CVEs in one year, that's backwards - it discloses a vulnerability, potentially with a reproducer attached, before anyone here has had a chance to look at it privately. Set to false. Findings now route to primary_contact by email instead, which is what OSS-Fuzz's own responsible-disclosure timeline (private first, then public after a fix ships or 90 days pass) actually assumes.
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
2 participants
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.
Flagged in review on the submission PR (google/oss-fuzz#15924) by a project maintainer:
file_github_issue: truemeans OSS-Fuzz auto-files a public GitHub issue on this repo the instant it finds a crash. For a project whose entire reason for adding fuzzing is 15 externally reported CVEs in one year, that's backwards - it discloses a vulnerability, potentially with a reproducer attached, before anyone here has had a chance to look at it privately.Set to
false. Findings now route toprimary_contactby email instead, which is what OSS-Fuzz's own responsible-disclosure timeline (private first, then public after a fix ships or 90 days pass) actually assumes.🤖 Generated with Claude Code
https://claude.ai/code/session_01NBmWiWg46r8BLbdwozKo6v