Security readout for executives and security teams
Plain-English summary
CVE-2023-3979 is a low-severity GitLab authorization flaw. In specific GitLab versions, an upstream member allowed to collaborate on a merge request could receive write permission to the merge request source branch. The business impact is limited but relevant where branch integrity, code review controls, or protected development workflows matter.
Executive priority
Treat as routine patch management unless your organization relies heavily on strict GitLab branch permissions for sensitive code. Prioritize remediation in regulated, high-trust, or shared-development environments, but this does not appear to warrant emergency response based on provided evidence.
Technical view
GitLab versions from 10.6 before 16.2.8, 16.3 before 16.3.5, and 16.4 before 16.4.1 are affected. The issue is CWE-863 Incorrect Authorization. CVSS is 3.1: network-accessible, high complexity, low privileges required, no user interaction, with low integrity impact only.
Likely exposure
Exposure is limited to GitLab instances running affected versions and using merge request workflows where upstream members collaborate on source branches. Instances on fixed or unaffected versions are not indicated as exposed by the provided sources.
Exploitation context
The sources describe a permission escalation within GitLab merge request collaboration behavior. The CVE is not listed as CISA KEV, and the provided sources do not support claims of active exploitation in the wild.
Researcher notes
The core condition is incorrect authorization around upstream member collaboration on merge request source branches. Public details may require authenticated access to GitLab issue or HackerOne pages. Do not assume broader repository takeover; the described impact is limited to write permission on the merge request source branch.
Mitigation direction
- Upgrade affected GitLab instances to 16.2.8, 16.3.5, 16.4.1, or later applicable releases.
- Review GitLab vendor guidance and release notes for deployment-specific remediation details.
- Limit merge request collaboration permissions where branch write access is sensitive.
- Use protected branches and code review controls for critical repositories.
Validation and detection
- Inventory GitLab versions across self-managed instances.
- Confirm affected versions are upgraded past the fixed version thresholds.
- Review merge request settings for source branch collaboration exposure.
- Check recent branch permission changes on sensitive repositories.
- Verify protected branch rules cover critical development branches.
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-3979 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
- Low
- CVSS
- 3.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/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:H/PR:L/UI:N/S:U/C:N/I:L/A:N1.61.4GitLabVulnerability scoring details
Base CVSS 3.1 score
3.1LowVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/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 #419972CVE reference, GitLab · issue-tracking, permissions-required
- HackerOne Bug Bounty Report #2082560CVE reference, GitLab · technical-description, exploit
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.