Auth bypass in Gitlab
CVE-2023-4317
An issue has been discovered in GitLab affecting all versions starting from 9.2 before 16.4.3, all versions starting from 16.5 before 16.5.3, all versions starting from 16.6 before 16.6.1. It was possible for a user with the Developer role to update a pipeline schedule from an unprotected branch to a protected branch.
Vulnerability class: Broken Access Control
EPSS: 0.004 (34.9th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 4.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N.
Affected products
- Gitlab — versions 16.6.0, 9.2, 16.5
Weakness classification (CWE)
Public proof-of-concept exploits
References
- cve@gitlab.com (issue-tracking, permissions-required, Broken Link, Vendor Advisory)
- cve@gitlab.com (Permissions Required, technical-description, permissions-required, Third Party Advisory, exploit)
Frequently asked questions
- What is CVE-2023-4317?
- CVE-2023-4317 is a medium-severity vulnerability in Gitlab, classified under Incorrect Authorization. CVSS score: 4.3/10. Published 2023-12-01.
- How severe is CVE-2023-4317?
- Medium severity. CVSS v3 base score is 4.3 out of 10.
- Is CVE-2023-4317 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.