What is the severity of CVE-2021-22254?

CVE-2021-22254 is considered a high severity vulnerability due to the potential for user impersonation under specific conditions.

How do I fix CVE-2021-22254?

To fix CVE-2021-22254, users should upgrade to GitLab versions 14.1.3, 14.0.8, or 13.12.10 or later.

What versions of GitLab are affected by CVE-2021-22254?

CVE-2021-22254 affects GitLab CE/EE versions between 13.1.0 and 13.12.9, as well as versions 14.0.0 to 14.0.7 and 14.1.0 to 14.1.2.

What is the impact of CVE-2021-22254 on GitLab users?

The impact of CVE-2021-22254 allows an attacker to impersonate another user, which can lead to unauthorized access and control over accounts.

When was CVE-2021-22254 disclosed?

CVE-2021-22254 was disclosed in 2021 as part of GitLab's vulnerability management process.

Vulnerability/
CVE-2021-22254

medium

4.3

CWE

116

20/8/2021

3/8/2024

CVE-2021-22254

First published: Fri Aug 20 2021(Updated: )

Under very specific conditions a user could be impersonated using Gitlab shell. This vulnerability affects GitLab CE/EE 13.1 and later through 14.1.2, 14.0.7 and 13.12.9.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.1.0<13.12.9
GitLab	>=13.1.0<13.12.9
GitLab	>=14.0.0<14.0.7
GitLab	>=14.0.0<14.0.7
GitLab	>=14.1.0<14.1.2
GitLab	>=14.1.0<14.1.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-22254?
CVE-2021-22254 is considered a high severity vulnerability due to the potential for user impersonation under specific conditions.
How do I fix CVE-2021-22254?
To fix CVE-2021-22254, users should upgrade to GitLab versions 14.1.3, 14.0.8, or 13.12.10 or later.
What versions of GitLab are affected by CVE-2021-22254?
CVE-2021-22254 affects GitLab CE/EE versions between 13.1.0 and 13.12.9, as well as versions 14.0.0 to 14.0.7 and 14.1.0 to 14.1.2.
What is the impact of CVE-2021-22254 on GitLab users?
The impact of CVE-2021-22254 allows an attacker to impersonate another user, which can lead to unauthorized access and control over accounts.
When was CVE-2021-22254 disclosed?
CVE-2021-22254 was disclosed in 2021 as part of GitLab's vulnerability management process.

agent/type
agent/references
agent/author
agent/weakness
agent/softwarecombine
agent/description
collector/mitre-cve
source/MITRE
agent/last-modified-date
agent/severity
agent/event
agent/first-publish-date
agent/source
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/gitlab
canonical/gitlab
version/gitlab/13.1.0
version/gitlab/14.0.0
version/gitlab/14.1.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-2021-22254?
CVE-2021-22254 is considered a high severity vulnerability due to the potential for user impersonation under specific conditions.
How do I fix CVE-2021-22254?
To fix CVE-2021-22254, users should upgrade to GitLab versions 14.1.3, 14.0.8, or 13.12.10 or later.
What versions of GitLab are affected by CVE-2021-22254?
CVE-2021-22254 affects GitLab CE/EE versions between 13.1.0 and 13.12.9, as well as versions 14.0.0 to 14.0.7 and 14.1.0 to 14.1.2.
What is the impact of CVE-2021-22254 on GitLab users?
The impact of CVE-2021-22254 allows an attacker to impersonate another user, which can lead to unauthorized access and control over accounts.
When was CVE-2021-22254 disclosed?
CVE-2021-22254 was disclosed in 2021 as part of GitLab's vulnerability management process.