LiveActive security incident?Get immediate response
CVE Record

CVE-2023-6477: Incorrect Privilege Assignment in GitLab

An issue has been discovered in GitLab EE affecting all versions starting from 16.5 before 16.7.6, all versions starting from 16.8 before 16.8.3, all versions starting from 16.9 before 16.9.1. When a user is assigned a custom role with admin_group_member permission, they may be able to make a group, other members or themselves Owners of that group, which may lead to privilege escalation.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2023-6477 is a GitLab EE privilege escalation flaw. A user with a custom role containing admin_group_member permission may be able to promote themselves or others to group Owner. This can undermine governance over source code, CI/CD settings, secrets, and group membership.

Executive priority

Prioritize within the normal patch cycle, faster for GitLab groups hosting sensitive code, CI/CD secrets, regulated data, or shared administrative teams. The issue is not unauthenticated, but successful abuse can hand over group ownership.

Technical view

GitLab EE versions 16.5 before 16.7.6, 16.8 before 16.8.3, and 16.9 before 16.9.1 incorrectly assign privileges for custom roles using admin_group_member. The flaw is network reachable, low complexity, requires high privileges, needs no user interaction, and can affect confidentiality, integrity, and availability.

Likely exposure

Exposure is limited to GitLab EE deployments in the affected version ranges that use custom roles with admin_group_member permission. Default unaffected status is noted, and GitLab CE is not named in the supplied sources.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. Abuse requires an authenticated user already assigned a custom role with admin_group_member permission, making this primarily an insider, compromised account, or over-permissioned role risk.

Researcher notes

The key research boundary is privilege context: high privileges and a specific custom role permission are required. Validate role definitions and ownership changes without attempting promotion workflows in production unless explicitly authorized and controlled.

Mitigation direction

  • Upgrade affected GitLab EE instances to 16.7.6, 16.8.3, 16.9.1, or later supported versions.
  • Review custom roles containing admin_group_member and restrict them until patched.
  • Audit recent group Owner assignments for unexpected promotions.
  • Check GitLab vendor guidance for any additional configuration or backport instructions.

Validation and detection

  • Inventory GitLab EE versions against the affected ranges.
  • Identify custom roles that include admin_group_member permission.
  • Review group membership history for unexpected Owner role changes.
  • Confirm patched version deployment in production and externally reachable instances.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-266: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Privilege behavior lookup

The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-6477 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.7 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
2ADP providers
3Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.7CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L1.25.5GitLab

Vulnerability scoring details

Base CVSS 3.1 score

6.7Medium
CVSS 3.1 vector shape for CVE-2023-6477Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GitLabGitLab16.5, 16.8, 16.9unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-266 · source CWE mapping

Incorrect Privilege Assignment

Incorrect Privilege Assignment represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.