Home > Blockchain >  GitLab: prevent new users from assigning admin privileges to themselves
GitLab: prevent new users from assigning admin privileges to themselves

Time:12-04

I know this looks like a dumb question, but I just found out that, last month, something terrible happened to my GitLab instance: someone signed up on it and became admin himself, without my invitation, as I was the only administrator. So he wiped off every internal and/or private project inside of it, groups too (and I don't even know whether he had stolen all of them before erasing or not, I'm worried because they were proprietary code). How did it happen? Does this have anything to do with, since the version was CE-13.3.0? If so, would version upgrading be enough to be safer, or should I make some particular configurations, such as disabling sign up page?

CodePudding user response:

It is best to follow "GitLab instance: security best practices", which does include indeed:

Ensure open sign-up is disabled on your instance.

Open registration is disabled by default on self-managed instances with GitLab 13.6 and above installed.
If new sign-up is enabled and your instance is open to the internet, anyone can sign up and access data.

Administrators who would like to further restrict access on their instance can follow our documentation on how to configure user access.

Regarding the CVE mentioned, follow also "Action needed by self-managed customers in response to CVE-2021-22205", in your case: "CVE-2021-22205: How to determine if a self-managed instance has been impacted" (unless the log events have been wiped out as well).

  • Related