LiveActive security incident?Get immediate response
CVE Record

CVE-2021-22253: Improper authorization in GitLab EE affecting all versions since 13.4 allowed a user who previously had the...

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

MediumCVSS 4.9Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Revoked deployment access might not fully take effect in affected GitLab EE versions. Someone who used to be allowed to deploy could still trigger deployments to protected environments, creating risk of unauthorized releases or disruption. It is not a broad takeover bug, but it affects release control.

Executive priority

Treat as a targeted release-control risk, not an emergency internet-wide issue. Prioritize remediation where GitLab controls production or sensitive deployments, especially in environments with recent staffing, contractor, or role changes.

Technical view

CVE-2021-22253 is an improper authorization issue in GitLab EE. An authenticated user who previously had deployment rights could, under specific conditions, trigger deployments to protected environments after access was removed. CVSS is 4.9 with high attack complexity, low privileges required, and low integrity and availability impact.

Likely exposure

Exposure is limited to GitLab EE versions >=13.4 and below 13.12.9, 14.0 below 14.0.7, and 14.1 below 14.1.2, especially instances using protected environments and deployment permissions.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. Practical risk depends on whether former authorized deployers still have account access and whether protected environment deployments are security or operations sensitive.

Researcher notes

The public description confirms the authorization failure but does not detail the exact triggering conditions. Avoid assuming broader privilege escalation. Focus validation on protected environments, revoked deployment rights, and affected GitLab EE version ranges.

Mitigation direction

  • Upgrade affected GitLab EE instances to a non-affected version or later.
  • Review GitLab vendor guidance for any environment-specific remediation notes.
  • Remove or disable accounts that no longer need GitLab access.
  • Audit protected environment deployment permissions after role or membership changes.
  • Review recent deployments by users whose deployment access was revoked.

Validation and detection

  • Inventory GitLab EE versions and compare them with the affected ranges.
  • Identify projects using protected environments and deployment approvals.
  • Check whether revoked users can still initiate protected environment deployments.
  • Review deployment logs for activity after permission removal.
  • Confirm access revocation workflows remove project and group deployment rights.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2021-22253 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L

Official CVE source material

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.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We 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.

ScoreVersionSeverityVectorExploitImpactSource
4.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L1.82.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

4.9Medium
CVSS 3.1 vector shape for CVE-2021-22253Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:N/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GitLabGitLab>=13.4, <13.12.9, >=14.0, <14.0.7, >=14.1, <14.1.2Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.