CVE-2021-22253
First published: Mon 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
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=13.4.0<13.12.9 | |
| GitLab | >=13.4.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
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
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.
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.
What versions are affected by CVE-2021-22253?
CVE-2021-22253 affects all GitLab versions from 13.4 to 14.1.2.
What type of vulnerability is CVE-2021-22253?
CVE-2021-22253 is classified as an improper authorization vulnerability.
Can CVE-2021-22253 impact both GitLab Community and Enterprise editions?
Yes, CVE-2021-22253 affects both GitLab Community and Enterprise editions.
- 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.4.0
- version/gitlab/14.0.0
- version/gitlab/14.1.0