dbcve.org
GitLabApplication

CVE-2022-1413

HIGH · 7.5 CVSS v3.1 Published 2022-05-19
Fix available
A fix is available. Upgrade to 14.8.6 / 14.9.4 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
Missing input masking in GitLab CE/EE affecting all versions starting from 1.0.2 before 14.8.6, all versions from 14.9.0 before 14.9.4, and all versions from 14.10.0 before 14.10.1 causes potentially sensitive integration properties to be disclosed in the web interface

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 · high confidence

Missing input masking in GitLab CE/EE causes sensitive integration properties (such as API tokens, passwords, or secrets configured for integrations like webhooks, CI/CD, or third-party services) to be displayed in plain text within the web interface rather than being masked, allowing users with interface access to view these credentials.

MitigationUpgrade GitLab to version 14.8.6, 14.9.4, 14.10.1 or later. Audit user access to integration settings and rotate any credentials that may have been exposed.

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:>= 1.0.2, < 14.8.6>= 14.9.0, < 14.9.4= 14.10.0

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 `sudo gitlab-rake gitlab:env:info` or check `/opt/gitlab/version` to retrieve the installed GitLab version number
    Affected if The version falls within >= 1.0.2 and < 14.8.6, OR >= 14.9.0 and < 14.9.4, OR equals 14.10.0
  2. Access integration settings in the web interface
    Navigate to any project or group settings, then go to Settings > Integrations (or Settings > CI/CD for pipeline settings)
    Affected if You have access to integration configuration pages in the UI
  3. Verify if credentials are masked
    View an integration that requires credentials (such as a webhook, Slack integration, or CI/CD variables) and check whether the password/token fields show masked dots (•) or display the actual plain-text value
    Affected if Credentials in any integration settings field appear as plain text instead of being masked with dots or asterisks

You are affected if your GitLab version is in the vulnerable range and integration credentials display in plain text rather than being masked in the web interface.

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.

dbcve · scoped
Upgrade available Upgrade to 14.8.6 / 14.9.4 or later
Fixed in 14.8.614.9.4
Interim mitigation

Upgrade GitLab to version 14.8.6, 14.9.4, 14.10.1 or later. Audit user access to integration settings and rotate any credentials that may have been exposed.

Recommended fix High confidence

Upgrade to GitLab 14.8.6, 14.9.4, 14.10.1, or later stable release (14.x LTS recommended)

  1. 1. Back up your GitLab instance data and configuration
  2. 2. Plan maintenance window as upgrade may require downtime
  3. 3. For GitLab installations usingOmnibus: run 'gitlab-ctl upgrade' or download and install the appropriate package for your OS from gitlab.com
  4. 4. For installations from source: follow the upgrade documentation for your version
  5. 5. After upgrade, verify that sensitive integration fields (passwords, tokens, API keys) are now masked in the web interface
  6. 6. Test that integrations still function correctly after the upgrade
Caveat Review GitLab upgrade notes for potential breaking changes between your current version and target version; some migrations may require additional steps

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1413 — 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-2022-1413 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