GitLabApplication
CVE-2023-3484
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 12.8 before 15.11.11, all versions starting from 16.0 before 16.0.7, all versions starting from 16.1 before 16.1.2. An attacker could change the name or path of a public top-level group in certain situations.
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 confidenceAn authorization bypass in GitLab EE allows authenticated attackers to modify the name or path of public top-level groups in certain situations, potentially enabling group hijacking or confusion attacks.
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
>= 12.8.0, < 15.11.11>= 16.0.0, < 16.0.7>= 16.1.0, < 16.1.2CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify GitLab versionAccess the GitLab administration panel or run 'gitlab-rake gitlab:env:info' to retrieve the installed GitLab versionAffected if The version is 12.8.0 or higher but below 15.11.11, OR 16.0.0 or higher but below 16.0.7, OR 16.1.0 or higher but below 16.1.2
-
Confirm public group existenceNavigate to the Groups section in GitLab and filter for groups with Public visibility, focusing on top-level groups that have no parent groupAffected if There are public top-level groups present in the GitLab instance
-
Verify group modification permissionsReview the permission settings for authenticated users on public groups, specifically checking if any user role has the ability to modify group name or pathAffected if Authenticated users have permissions to edit group name or path on public groups
-
Check audit logs for group modificationsReview GitLab audit logs for any recent changes to public group names or paths that were performed by users without explicit group owner privilegesAffected if Unusual or unauthorized modifications to public group names or paths are observed in the audit logs
You are affected if your GitLab version is within the affected ranges AND you have public top-level groups where authenticated users can modify group settings.
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 · scoped15.11.1116.0.716.1.2
Upgrade GitLab to versions 15.11.11, 16.0.7, 16.1.2 or later. If immediate upgrade is not possible, restrict group modification permissions pending the patch.
GitLab 15.11.11+ (for 12.8.0-15.11.x), 16.0.7+ (for 16.0.x), or 16.1.2+ (for 16.1.x)
- Identify the currently installed GitLab version by running `gitlab-rake gitlab:env:info` or checking /admin/about
- Determine which version branch your current installation falls into: 12.8.0-15.11.x, 16.0.x, or 16.1.x
- For versions 12.8.0 through 15.11.x: upgrade to GitLab 15.11.11 or later (recommended: latest 15.11.x)
- For versions 16.0.x: upgrade to GitLab 16.0.7 or later (recommended: latest 16.0.x)
- For versions 16.1.x: upgrade to GitLab 16.1.2 or later (recommended: latest 16.1.x)
- After upgrade, verify the version with `gitlab-rake gitlab:env:info` and test group rename functionality
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-3484 — 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-3484 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