LiveActive security incident?Get immediate response
CVE Record

CVE-2023-4812: Incorrect Authorization in GitLab

An issue has been discovered in GitLab EE affecting all versions starting from 15.3 before 16.5.6, all versions starting from 16.6 before 16.6.4, all versions starting from 16.7 before 16.7.2. The required CODEOWNERS approval could be bypassed by adding changes to a previously approved merge request.

HighCVSS 7.6Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This GitLab EE flaw could let someone bypass required CODEOWNERS approval after a merge request was already approved. For organizations relying on CODEOWNERS to protect sensitive code, this creates integrity risk because unreviewed changes could enter protected areas.

Executive priority

Treat this as a high-priority integrity issue for GitLab EE environments that rely on CODEOWNERS as a control. It is not marked as known exploited in the provided sources, but it can undermine a key code governance safeguard.

Technical view

CVE-2023-4812 is an incorrect authorization issue in GitLab EE. A required CODEOWNERS approval could be bypassed by adding changes to a previously approved merge request. The CVSS 3.1 score is 7.6 high, with low attack complexity, low privileges, user interaction required, changed scope, low confidentiality impact, high integrity impact, and no availability impact.

Likely exposure

Exposure is limited by the bundle to GitLab EE versions starting at 15.3 before 16.5.6, 16.6 before 16.6.4, and 16.7 before 16.7.2. Organizations using CODEOWNERS approvals for merge request control have the clearest business exposure.

Exploitation context

The bundle does not show CISA KEV listing or active exploitation evidence. It does reference a HackerOne report tagged as exploit and technical description, but the report is marked permissions-required in the bundle.

Researcher notes

The strongest source detail is the CVE description and CVSS vector. The public bundle does not provide full GitLab issue or HackerOne details because both are marked permissions-required, so exploit mechanics and any workaround specifics should not be assumed.

Mitigation direction

  • Upgrade affected GitLab EE instances to 16.5.6, 16.6.4, 16.7.2, or a later fixed release.
  • Prioritize instances where CODEOWNERS approvals protect sensitive repositories or regulated code paths.
  • Review recent approved merge requests that received additional changes before merge.
  • Check GitLab vendor guidance for any version-specific remediation details.

Validation and detection

  • Inventory GitLab EE versions and compare them against the affected ranges.
  • Confirm CODEOWNERS approval rules are used on high-value projects.
  • Review merge request history for approvals followed by later code changes.
  • Validate upgraded instances report a fixed GitLab EE version.
Prepared
Confidence
medium
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 · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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
cve · low confidence lookup

CVE-2023-4812 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
High
CVSS
7.6 (3.1)
Known Exploited
No
Published

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

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
0Timeline events
0ADP providers
3Source links

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
7.6CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:H/A:N2.34.7Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.6High
CVSS 3.1 vector shape for CVE-2023-4812Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GitLabGitLab15.3, 16.6, 16.7unaffected
Weakness

CWE details

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

CWE-863 · source CWE mapping

CWE mapping pending import

This CVE carries a CWE mapping that will resolve to a full Glexia CWE intelligence page after the official CWE import is complete.