Coordinated Vulnerability Disclosure Policy
The Cosmos ecosystem believes that strong security is a blend of highly technical security researchers who care about security and the forward progression of the ecosystem and the attentiveness and openness of Cosmos core contributors to help continually secure our operations.
IMPORTANT: DO NOT open public issues on this repository for security vulnerabilities.
Scope​
| Scope |
|---|
| last release (tagged) |
| main branch |
The latest release tag of this repository is supported for security updates as well as the main branch. Security vulnerabilities should be reported if the vulnerability can be reproduced on either one of those.
Reporting a Vulnerability​
| Reporting methods | Bounty eligible |
|---|---|
| HackerOne program | yes |
| security@interchain.io | no |
Issues identified in this repository may be eligible for a bug bounty. For your report to be bounty eligible it must be reported exclusively through the HackerOne Bug Bounty.
If you do not wish to be eligible for a bounty or do not want to use the HackerOne platform to report an issue, please send your report via email to security@interchain.io with reproduction steps and details of the issue.
Guidelines​
We require that all researchers:
- Abide by this policy to disclose vulnerabilities, and avoid posting vulnerability information in public places, including GitHub, Discord, Telegram, and Twitter.
- Make every effort to avoid privacy violations, degradation of user experience, disruption to production systems (including but not limited to the Cosmos Hub), and destruction of data.
- Keep any information about vulnerabilities that you’ve discovered confidential between yourself and the Cosmos engineering team until the issue has been resolved and disclosed.
- Avoid posting personally identifiable information, privately or publicly.
If you follow these guidelines when reporting an issue to us, we commit to:
- Not pursue or support any legal action related to your research on this vulnerability
- Work with you to understand, resolve and ultimately disclose the issue in a timely fashion
More information​
- See TIMELINE.md for an example timeline of a disclosure.
- See DISCLOSURE.md to see more into the inner workings of the disclosure process.
- See EXAMPLES.md for some of the examples that we are interested in for the bug bounty program.