GitLabApplication
CVE-2023-3915
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 · uneditedAn issue has been discovered in GitLab EE affecting all versions starting from 16.1 before 16.1.5, all versions starting from 16.2 before 16.2.5, all versions starting from 16.3 before 16.3.1. If an external user is given an owner role on any group, that external user may escalate their privileges on the instance by creating a service account in that group. This service account is not classified as external and may be used to access internal projects.
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 confidenceIn GitLab EE, an external user granted owner role on any group can create a service account within that group. The created service account is incorrectly classified as internal rather than external, allowing it to bypass external user restrictions and access internal projects that should be inaccessible to external users.
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
>= 16.1.0, < 16.1.5>= 16.2, < 16.2.5= 16.3.0CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed GitLab versionRun `sudo gitlab-rake gitlab:env:info` or check the GitLab admin area under Help > Version to see the exact version numberAffected if The version falls within 16.1.0 to 16.1.4, 16.2.0 to 16.2.4, or exactly 16.3.0
-
Identify external users with owner role on any groupIn GitLab admin area, navigate to Groups > select each group > Members. Look for users with Owner role where the user type is marked as ExternalAffected if Any external user holds the Owner role on one or more groups
-
Audit service accounts in groups with external ownersUsing GitLab Rails console: `Group.with_owner_role.where(id: GroupMember.with_user_type(:external).select(:group_id)).find_each { |g| puts "Group: #{g.name}, Path: #{g.full_path}" }`. Then review each group's service accounts under Group Settings > CI/CD > RunnersAffected if Service accounts exist in groups where an external user has owner role
-
Verify service account user type classificationIn GitLab Rails console, query service account users: `User.where(user_type: :service_account).each { |u| puts "#{u.username}: external = #{u.external?}, created_at = #{u.created_at}" }`. Check if any service accounts show `external = false` (incorrectly marked internal)Affected if Service accounts in affected groups are classified as internal (external: false) when they should be external based on the group owner's status
You are affected if your GitLab version is 16.1.0-16.1.4, 16.2.0-16.2.4, or 16.3.0 AND any external user holds owner role on a group that contains service accounts classified as internal.
Generated from the published advisory. Verify against your own configuration.
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 · scoped16.1.516.2.5
Upgrade GitLab EE to version 16.1.5, 16.2.5, 16.3.1 or later. Until upgraded, audit groups where external users hold owner role and monitor for unauthorized service account creation.
GitLab 16.1.5, 16.2.5, or 16.3.1 (or later stable releases)
- 1. Identify the currently installed GitLab version using `gitlab-rake gitlab:env:info` or the GitLab admin dashboard.
- 2. For versions 16.1.0-16.1.4: Plan upgrade to GitLab 16.1.5 or later (preferably 16.2.5+ or 16.3.1+).
- 3. For versions 16.2.0-16.2.4: Plan upgrade to GitLab 16.2.5 or later (preferably 16.3.1+).
- 4. For version 16.3.0: Plan upgrade to GitLab 16.3.1 or later.
- 5. Before upgrading, backup the GitLab database and repository storage as per GitLab backup documentation.
- 6. Follow the official GitLab upgrade documentation for your installation method (Omnibus, source, or Helm chart).
- 7. After upgrade, verify the version with `gitlab-rake gitlab:env:info`.
- 8. Review user roles and service accounts in groups where external users have owner roles to ensure no unauthorized service accounts were created during the vulnerable period.
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
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2023-3915 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-3915 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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