What is the severity of CVE-2022-0125?

CVE-2022-0125 is classified as a medium severity vulnerability.

How do I fix CVE-2022-0125?

To fix CVE-2022-0125, update your GitLab installation to version 14.4.5 or later, or to version 14.5.3 or later, or to version 14.6.2 or later.

Which versions of GitLab are affected by CVE-2022-0125?

CVE-2022-0125 affects GitLab versions between 12.0 and 14.4.5, 14.5.0 and 14.5.3, and 14.6.0 and 14.6.2.

What type of vulnerability is CVE-2022-0125?

CVE-2022-0125 is a permissions vulnerability that allows unauthorized members to be imported into a project.

Is there a workaround for CVE-2022-0125?

Currently, there is no documented workaround for CVE-2022-0125; the recommended action is to update to a secure version.

Vulnerability/
CVE-2022-0125

medium

4.3

CWE

862

18/1/2022

2/8/2024

CVE-2022-0125

First published: Tue Jan 18 2022(Updated: )

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.

Credit: cve@gitlab.com cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.0<14.4.5
GitLab	>=12.0<14.4.5
GitLab	>=14.5.0<14.5.3
GitLab	>=14.5.0<14.5.3
GitLab	>=14.6.0<14.6.2
GitLab	>=14.6.0<14.6.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-0125?
CVE-2022-0125 is classified as a medium severity vulnerability.
How do I fix CVE-2022-0125?
To fix CVE-2022-0125, update your GitLab installation to version 14.4.5 or later, or to version 14.5.3 or later, or to version 14.6.2 or later.
Which versions of GitLab are affected by CVE-2022-0125?
CVE-2022-0125 affects GitLab versions between 12.0 and 14.4.5, 14.5.0 and 14.5.3, and 14.6.0 and 14.6.2.
What type of vulnerability is CVE-2022-0125?
CVE-2022-0125 is a permissions vulnerability that allows unauthorized members to be imported into a project.
Is there a workaround for CVE-2022-0125?
Currently, there is no documented workaround for CVE-2022-0125; the recommended action is to update to a secure version.

agent/author
agent/type
agent/references
agent/weakness
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-api
agent/software-canonical-lookup-request
collector/nvd-index
vendor/gitlab
canonical/gitlab
version/gitlab/12.0
version/gitlab/14.5.0
version/gitlab/14.6.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2022-0125?
CVE-2022-0125 is classified as a medium severity vulnerability.
How do I fix CVE-2022-0125?
To fix CVE-2022-0125, update your GitLab installation to version 14.4.5 or later, or to version 14.5.3 or later, or to version 14.6.2 or later.
Which versions of GitLab are affected by CVE-2022-0125?
CVE-2022-0125 affects GitLab versions between 12.0 and 14.4.5, 14.5.0 and 14.5.3, and 14.6.0 and 14.6.2.
What type of vulnerability is CVE-2022-0125?
CVE-2022-0125 is a permissions vulnerability that allows unauthorized members to be imported into a project.
Is there a workaround for CVE-2022-0125?
Currently, there is no documented workaround for CVE-2022-0125; the recommended action is to update to a secure version.