Question

How to secure your GitLab instance from CVE-2021-22205?

Posted November 5, 2021 479 views
SecurityGit

We love that you have chosen to host your source code repo on DigitalOcean. We know how important it is to have organized and up-to-date code for your projects and products. But it’s also important to keep that source-code repo infrastructure up-to-date to avoid potential attacks!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

×
Submit an Answer
1 answer

In April 2021, GitLab disclosed CVE-2021-22205 detailing a trivial Remote Code Execution vulnerability. “Trivial” meaning that it is both (1) easy to execute and (2) can be done by unauthenticated users. On November 1st, this vulnerability was found being actively exploited in the wild, including DigitalOcean customers.
We strongly encourage you to:

Stay up to date with the latest releases to ensure security vulnerabilities are patched. GitLab publishes upgrade instructions for a variety of deployment methodologies here: https://about.gitlab.com/update/.

Follow GitLab’s best practices for securing your environment: https://about.gitlab.com/blog/2020/05/20/gitlab-instance-security-best-practices/.

Ensure you are signed up to receive notifications from GitLab about important security release updates. Visit https://about.gitlab.com/company/contact/ and fill out the form under “Sign up for Security notices.” For those who love RSS feeds: https://about.gitlab.com/security-releases.xml

Patching and downtime can be disruptive to your workflow, however, to protect your project/product, your Droplet, other DigitalOcean customers, and the broader internet community please ensure your infrastructure is up to date!