dbcve.org
GitLabApplication

CVE-2022-1963

MEDIUM · 5.3 CVSS v3.1 Published 2022-07-01
Fix available
A fix is available. Upgrade to 14.10.5 / 15.0.4 or later.
See remediation →
62/100
Remediation priority · Elevated
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
An issue has been discovered in GitLab CE/EE affecting all versions starting from 13.4 before 14.10.5, all versions starting from 15.0 before 15.0.4, all versions starting from 15.1 before 15.1.1. GitLab reveals if a user has enabled two-factor authentication on their account in the HTML source, to unauthenticated users.

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

GitLab CE/EE exposes whether a user has enabled two-factor authentication in the HTML source to unauthenticated (non-logged-in) visitors. This information disclosure occurs through the user interface or API responses that include 2FA status in page HTML, allowing attackers to enumerate which accounts have enhanced security.

MitigationUpgrade GitLab to versions 14.10.5, 15.0.4, 15.1.1 or later. Self-hosted deployments should apply the patch version corresponding to their current major release.

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:>= 13.4.0, < 14.10.5>= 15.0.0, < 15.0.4= 15.1.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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Check GitLab version
    Run command: sudo gitlab-rake gitlab:env:info or check in Admin Area > Dashboard under Version
    Affected if Version is >= 13.4.0 and < 14.10.5, OR >= 15.0.0 and < 15.0.4, OR exactly 15.1.0
  2. Verify 2FA status visibility in unauthenticated HTML
    Open a private/incognito browser window, navigate to any user profile page (e.g., https://your-gitlab-instance/username), then view page source (right-click > View Page Source) and search for terms like 'two_factor', '2fa', 'two-factor', or 'otp'
    Affected if HTML source reveals any 2FA-related fields, status indicators, or security settings for the user without being logged in
  3. Check API endpoint for 2FA information leak
    Use a tool like curl to send an unauthenticated GET request to the users API endpoint: curl https://your-gitlab-instance/api/v4/users/[user_id] and examine the JSON response for 2FA-related fields
    Affected if API response includes two_factor_enabled, otp_enabled, or similar fields to unauthenticated callers

Environment is affected if GitLab version falls within the vulnerable ranges AND 2FA status is exposed in unauthenticated HTTP responses or HTML source.

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.10.5 / 15.0.4 or later
Fixed in 14.10.515.0.4
Interim mitigation

Upgrade GitLab to versions 14.10.5, 15.0.4, 15.1.1 or later. Self-hosted deployments should apply the patch version corresponding to their current major release.

Recommended fix High confidence

14.10.5+, 15.0.4+, or 15.1.1+ depending on your branch

  1. Identify your current GitLab version by checking the GitLab admin area or running `gitlab-rake gitlab:env:info`
  2. Determine which version branch you are on (14.x, 15.0.x, or 15.1.x)
  3. For GitLab 14.x (versions 13.4.0 to 14.10.4): Upgrade to version 14.10.5 or later
  4. For GitLab 15.0.x (versions 15.0.0 to 15.0.3): Upgrade to version 15.0.4 or later
  5. For GitLab 15.1.0: Upgrade to version 15.1.1 or later
  6. After upgrade, verify the fix by checking that unauthenticated user HTML responses no longer reveal 2FA status information
  7. Consult GitLab upgrade documentation for your specific installation method (omnibus, source, etc.) for proper upgrade procedures
Caveat Review GitLab release notes for major changes between your current version and target version, especially when crossing major version boundaries (e.g., 14.x to 15.x)

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

Fix this in GitLab Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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