CVE-2022-0125 Missing authorization in GitLab

Medium 4.3 Published 18 Jan 2022 Updated 2 Aug 2024

GitLab allows project maintainers to import members from target projects without proper access verification, potentially leading to unauthorized privilege escalation.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: Available

What is CVE-2022-0125?

CVE-2022-0125 is a medium-severity missing authorization vulnerability in Gitlab Gitlab, published on 18 Jan 2022. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

An issue has been discovered in GitLab affecting all versions starting from 12.0 before 14.4.5, all versions starting from 14.5.0 before 14.5.3, all versions starting from 14.6.0 before 14.6.2. GitLab was not verifying that a maintainer of a project had the right access to import members from a target project.

Weakness: CWE-862

Which versions are affected by CVE-2022-0125?

1 open source package ship an affected version, including gitlab. It affects 1 product.

Package	Affected	Fixed in
`gitlab` Bitnami	From `12.0.0`	`14.4.5, 14.5.3, 14.6.2`

Products include Gitlab Gitlab.

How do I fix CVE-2022-0125?

Upgrade gitlab to a fixed version for your release line: 14.4.5, 14.5.3 or 14.6.2.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2022-0125 being exploited?

There is no known exploitation of CVE-2022-0125 in the wild and no public exploit code.

All Gitlab Gitlab vulnerabilities

Sources

Also known as BIT-gitlab-2022-0125, GHSA-75xf-j8f2-9vxq, UBUNTU-CVE-2022-0125.