Security readout for executives and security teams
Plain-English summary
A removed GitLab project member could still modify protected branches if they used deploy keys. This is an authorization failure affecting integrity rather than confidentiality or availability. Business impact is unauthorized code changes to protected branches, especially where deploy keys are widely used.
Executive priority
Treat as a targeted integrity risk, not a broad outage risk. Prioritize GitLab systems that host sensitive production code, regulated workflows, or release branches protected by policy.
Technical view
CVE-2023-5198 is CWE-863 incorrect authorization in GitLab. Affected versions are before 16.2.7, 16.3 before 16.3.5, and 16.4 before 16.4.1. The CVSS 3.1 score is 4.3: network reachable, low complexity, low privileges, no user interaction, with low integrity impact.
Likely exposure
Self-managed GitLab instances in the affected version ranges are the likely concern. Exposure depends on projects using protected branches, deploy keys, and removed members with prior project access.
Exploitation context
The provided bundle does not show CISA KEV listing or active exploitation evidence. Public references include GitLab and HackerOne records, but the bundle marks them as permission-required and provides no confirmed exploitation-in-the-wild detail.
Researcher notes
The available evidence supports an authorization bypass involving removed members and deploy keys. Details beyond the CVE description are limited because cited GitLab and HackerOne references are marked permission-required in the bundle.
Mitigation direction
- Upgrade GitLab to 16.2.7, 16.3.5, 16.4.1, or a later supported release.
- Review GitLab vendor guidance for any additional remediation notes.
- Audit deploy keys on protected-branch projects.
- Disable or rotate deploy keys no longer tied to active authorized users.
- Review protected branch permissions for least privilege.
Validation and detection
- Inventory all GitLab instances and record exact versions.
- Identify projects using protected branches and deploy keys.
- Check whether removed members had deploy-key-related write paths.
- Review protected branch change history for unexpected writes.
- Confirm post-upgrade authorization behavior matches current policy.
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-5198 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
- Medium
- CVSS
- 4.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/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:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4GitLabVulnerability scoring details
Base CVSS 3.1 score
4.3MediumVector: CVSS:3.1/AV:N/AC:L/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 #416957CVE reference, GitLab · issue-tracking, permissions-required
- HackerOne Bug Bounty Report #2041789CVE 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.