LiveActive security incident?Get immediate response
CVE Record

CVE-2021-22252: A confusion between tag and branch names in GitLab CE/EE affecting all versions since 13.7 allowed a Develo...

A confusion between tag and branch names in GitLab CE/EE affecting all versions since 13.7 allowed a Developer to access protected CI variables which should only be accessible to Maintainers

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

Security readout for executives and security teams

Plain-English summary

This GitLab flaw could let a user with Developer access see protected CI variables that should be limited to Maintainers. Those variables often contain deployment tokens, credentials, or environment secrets, so the business risk is unauthorized secret disclosure rather than system takeover.

Executive priority

Treat this as a moderate-priority secrets exposure issue. It is not described as unauthenticated or actively exploited, but compromised CI variables can enable downstream access to cloud, deployment, or production systems.

Technical view

GitLab CE/EE versions from 13.7 through affected 13.12, 14.0, and 14.1 releases confused tag and branch names. With low-privileged authenticated access as Developer, an attacker could access protected CI variables. CVSS 3.1 is 6.5, with high confidentiality impact and no integrity or availability impact stated.

Likely exposure

Exposure is limited to GitLab CE/EE instances in the affected version ranges where Developers exist on projects using protected CI variables. Internet exposure is not required by the CVSS data, but network access and authenticated Developer privileges are required.

Exploitation context

The provided bundle does not show CISA KEV listing or confirmed active exploitation. Public references include GitLab, HackerOne, CVE Program, and CVE List records, but no source in the bundle supports saying this is being actively exploited.

Researcher notes

The key condition is role-based access: a Developer could access variables intended only for Maintainers because of tag and branch name confusion. The bundle does not include exploit mechanics, affected configurations beyond protected CI variables, or detailed detection guidance.

Mitigation direction

  • Upgrade GitLab CE/EE beyond the affected version ranges.
  • Use at least 13.12.9, 14.0.7, 14.1.2, or later where applicable.
  • Review projects using protected CI variables.
  • Rotate protected secrets if Developer exposure cannot be ruled out.
  • Restrict Developer access on sensitive projects.
  • Check current GitLab vendor guidance before remediation closure.

Validation and detection

  • Inventory GitLab CE/EE versions across all instances.
  • Compare versions against 13.7 to below 13.12.9, 14.0.7, and 14.1.2.
  • Identify projects with protected CI variables.
  • Review Developer membership on those projects.
  • Check audit and CI activity around protected variables where available.
  • Confirm remediated instances are outside affected ranges.
Prepared
Confidence
high
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-22252 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
6.5 (3.1)
Known Exploited
No
Published

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

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
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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