goat-cloud reads cloud accounts and, when armed, deletes resources in them. Security reports are prioritised over feature work.
Do not open a public issue or pull request to report a vulnerability.
Report a vulnerability privately
You can also open the reporting form from this repository's Security tab by selecting Report a vulnerability.
Reports are private and accessible to repository administrators, organization owners, security managers, the reporter, and collaborators explicitly added to the advisory. Being listed in CODEOWNERS does not itself grant access. Reports remain private until an authorized maintainer publishes the advisory. See GitHub's advisory permissions for details.
Include: a description of the issue and its impact; reproduction steps or a proof of concept; the affected versions or commits; whether you have shared it elsewhere.
| Step | Target |
|---|---|
| Acknowledgement | 3 working days |
| Triage and severity | 7 working days |
| Fix or mitigation for a confirmed high or critical issue | 30 days, with a coordinated disclosure date agreed with you |
| Public advisory | when the fix is released, crediting you unless you prefer otherwise |
In scope: the code in this repository and the release artifacts built from it. Out of scope: the cloud providers' own services and SDKs (report those to their maintainers, and tell us too if this project's use of them is affected); any deployment you do not own.
Pre-1.0, the latest tagged release is supported. Fixes land on main and are released by tag.
Registered members of the goat user community can receive advance notice of a vulnerability before its public advisory. A recipient receives, privately, the advisory text and the fix as a patch, so the deployments they operate are patched by the time the advisory is published.
When it is used. Only for a vulnerability in this repository's own code that is not already public or easily discoverable, and only once a fix exists. A vulnerability in a dependency that already has a public advisory is handled in the open, through the normal dependency update.
Timing. The advance-notice window sits inside the coordinated disclosure date agreed with the reporter and never moves that date. It is 7 days from the notice by default, may be extended once to 14 days, and always ends at the agreed disclosure date or earlier. The advisory is published at once, ending the window, if the vulnerability is found being exploited, becomes public, or is disclosed by anyone who received notice.
What a recipient may do during the window. Deploy the fix to the deployments they operate, and share the notice with the people who operate them. They may not discuss the vulnerability publicly, publish the patch, or share it with anyone outside those deployments.
Who receives notice. Registered members of the goat user community, as described in the "Advance notice" section of the goat security policy. A registered member is a person who has completed onboarding to one of the community environments the maintainers operate, whose registration is current, and who has linked a GitHub account to that registration. Registration is the admission: there is no separate application.
To link your GitHub account, add your GitHub username to your registration in your community environment's identity service, when you register or at any time afterwards. Registered members are given read access to a private repository, from which notices and patches are distributed, and receive each notice by e-mail. Access ends when the registration ends.