|
| 1 | +# Keep the sections and prompts aligned with |
| 2 | +# .agents/skills/create-security-advisory/assets/advisory-template.md. |
| 3 | +name: Private vulnerability report |
| 4 | +description: Report an OpenShell vulnerability privately using the required advisory template. |
| 5 | +body: |
| 6 | + - type: markdown |
| 7 | + attributes: |
| 8 | + value: | |
| 9 | + Follow [SECURITY.md](https://github.com/NVIDIA/OpenShell/blob/main/SECURITY.md) and the [advisory template](https://github.com/NVIDIA/OpenShell/blob/main/.agents/skills/create-security-advisory/assets/advisory-template.md). |
| 10 | +
|
| 11 | + Review the report and verify its accuracy before submitting. Distinguish reproduced behavior, code inspection, and unverified claims. Remove secrets and personal information from evidence. |
| 12 | +
|
| 13 | + - type: textarea |
| 14 | + id: summary-and-impact |
| 15 | + attributes: |
| 16 | + label: Summary and impact |
| 17 | + description: Describe what the attacker can do, which security boundary should prevent it, and the demonstrated impact. Separate unverified consequences. |
| 18 | + placeholder: Summarize the vulnerability and its impact in two or three sentences. |
| 19 | + validations: |
| 20 | + required: true |
| 21 | + |
| 22 | + - type: textarea |
| 23 | + id: scope-and-prerequisites |
| 24 | + attributes: |
| 25 | + label: Scope and prerequisites |
| 26 | + description: Include each item below. Separate the tested revision from confirmed affected releases. For unknowns, state what needs checking. |
| 27 | + placeholder: | |
| 28 | + - Product and tested version: Component, release or full commit SHA; image digest if relevant. |
| 29 | + - Affected versions: Confirmed release range and evidence, or Unknown with the needed check. |
| 30 | + - Environment and configuration: Relevant OS, runtime/driver, topology, and exact settings; default or opt-in. |
| 31 | + - Attacker access: Starting privileges, controlled input, and resources in scope. |
| 32 | + validations: |
| 33 | + required: true |
| 34 | + |
| 35 | + - type: textarea |
| 36 | + id: reproduction-and-evidence |
| 37 | + attributes: |
| 38 | + label: Reproduction and evidence |
| 39 | + description: Provide reproduction steps and observed results, or concrete code evidence of the attack path. State what was verified and what was not run; scanner output alone is insufficient. |
| 40 | + placeholder: | |
| 41 | + Verification status: Reproduced / code inspection only / reporter claim not reproduced. |
| 42 | +
|
| 43 | + 1. Operator setup: Minimal prerequisites, test resources, and copyable commands/configuration. |
| 44 | + 2. Attacker actions: Exact steps under the privileges stated above. |
| 45 | + 3. Check: Read back the response or state change that demonstrates the impact. |
| 46 | +
|
| 47 | + Expected: Security-preserving behavior; link the applicable policy, contract, or enforcing code. |
| 48 | + Observed: Actual result and concise redacted output; if not executed, say so. |
| 49 | +
|
| 50 | + Link the source report, private artifacts, and relevant code at an immutable revision. |
| 51 | + State who verified what and any failed attempts or limitations. |
| 52 | + validations: |
| 53 | + required: true |
| 54 | + |
| 55 | + - type: textarea |
| 56 | + id: additional-details |
| 57 | + attributes: |
| 58 | + label: Additional details |
| 59 | + description: Include supported optional details that help review. Leave blank if none are available. |
| 60 | + placeholder: | |
| 61 | + Root cause, severity rationale and CVSS/CWE, existing CVE identifiers, |
| 62 | + disclosure deadlines, a proposed fix or verified workaround, known |
| 63 | + unaffected deployments, or a related private PR. |
| 64 | + validations: |
| 65 | + required: false |
| 66 | + |
| 67 | + - type: textarea |
| 68 | + id: open-questions |
| 69 | + attributes: |
| 70 | + label: Open questions |
| 71 | + description: List missing evidence that affects the assessment and the next check for each gap. Leave blank if there are no known gaps. |
| 72 | + validations: |
| 73 | + required: false |
0 commit comments