CVE-2021-22253: Medium severity gitlab vulnerability
Published Aug 23, 2021
·Updated
Improper authorization in GitLab EE affecting all versions since 13.4 allowed a user who previously had the necessary access to trigger deployments to protected environments under specific conditions after the access has been removed
Affected Software
6 affected components
GitLab GitLab>=13.4.0<13.12.9
GitLab GitLab>=13.4.0<13.12.9
GitLab GitLab>=14.0.0<14.0.7
GitLab GitLab>=14.0.0<14.0.7
GitLab GitLab>=14.1.0<14.1.2
GitLab GitLab>=14.1.0<14.1.2
Event History
Aug 23, 2021
CVE Published
via MITRE·07:34 PM
Data Sourced
via MITRE·07:34 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2021-22253?
CVE-2021-22253 has been identified with a high severity due to its impact on unauthorized access to deployments.
2
How do I fix CVE-2021-22253?
To fix CVE-2021-22253, update your GitLab installation to versions 13.12.10, 14.0.8, or 14.1.3 or later.
3
What versions are affected by CVE-2021-22253?
CVE-2021-22253 affects all GitLab versions from 13.4 to 14.1.2.
4
What type of vulnerability is CVE-2021-22253?
CVE-2021-22253 is classified as an improper authorization vulnerability.
5
Can CVE-2021-22253 impact both GitLab Community and Enterprise editions?
Yes, CVE-2021-22253 affects both GitLab Community and Enterprise editions.