What is the severity of CVE-2021-22180?

CVE-2021-22180 is classified as a medium severity vulnerability due to improper access control allowing unauthorized user access.

How do I fix CVE-2021-22180?

To fix CVE-2021-22180, upgrade GitLab to version 13.6.8, 13.7.8, or 13.8.5 or later.

Which versions of GitLab are affected by CVE-2021-22180?

CVE-2021-22180 affects GitLab versions 13.4 and above, up to version 13.8.4.

What type of vulnerability is CVE-2021-22180?

CVE-2021-22180 is an access control vulnerability that allows unauthorized access to analytic pages.

Can exploitations of CVE-2021-22180 lead to data breaches?

Yes, the exploitation of CVE-2021-22180 can potentially lead to unauthorized exposure of sensitive analytic information.

Vulnerability/
CVE-2021-22180

medium

4.3

CWE

425

26/3/2021

3/8/2024

CVE-2021-22180

First published: Fri Mar 26 2021(Updated: )

An issue has been discovered in GitLab affecting all versions starting from 13.4. Improper access control allows unauthorized users to access details on analytic pages.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=13.6.0<13.6.7
GitLab	>=13.6.0<13.6.7
GitLab	>=13.7.0<13.7.7
GitLab	>=13.7.0<13.7.7
GitLab	>=13.8.0<13.8.4
GitLab	>=13.8.0<13.8.4

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-22180?
CVE-2021-22180 is classified as a medium severity vulnerability due to improper access control allowing unauthorized user access.
How do I fix CVE-2021-22180?
To fix CVE-2021-22180, upgrade GitLab to version 13.6.8, 13.7.8, or 13.8.5 or later.
Which versions of GitLab are affected by CVE-2021-22180?
CVE-2021-22180 affects GitLab versions 13.4 and above, up to version 13.8.4.
What type of vulnerability is CVE-2021-22180?
CVE-2021-22180 is an access control vulnerability that allows unauthorized access to analytic pages.
Can exploitations of CVE-2021-22180 lead to data breaches?
Yes, the exploitation of CVE-2021-22180 can potentially lead to unauthorized exposure of sensitive analytic information.

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.6.0
version/gitlab/13.7.0
version/gitlab/13.8.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-22180?
CVE-2021-22180 is classified as a medium severity vulnerability due to improper access control allowing unauthorized user access.
How do I fix CVE-2021-22180?
To fix CVE-2021-22180, upgrade GitLab to version 13.6.8, 13.7.8, or 13.8.5 or later.
Which versions of GitLab are affected by CVE-2021-22180?
CVE-2021-22180 affects GitLab versions 13.4 and above, up to version 13.8.4.
What type of vulnerability is CVE-2021-22180?
CVE-2021-22180 is an access control vulnerability that allows unauthorized access to analytic pages.
Can exploitations of CVE-2021-22180 lead to data breaches?
Yes, the exploitation of CVE-2021-22180 can potentially lead to unauthorized exposure of sensitive analytic information.