LiveActive security incident?Get immediate response
CVE Record

CVE-2021-22219: All versions of GitLab CE/EE starting from 9.5 before 13.10.5, all versions starting from 13.11 before 13.1...

All versions of GitLab CE/EE starting from 9.5 before 13.10.5, all versions starting from 13.11 before 13.11.5, and all versions starting from 13.12 before 13.12.2 allow a high privilege user to obtain sensitive information from log files because the sensitive information was not correctly registered for log masking.

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

Security readout for executives and security teams

Plain-English summary

This GitLab issue could expose secrets or other sensitive data in logs because some values were not properly masked. It requires a high-privilege user, so the main business risk is insider misuse, compromised administrator accounts, or over-broad log access rather than broad unauthenticated attack.

Executive priority

Treat as a moderate-priority remediation. It is not a broad remote compromise issue, but it can expose secrets if privileged accounts or log access are misused.

Technical view

GitLab CE/EE versions 9.5 through before 13.10.5, 13.11 before 13.11.5, and 13.12 before 13.12.2 are affected. The flaw is improper registration for log masking, allowing a high-privilege user to obtain sensitive information from log files. CVSS 3.1 is 4.4 with high confidentiality impact.

Likely exposure

Exposure is likely limited to self-managed GitLab CE/EE instances in the listed version ranges, especially where administrators, maintainers, support staff, or centralized logging users can read application logs.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires high privileges and high complexity, but compromised privileged accounts could use log access to recover sensitive information.

Researcher notes

No CWE is listed in the bundle. Validation should focus on affected version confirmation, log access paths, secret exposure risk, and post-upgrade verification. Avoid assuming exploit availability; the provided sources only describe the masking failure and affected ranges.

Mitigation direction

  • Upgrade affected GitLab instances to 13.10.5, 13.11.5, 13.12.2, or later supported versions.
  • Review GitLab vendor guidance for any additional log-handling or secret-rotation recommendations.
  • Restrict access to GitLab application logs and centralized log platforms.
  • Rotate exposed credentials if logs may have contained secrets during the affected period.

Validation and detection

  • Inventory GitLab CE/EE versions across self-managed environments.
  • Confirm no instance remains in the affected version ranges.
  • Review who can access GitLab logs and centralized log stores.
  • Assess logs from affected periods for possible sensitive values, following internal handling procedures.
Prepared
Confidence
medium
Sources
4

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-22219 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.4 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:H/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
3Source 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.4CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N0.73.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:H/PR:H/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>=9.5, <13.10.5, >=13.11, <13.11.5, >=13.12, <13.12.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.