What is the severity of CVE-2022-0549?

CVE-2022-0549 is classified as a medium severity vulnerability due to its potential impact on user access control.

How do I fix CVE-2022-0549?

To mitigate CVE-2022-0549, upgrade GitLab to version 14.3.6, 14.4.4 or later, or 14.5.2 or later.

Who is affected by CVE-2022-0549?

CVE-2022-0549 affects all versions of GitLab CE/EE prior to 14.3.6 and specific versions between 14.4 and 14.5.

What types of attacks are possible with CVE-2022-0549?

CVE-2022-0549 could allow unprivileged users to add other users to groups, potentially leading to unauthorized access.

Is there a workaround for CVE-2022-0549?

There are no official workarounds for CVE-2022-0549; upgrading to a patched version is the recommended solution.

Vulnerability/
CVE-2022-0549

medium

6.5

28/3/2022

2/8/2024

CVE-2022-0549

First published: Mon Mar 28 2022(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions before 14.3.6, all versions starting from 14.4 before 14.4.4, all versions starting from 14.5 before 14.5.2. Under certain conditions, GitLab REST API may allow unprivileged users to add other users to groups even if that is not possible to do through the Web UI.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.2<14.6.5
GitLab	>=13.2<14.6.5
GitLab	>=14.7<14.7.4
GitLab	>=14.7<14.7.4
GitLab	>=14.8<14.8.2
GitLab	>=14.8<14.8.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2022-0549?
CVE-2022-0549 is classified as a medium severity vulnerability due to its potential impact on user access control.
How do I fix CVE-2022-0549?
To mitigate CVE-2022-0549, upgrade GitLab to version 14.3.6, 14.4.4 or later, or 14.5.2 or later.
Who is affected by CVE-2022-0549?
CVE-2022-0549 affects all versions of GitLab CE/EE prior to 14.3.6 and specific versions between 14.4 and 14.5.
What types of attacks are possible with CVE-2022-0549?
CVE-2022-0549 could allow unprivileged users to add other users to groups, potentially leading to unauthorized access.
Is there a workaround for CVE-2022-0549?
There are no official workarounds for CVE-2022-0549; upgrading to a patched version is the recommended solution.

agent/type
agent/references
agent/author
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/first-publish-date
agent/event
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/13.2
version/gitlab/14.7
version/gitlab/14.8

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-0549?
CVE-2022-0549 is classified as a medium severity vulnerability due to its potential impact on user access control.
How do I fix CVE-2022-0549?
To mitigate CVE-2022-0549, upgrade GitLab to version 14.3.6, 14.4.4 or later, or 14.5.2 or later.
Who is affected by CVE-2022-0549?
CVE-2022-0549 affects all versions of GitLab CE/EE prior to 14.3.6 and specific versions between 14.4 and 14.5.
What types of attacks are possible with CVE-2022-0549?
CVE-2022-0549 could allow unprivileged users to add other users to groups, potentially leading to unauthorized access.
Is there a workaround for CVE-2022-0549?
There are no official workarounds for CVE-2022-0549; upgrading to a patched version is the recommended solution.