2.3 KiB
GitHub Security Policy
Software security researchers are increasingly engaging with Internet companies to hunt down vulnerabilities. Our bounty program gives a tip of the hat to these researchers and provides rewards of $30,000 or more for critical vulnerabilities.
If you’ve found a vulnerability, submit it here.
<<<<<<< HEAD <<<<<<< HEAD <<<<<<< HEAD Even though open source repositories are outside of the scope of our bug bounty program and therefore not eligible for bounty rewards, we will ensure that your finding gets passed along to the appropriate maintainers for remediation.
Reporting Security Issues
If you believe you have found a security vulnerability in any GitHub-owned repository, please report it to us through coordinated disclosure.
Please do not report security vulnerabilities through public GitHub issues, discussions, or pull requests.
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:
- 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
For repositories not covered by the Bug Bounty program, please open an issue.
parent of
5540da0
(Updating security.md file) ======= For repositories not covered by the Bug Bounty program, please open an issue. parent ofade2246
(update security.md) ======= You can find useful information in our rules, scope, targets and FAQ. parent ofd0ad28a
(Update SECURITY.md)