dbcve.org
GitLabApplication

CVE-2023-2182

HIGH · 8.8 CVSS v3.1 Published 2023-05-03
Fix available
A fix is available. Upgrade to 15.10.5 or later.
See remediation →
94/100
Remediation priority · Urgent
Public exploit Remotely reachable 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 EE affecting all versions starting from 15.10 before 15.10.5, all versions starting from 15.11 before 15.11.1. Under certain conditions when OpenID Connect is enabled on an instance, it may allow users who are marked as 'external' to become 'regular' users thus leading to privilege escalation for those 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

A detailed technical summary for this CVE is being prepared.

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:>= 15.10.0, < 15.10.5= 15.11.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 15.10.5 or later
Fixed in 15.10.5
Recommended fix High confidence

15.10.5+ or 15.11.1+ (depending on your current branch)

  1. 1. Identify the currently installed GitLab version by checking /opt/gitlab/version or running `gitlab-rake gitlab:env:info`
  2. 2. If running GitLab 15.10.x (versions 15.10.0 through 15.10.4), plan an upgrade to version 15.10.5 or later
  3. 3. If running GitLab 15.11.0, plan an upgrade to version 15.11.1 or later
  4. 4. Before upgrading, review the GitLab upgrade documentation for your deployment method (omnibus, source, etc.)
  5. 5. Create a full backup of your GitLab instance using `gitlab-rake gitlab:backup:create`
  6. 6. Perform the upgrade following your installation method's upgrade procedure
  7. 7. After upgrade, verify that external users cannot escalate privileges to regular users, especially when OpenID Connect is configured
  8. 8. Review user accounts that were created or modified during the vulnerable period to ensure no unauthorized privilege escalation occurred
Caveat Review GitLab 15.10.5 and 15.11.1 release notes for any other changes that may affect your instance; minor version upgrades typically have low risk but always test in staging first

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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