Security readout for executives and security teams
Plain-English summary
This GitLab EE issue could let an authenticated user bypass a configured user cap through single sign-on user creation. Business impact is mainly governance and licensing/control failure, with limited confidentiality and integrity impact in the published CVSS data.
Executive priority
Treat as moderate priority. Prioritize affected externally reachable GitLab EE instances using SSO, especially where user caps enforce licensing, onboarding, or access-control boundaries.
Technical view
CVE-2021-22240 is an improper access control flaw in GitLab EE. Affected ranges are 13.7 through before 13.11.6, 13.12 before 13.12.6, and 14.0 before 14.0.2. The vector is network-accessible, high complexity, low privileges, no user interaction, with limited confidentiality and integrity impact.
Likely exposure
Exposure is likely limited to GitLab EE deployments in the affected version ranges that use SSO and rely on the user cap control.
Exploitation context
The bundle does not show CISA KEV listing or other evidence of active exploitation. Exploitation requires low privileges and appears conditional on SSO and user-cap configuration.
Researcher notes
The published CVSS is 4.2 with AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N. Sources do not provide enough evidence here to claim broad exploitability, public exploitation, or impact beyond SSO user-cap bypass.
Mitigation direction
- Upgrade GitLab EE beyond the affected version range for your maintained branch.
- Review GitLab vendor guidance for the exact fixed release path.
- Confirm SSO user creation and user cap settings match intended policy.
- Review newly created SSO users during the vulnerable period.
Validation and detection
- Inventory GitLab EE version and confirm it is not in the affected ranges.
- Check whether SSO is enabled and user cap enforcement is configured.
- Review audit logs for unexpected user creation through SSO.
- Confirm user counts and licensed users match administrative expectations.
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-22240 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
- 4.2 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
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:H/PR:L/UI:N/S:U/C:L/I:L/A:N1.62.5Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
4.2MediumVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://gitlab.com/gitlab-org/gitlab/-/issues/327641CVE reference · x_refsource_MISC
- https://hackerone.com/reports/1166566CVE reference · x_refsource_MISC
- https://gitlab.com/gitlab-org/cves/-/blob/master/2021/CVE-2021-22240.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.