Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cosmos SDK Security Advisory: Release coordination for Cosmos SDK Barberry #80

Closed
greg-szabo opened this issue Jun 7, 2023 · 1 comment · Fixed by #82
Closed

Cosmos SDK Security Advisory: Release coordination for Cosmos SDK Barberry #80

greg-szabo opened this issue Jun 7, 2023 · 1 comment · Fixed by #82
Milestone

Comments

@greg-szabo
Copy link

The Cosmos SDK team has notified the community that a high-severity security issue patch will be released on June 8th, 16:00UTC. I am contacting you because your network is running an impacted version of the Cosmos SDK and to give advanced notice to prepare for security patch coordination. The patch can be applied without a consensus upgrade and will require at least 33.3% of the validators to update their nodes as quickly as possible to protect the network from exploitation.

When the Cosmos SDK patch is available, it is the responsibility of each network to validate it as quickly as possible, have a security release for the network binary as soon as possible, and coordinate with the network validators to upgrade their nodes as early as possible.

I am contacting you here because there was no e-mail address listed in the SECURITY.MD file for the repository or the SECURITY.MD file is missing. Please populate a SECURITY.MD file with the relevant information for subsequent reach-outs regarding security updates.

You can find more information on the link above.

@johnletey
Copy link
Member

Thanks for opening this issue @greg-szabo.

The team is aware of the Barberry Advisory, and is ready to release a patch.

We're also adding a SECURITY.md file for future advisories. (See #81)

@johnletey johnletey added this to the v1.2.2 milestone Jun 8, 2023
@johnletey johnletey linked a pull request Jun 8, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants