Security readout for executives and security teams
Plain-English summary
This GitLab EE flaw could let a merge request keep code owner approval after its target branch changed. That weakens an important review gate and may let sensitive code changes be merged without the intended renewed owner approval.
Executive priority
Treat this as a high-priority governance and integrity risk for GitLab EE environments. It can undermine review controls used to protect source code, but current sources do not establish active exploitation.
Technical view
CVE-2023-4379 is an incorrect authorization issue in GitLab EE. Affected versions did not remove code owner approval from merge requests when the target branch was updated. The CVSS vector requires high privileges and user interaction, but scope changes with high confidentiality and integrity impact.
Likely exposure
Exposure is limited to GitLab EE versions 15.3 through affected 16.2, 16.3, and 16.4 releases, especially organizations relying on code owner approvals for protected branches or regulated change control.
Exploitation context
The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Abuse would depend on merge request permissions, user interaction, and workflows where target branch changes should invalidate code owner approval.
Researcher notes
The available evidence identifies CWE-863 and the approval-state failure, but provides limited operational detail. Avoid assuming broader GitLab editions, exploit availability, or compensating controls beyond the cited affected ranges and vendor issue.
Mitigation direction
- Upgrade affected GitLab EE instances to 16.2.8, 16.3.5, 16.4.1, or later.
- Check GitLab vendor guidance and issue tracking for current remediation details.
- Review open merge requests where target branches changed during affected-version operation.
- Require renewed code owner review for suspicious or high-impact merge requests.
- Confirm branch protection and code owner approval policies are still enforced.
Validation and detection
- Inventory GitLab EE versions and compare them to the affected ranges.
- Test whether target branch changes invalidate code owner approval after remediation.
- Review recent merges involving target branch changes and sensitive repositories.
- Check audit records for merges that bypassed expected code owner reapproval.
- Confirm vulnerable versions are no longer running in production or staging.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCVE-2023-4379 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 8.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N1.75.8GitLabVulnerability scoring details
Base CVSS 3.1 score
8.1HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #415496CVE reference, GitLab · issue-tracking
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Incorrect Authorization
Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.