CVE-2021-22237
First published: Wed Aug 25 2021(Updated: )
Under specialized conditions, GitLab may allow a user with an impersonation token to perform Git actions even if impersonation is disabled. This vulnerability is present in GitLab CE/EE versions before 13.12.9, 14.0.7, 14.1.2
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| GitLab | >=13.1.0<13.12.9 | |
| GitLab | >=13.1.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-22237?
CVE-2021-22237 is considered a high-severity vulnerability that allows unauthorized Git actions under specific conditions.
How do I fix CVE-2021-22237?
To remediate CVE-2021-22237, upgrade to GitLab versions 13.12.9, 14.0.7, or 14.1.2 or later.
Who is affected by CVE-2021-22237?
CVE-2021-22237 affects GitLab Community and Enterprise editions prior to the specified patched versions.
What can an attacker do with CVE-2021-22237?
An attacker can perform Git actions using an impersonation token even if impersonation is disabled, potentially leading to unauthorized access.
What versions of GitLab are vulnerable to CVE-2021-22237?
GitLab CE/EE versions before 13.12.9, 14.0.7, and 14.1.2 are vulnerable to CVE-2021-22237.
- agent/type
- agent/references
- agent/author
- agent/weakness
- 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/13.1.0
- version/gitlab/14.0.0
- version/gitlab/14.1.0