Security readout for executives and security teams
Plain-English summary
This GitLab flaw could let a user with developer-level access change predefined CI variables through the REST API in some situations. That can affect pipeline integrity, especially where CI/CD variables influence deployments, security checks, or release behavior. The CVE rates it medium because it requires authenticated low-privilege access and impacts integrity, not confidentiality or availability.
Executive priority
Handle as a moderate-priority GitLab patch and access-review item. Prioritize environments where CI/CD deploys production systems or where Developer access is broadly granted. The business risk is unauthorized pipeline behavior, not direct data theft based on the provided CVSS and description.
Technical view
CVE-2023-5061 is a CWE-862 missing authorization issue in GitLab. Affected ranges are 9.3 through before 16.4.4, 16.5 before 16.5.4, and 16.6 before 16.6.2. The reported behavior allowed developers to override predefined CI variables via REST API under certain conditions. CVSS 3.1 is 4.3, AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N.
Likely exposure
Exposure is likely for self-managed GitLab instances running the affected versions, especially projects where many users have Developer role and CI/CD variables control build, deployment, or release decisions. GitLab.com exposure is not stated in the source bundle, so it should not be assumed.
Exploitation context
The source bundle does not show CISA KEV listing or active exploitation evidence. It references GitLab and HackerOne reports, but both are marked permissions-required. Treat this as a plausible authenticated misuse risk, not as confirmed internet-wide exploitation.
Researcher notes
Evidence is limited to the CVE description, CVSS vector, affected version ranges, and permission-gated GitLab/HackerOne references. The key security question is whether a Developer can alter predefined CI variable behavior through REST API paths that should enforce stronger authorization.
Mitigation direction
- Upgrade affected GitLab instances to 16.4.4, 16.5.4, 16.6.2, or later supported releases.
- Check GitLab vendor guidance for any backports, configuration notes, or additional remediation.
- Restrict Developer role membership to users who need CI/CD modification ability.
- Review CI/CD variables and pipeline permissions for sensitive deployment paths.
- Rotate secrets if pipeline behavior or protected variables may have been exposed to misuse.
Validation and detection
- Inventory all GitLab instances and compare versions against the affected ranges.
- Confirm upgraded instances report a fixed or later supported version.
- Review projects with broad Developer role assignment and CI/CD deployment privileges.
- Audit recent REST API and pipeline activity for unexpected CI variable overrides.
- Verify production deployment pipelines do not rely on unreviewed developer-controlled variables.
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-862: 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-5061 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.
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.4Primary CVE scoreVulnerability 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
Source materials
- CVE List V5 sourceCVE List V5
- GitLab Issue #425521CVE reference · issue-tracking, permissions-required
- HackerOne Bug Bounty Report #2125189CVE reference · 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.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.