Some checks are pending
docker-build-cometbft / vars (push) Waiting to run
docker-build-cometbft / build-images (amd64, ubuntu-24.04) (push) Blocked by required conditions
docker-build-cometbft / build-images (arm64, ubuntu-24.04-arm) (push) Blocked by required conditions
docker-build-cometbft / merge-images (push) Blocked by required conditions
docker-build-e2e-node / vars (push) Waiting to run
docker-build-e2e-node / build-images (amd64, ubuntu-24.04) (push) Blocked by required conditions
docker-build-e2e-node / build-images (arm64, ubuntu-24.04-arm) (push) Blocked by required conditions
docker-build-e2e-node / merge-images (push) Blocked by required conditions
33 lines
1.6 KiB
Markdown
33 lines
1.6 KiB
Markdown
# How to Report a Security Bug
|
|
|
|
If you believe you have found a security vulnerability in the Interchain Stack,
|
|
you can report it to our primary vulnerability disclosure channel, the [Cosmos
|
|
HackerOne Bug Bounty program][h1].
|
|
|
|
If you prefer to report an issue via email, you may send a bug report to
|
|
<security@interchain.io> with the issue details, reproduction, impact, and other
|
|
information. Please submit only one unique email thread per vulnerability. Any
|
|
issues reported via email are ineligible for bounty rewards.
|
|
|
|
Artifacts from an email report are saved at the time the email is triaged.
|
|
Please note: our team is not able to monitor dynamic content (e.g. a Google Docs
|
|
link that is edited after receipt) throughout the lifecycle of a report. If you
|
|
would like to share additional information or modify previous information,
|
|
please include it in an additional reply as an additional attachment.
|
|
|
|
Please **DO NOT** file a public issue in this repository to report a security
|
|
vulnerability.
|
|
|
|
## Coordinated Vulnerability Disclosure Policy and Safe Harbor
|
|
|
|
For the most up-to-date version of the policies that govern vulnerability
|
|
disclosure, please consult the [HackerOne program page][h1-policy].
|
|
|
|
The policy hosted on HackerOne is the official Coordinated Vulnerability
|
|
Disclosure policy and Safe Harbor for the Interchain Stack, and the teams and
|
|
infrastructure it supports, and it supersedes previous security policies that
|
|
have been used in the past by individual teams and projects with targets in
|
|
scope of the program.
|
|
|
|
[h1]: https://hackerone.com/cosmos?type=team
|
|
[h1-policy]: https://hackerone.com/cosmos?type=team&view_policy=true
|