CVE-2021-22200: High severity gitlab vulnerability
Published Apr 2, 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.
Affected Software
6 affected components
GitLab GitLab>=12.6.0<13.8.7
GitLab GitLab>=12.6.0<13.8.7
GitLab GitLab>=13.9.0<13.9.5
GitLab GitLab>=13.9.0<13.9.5
GitLab GitLab=13.10.0
GitLab GitLab=13.10.0
Event History
Apr 2, 2021
CVE Published
via MITRE·04:22 PM
Data Sourced
via MITRE·04:22 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
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.
2
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.
3
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.
4
What type of vulnerability is CVE-2021-22200?
CVE-2021-22200 is categorized as an access control vulnerability.
5
Can CVE-2021-22200 be exploited by unauthenticated users?
Yes, CVE-2021-22200 can be exploited by anonymous users who access public project forks.