What is the severity of CVE-2021-22250?

CVE-2021-22250 is rated as a high severity vulnerability due to improper authorization allowing unauthorized access to impersonation tokens.

How do I fix CVE-2021-22250?

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

Who is affected by CVE-2021-22250?

CVE-2021-22250 affects all versions of GitLab CE and EE from version 13.3 to 14.1.2.

What types of tokens can be accessed due to CVE-2021-22250?

CVE-2021-22250 allows unauthorized users to view and delete impersonation tokens created by administrators.

What is the impact of CVE-2021-22250?

The impact of CVE-2021-22250 includes the potential for unauthorized users to compromise the security of administrator impersonation tokens.

Vulnerability/
CVE-2021-22250

medium

5.5

25/8/2021

3/8/2024

CVE-2021-22250

First published: Wed Aug 25 2021(Updated: )

Improper authorization in GitLab CE/EE affecting all versions since 13.3 allowed users to view and delete impersonation tokens that administrators created for their account

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.3.0<13.12.9
GitLab	>=13.3.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-22250?
CVE-2021-22250 is rated as a high severity vulnerability due to improper authorization allowing unauthorized access to impersonation tokens.
How do I fix CVE-2021-22250?
To fix CVE-2021-22250, upgrade to GitLab versions 13.12.10, 14.0.8, or 14.1.3 or later.
Who is affected by CVE-2021-22250?
CVE-2021-22250 affects all versions of GitLab CE and EE from version 13.3 to 14.1.2.
What types of tokens can be accessed due to CVE-2021-22250?
CVE-2021-22250 allows unauthorized users to view and delete impersonation tokens created by administrators.
What is the impact of CVE-2021-22250?
The impact of CVE-2021-22250 includes the potential for unauthorized users to compromise the security of administrator impersonation tokens.

agent/references
agent/author
agent/softwarecombine
agent/description
agent/type
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.3.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-22250?
CVE-2021-22250 is rated as a high severity vulnerability due to improper authorization allowing unauthorized access to impersonation tokens.
How do I fix CVE-2021-22250?
To fix CVE-2021-22250, upgrade to GitLab versions 13.12.10, 14.0.8, or 14.1.3 or later.
Who is affected by CVE-2021-22250?
CVE-2021-22250 affects all versions of GitLab CE and EE from version 13.3 to 14.1.2.
What types of tokens can be accessed due to CVE-2021-22250?
CVE-2021-22250 allows unauthorized users to view and delete impersonation tokens created by administrators.
What is the impact of CVE-2021-22250?
The impact of CVE-2021-22250 includes the potential for unauthorized users to compromise the security of administrator impersonation tokens.