Repository navigation
feat: add security finding issue template #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
Timur Tukaev (tym83)
wants to merge
3
commits into
cozystack:main
Choose a base branch
from
tym83:feat/security-issue-template
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,95 @@ | ||
| name: Security Finding | ||
| description: Report an automated security scanner finding (for maintainers) | ||
| title: "[security] <package>: <vulnerability ID>" | ||
| labels: ["security/triage-needed"] | ||
| body: | ||
| - type: markdown | ||
| attributes: | ||
| value: | | ||
| **This template is for automated scanner findings reviewed by maintainers.** | ||
| If you are an external reporter, please use [Private Vulnerability Reporting](https://github.com/cozystack/cozystack/security/advisories/new) or email cncf-cozystack-security@lists.cncf.io instead. | ||
| - type: input | ||
| id: vulnerability_id | ||
| attributes: | ||
| label: Vulnerability ID | ||
| description: CVE where one is assigned, otherwise the GHSA or other advisory ID. | ||
| placeholder: "e.g., CVE-YYYY-NNNNN or GHSA-xxxx-xxxx-xxxx" | ||
| validations: | ||
| required: true | ||
| - type: input | ||
| id: scanner | ||
| attributes: | ||
| label: Scanner | ||
| placeholder: "e.g., Trivy, Grype, osv-scanner, Dependabot" | ||
| validations: | ||
| required: true | ||
| - type: input | ||
| id: finding_id | ||
| attributes: | ||
| label: Scanner finding ID | ||
| description: Rule ID, alert URL or other identifier the scanner gives this finding, if any. Used to match repeat reports of the same finding across scan runs. | ||
| placeholder: "e.g., https://github.com/cozystack/cozystack/security/code-scanning/123" | ||
| - type: dropdown | ||
| id: severity | ||
| attributes: | ||
| label: Severity | ||
| options: | ||
| - Critical | ||
| - High | ||
| - Medium | ||
| - Low | ||
| validations: | ||
| required: true | ||
| - type: input | ||
| id: package | ||
| attributes: | ||
| label: Affected package | ||
| placeholder: "e.g., libcrypto3, stdlib, redis" | ||
| validations: | ||
| required: true | ||
| - type: input | ||
| id: installed_version | ||
| attributes: | ||
| label: Installed version | ||
| placeholder: "e.g., 3.5.1-r0" | ||
| - type: input | ||
| id: fixed_version | ||
| attributes: | ||
| label: Fixed version | ||
| placeholder: "e.g., 3.5.5-r0 (or 'none available')" | ||
| - type: textarea | ||
| id: affected_components | ||
| attributes: | ||
| label: Affected Cozystack components | ||
| placeholder: | | ||
| - packages/system/velero | ||
| - packages/apps/postgres | ||
| validations: | ||
| required: true | ||
| - type: textarea | ||
| id: description | ||
| attributes: | ||
| label: Description | ||
| placeholder: Brief description of the vulnerability and its impact | ||
| validations: | ||
| required: true | ||
| - type: textarea | ||
| id: references | ||
| attributes: | ||
| label: References | ||
| placeholder: | | ||
| - https://nvd.nist.gov/vuln/detail/CVE-YYYY-NNNNN | ||
| - https://github.com/advisories/GHSA-XXXX | ||
| - type: dropdown | ||
| id: triage_status | ||
| attributes: | ||
| label: Triage status | ||
| options: | ||
| - new (needs triage) | ||
| - confirmed | ||
| - false-positive | ||
| - accepted-risk | ||
| - in-progress | ||
| - fixed | ||
| validations: | ||
| required: true | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
cvefield is mandatory, but not all security findings have a CVE ID (e.g., they might have a GHSA ID or be an internal finding). It is better to use a more inclusive label like 'Vulnerability ID' and update the placeholder to reflect this. I also suggest renaming the ID tovulnerability_idfor clarity.