dbcve.org
GitLabApplication

CVE-2021-22184

MEDIUM · 5.5 CVSS v3.1 Published 2021-03-26
Fix available
A fix is available. Upgrade to 13.6.6 / 13.7.6 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An information disclosure issue in GitLab starting from version 12.8 allowed a user with access to the server logs to see sensitive information that wasn't properly redacted.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

GitLab versions 12.8 and later contain an information disclosure vulnerability where sensitive information in server logs was not properly redacted, allowing users with server log access to view potentially sensitive data.

MitigationUpgrade GitLab to the patched version. Restrict access to server logs pending the upgrade.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
GitLabApplication
Affected:>= 12.8.0, < 13.6.6>= 13.7.0, < 13.7.6>= 13.8.0, < 13.8.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed GitLab version
    Run command: gitlab-rake gitlab:env:info or check /opt/gitlab/version
    Affected if Version falls within >= 12.8.0, < 13.6.6 OR >= 13.7.0, < 13.7.6 OR >= 13.8.0, < 13.8.2
  2. Confirm server log access exists
    Verify user has read access to /var/log/gitlab/ or uses the GitLab admin area Logs section
    Affected if Users or administrators can access GitLab server log files or the Logs admin interface
  3. Inspect log files for unredacted sensitive data
    Search recent log entries in /var/log/gitlab/ for patterns such as raw API tokens, password parameters, or authorization headers that appear unreplaced
    Affected if Log entries contain visible sensitive strings like 'PRIVATE-TOKEN', 'password', or 'secret' that should have been redacted but are not masked

User is affected if running a GitLab version in the listed ranges AND has users or processes with access to server logs where sensitive data may be exposed unreplaced.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 13.6.6 / 13.7.6 / 13.8.2 or later
Fixed in 13.6.613.7.613.8.2
Interim mitigation

Upgrade GitLab to the patched version. Restrict access to server logs pending the upgrade.

Fix this in GitLab Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-22184 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-22184 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data