What is the severity of CVE-2021-22200?

CVE-2021-22200 is considered a high-severity vulnerability due to the potential for unauthorized data access.

How do I fix CVE-2021-22200?

To mitigate CVE-2021-22200, upgrade GitLab to the latest patch version, specifically 13.10.0 or later.

Who is affected by CVE-2021-22200?

CVE-2021-22200 affects all versions of GitLab CE/EE starting from 12.6.0 up to 13.8.7.

What type of vulnerability is CVE-2021-22200?

CVE-2021-22200 is categorized as an access control vulnerability.

Can CVE-2021-22200 be exploited by unauthenticated users?

Yes, CVE-2021-22200 can be exploited by anonymous users who access public project forks.

Vulnerability/
CVE-2021-22200

high

7.5

2/4/2021

3/8/2024

CVE-2021-22200

First published: Fri Apr 02 2021(Updated: )

An issue has been discovered in GitLab CE/EE affecting all versions starting with 12.6. Under a special condition it was possible to access data of an internal repository through a public project fork as an anonymous user.

Credit: cve@gitlab.com

Affected Software	Affected Version	How to fix
GitLab	>=12.6.0<13.8.7
GitLab	>=12.6.0<13.8.7
GitLab	>=13.9.0<13.9.5
GitLab	>=13.9.0<13.9.5
GitLab	=13.10.0
GitLab	=13.10.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2021-22200?
CVE-2021-22200 is considered a high-severity vulnerability due to the potential for unauthorized data access.
How do I fix CVE-2021-22200?
To mitigate CVE-2021-22200, upgrade GitLab to the latest patch version, specifically 13.10.0 or later.
Who is affected by CVE-2021-22200?
CVE-2021-22200 affects all versions of GitLab CE/EE starting from 12.6.0 up to 13.8.7.
What type of vulnerability is CVE-2021-22200?
CVE-2021-22200 is categorized as an access control vulnerability.
Can CVE-2021-22200 be exploited by unauthenticated users?
Yes, CVE-2021-22200 can be exploited by anonymous users who access public project forks.

agent/references
agent/type
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/12.6.0
version/gitlab/13.9.0
version/gitlab/13.10.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-22200?
CVE-2021-22200 is considered a high-severity vulnerability due to the potential for unauthorized data access.
How do I fix CVE-2021-22200?
To mitigate CVE-2021-22200, upgrade GitLab to the latest patch version, specifically 13.10.0 or later.
Who is affected by CVE-2021-22200?
CVE-2021-22200 affects all versions of GitLab CE/EE starting from 12.6.0 up to 13.8.7.
What type of vulnerability is CVE-2021-22200?
CVE-2021-22200 is categorized as an access control vulnerability.
Can CVE-2021-22200 be exploited by unauthenticated users?
Yes, CVE-2021-22200 can be exploited by anonymous users who access public project forks.