Security readout for executives and security teams
Plain-English summary
This GitLab issue could cause OAuth tokens for new subscriptions to be created against the wrong OAuth client application. That can create access-control confusion and limited confidentiality, integrity, or availability impact. The known affected range is GitLab CE/EE 14.1 before 14.1.2.
Executive priority
Treat as a moderate remediation item. Prioritize affected public or business-critical GitLab instances, but the available evidence does not support emergency action absent exposure or suspicious OAuth activity.
Technical view
CVE-2021-22236 is improper handling of OAuth client IDs in GitLab CE/EE. The CVSS 3.1 score is 5.5 with network attack vector, low complexity, low privileges required, and user interaction required. Sources identify affected versions as >=14.1 and <14.1.2.
Likely exposure
Exposure is most likely for self-managed GitLab CE/EE instances running version 14.1.0 or 14.1.1, especially where subscription and OAuth token flows were used during that period.
Exploitation context
The provided sources do not show CISA KEV listing or active exploitation. The CVSS vector indicates exploitation requires low privileges and user interaction, reducing urgency compared with unauthenticated remote flaws.
Researcher notes
Evidence is limited to the CVE description, version range, CVSS vector, and GitLab references. No CWE, exploit evidence, or detailed patch notes are included in the supplied bundle.
Mitigation direction
- Upgrade GitLab CE/EE to a version outside >=14.1 and <14.1.2.
- Check GitLab vendor guidance before choosing compensating controls.
- Review OAuth applications related to subscription flows.
- Revoke suspicious or unnecessary OAuth tokens created during the exposure window.
Validation and detection
- Inventory GitLab CE/EE versions across self-managed instances.
- Flag any instance running 14.1.0 or 14.1.1.
- Review subscription-related OAuth client configuration for unexpected application mappings.
- Check OAuth token records for unusual creation tied to new subscriptions.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2021-22236 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L2.13.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.5MediumVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L
Source materials
- CVE List V5 sourceCVE List V5
- https://gitlab.com/gitlab-org/gitlab/-/issues/334925CVE reference · x_refsource_MISC
- https://gitlab.com/gitlab-org/cves/-/blob/master/2021/CVE-2021-22236.jsonCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.