|
|
@ -17,15 +17,4 @@ Instead, please send an email to opensource-security[@]github.com. |
|
|
Please include as much of the information listed below as you can to help us better understand and resolve the issue: |
|
|
Please include as much of the information listed below as you can to help us better understand and resolve the issue: |
|
|
|
|
|
|
|
|
* The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting) |
|
|
* The type of issue (e.g., buffer overflow, SQL injection, or cross-site scripting) |
|
|
* Full paths of source file(s) related to the manifestation of the issue |
|
|
|
|
|
* The location of the affected source code (tag/branch/commit or direct URL) |
|
|
|
|
|
* Any special configuration required to reproduce the issue |
|
|
|
|
|
* Step-by-step instructions to reproduce the issue |
|
|
|
|
|
* Proof-of-concept or exploit code (if possible) |
|
|
|
|
|
* Impact of the issue, including how an attacker might exploit the issue |
|
|
|
|
|
|
|
|
|
|
|
This information will help us triage your report more quickly. |
|
|
|
|
|
|
|
|
|
|
|
## Policy |
|
|
|
|
|
|
|
|
|
|
|
See [GitHub's Safe Harbor Policy](https://docs.github.com/en/site-policy/security-policies/github-bug-bounty-program-legal-safe-harbor) |
|
|
|
|
|
|
|
|
* Full paths of source file(s) related to the manifestation of the i |
Elijah
2 years ago
GitHub