A critical security release is made when the severity, impact, and priority of an issue requires mitigation as soon as possible.
For each critical security release, there will be three blog posts.
This is intended to be a template and suggested schedule for actions required for GitLab to respond to critical vulnerabilities. Steps include actions taken from the moment the vulnerability is discovered/reported up to the final package deployments and announcements. This assumes that a critical patch will take roughly one week to deploy, however this will vary depending on the vulnerability and number of releases to be patched.
Also see the general security release process for more details on what needs to be done to create a security release.
### First steps: - [ ] Create a confidential issue for diagnosing, discussing, and mitigating the vulnerability in the GitLab CE repository. - [ ] Create a confidential issue for the release (using the rest of this document as a rough template). Include a reference to the vulnerability issue and merge request when it exists. This issue should include information on which releases are vulnerable and which will receive a patch. - [ ] Branch off of the dev gitlabhq/security-X-Y branch for pushing patches (X and Y are the major and minor versions for the current release). If a branch for the current release does not exist, create one by branching off of X-Y-stable. - [ ] Designate a "security release manager" to act as the release manager for this security release. By default, the security release manager is the RM from the _previous_ release. Having one RM for the security release - even though a security release will typically span multiple prior versions - is more efficient and less likely to lead to confusion or unintended "leaking" of the vulnerability. By designating the RM from the _previous_ release, the RM for the _current_ release is not hindered in their work to get out the next release (candidate). - [ ] Create a Work-In-Progress merge request against dev security-X-Y branch, assign to the release manager. - [ ] Fix build failures (owner: release manager) - [ ] Install mitigation for GitLab.com, GitHost.io (if possible) and any other vulnerable infrastructure hosts, create an issue in the infrastructure project describing the mitigation and impact. ### Day one: - [ ] Merge all patches to dev.gitlab.org security-X-Y branch (owner: dev team) - [ ] Write pre-announcement blog post (owner: security lead) - Do NOT pre-announce affected versions - [ ] Send pre-announcement e-mail to general security list and contacts (owners: customer relations / marketing) - [ ] Notify marketing group of critical security issue so they are ready to respond to inquiries (owner: security team) - [ ] Contact package maintainers about security announcement (e.g. GitSwarm, Debian, FreeBSD) (owner: security team) - [ ] Request pre-assigned CVE (owner: security team) ### Day two: - [ ] Cherry-pick all patches to releases -> stable branches including backports (owner: release manager) - [ ] Validate security fixes for current release (owner: dev team) - [ ] Write WIP second and third blog posts against www-gitlab-com on dev.gitlab.org about security update, mitigation steps (include HAProxy/Apache/nginx workarounds): (owner: security team) ### Day three: - [ ] Build packages to private PackageCloud package repository (latest stable and patches) (owner: release manager & build team) - [ ] Validate security fixes on dedicated test instances for each package (owner: dev team) - [ ] Deploy to staging (owner: release manager) - [ ] Deploy to GitLab.com (owners: infrastructure) - [ ] Remove mitigation from infrastructure hosts and close issue. (owner: infrastructure) ### Day four (before 12:00 UTC): - [ ] Build packages for all versions to private PackageCloud package repository (owners: build team) - [ ] Write second blog post with high-level information about vulnerabilities (owner: security team) - [ ] Write CVE notice for CVE-ID provider (owner: security team) ### Day four (before 23:59 UTC): - [ ] Publish security packages to public (owner: build team) - [ ] Publish latest security Docker images (owner: build team) - [ ] Publish latest code to GitLab.com (owner: release manager) - [ ] Add version.gitlab.com entries (owner: release manager) - [ ] Update GitHost.io (owner: githost / infrastructure) - [ ] Send CVE notice to CVE-ID provider (owner: security team) - [ ] Publish second blog post (owner: marketing) - [ ] Email, Tweet, etc. (owner: marketing) - [ ] Update vulnerability acknowledgements (owner: security team) - [ ] Follow-up with disclosure reports to inform/thank security researchers (owner: security team) - [ ] Approve request(s) for disclosure on HackerOne (owner: security team) _Note that we should not publish code or the packages to the public until everything is ready._ ### Afterwards: - [ ] 30 days after announcement blog, write and post third blog with details of vulnerability (owner: security team) - [ ] Remove confidentiality from disclosure issues. (owner: security team) - [ ] "Lessons learned" writeup / blog post. (owner: security team)