CVE-2023-4317: Improper Access Control in GitLab
First published: Fri Dec 01 2023(Updated: )
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.
Credit: cve@gitlab.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Gitlab Gitlab | >=9.2.0<16.4.3 | |
| Gitlab Gitlab | >=9.2.0<16.4.3 | |
| Gitlab Gitlab | >=16.5.0<16.5.3 | |
| Gitlab Gitlab | >=16.5.0<16.5.3 | |
| Gitlab Gitlab | =16.6.0 | |
| Gitlab Gitlab | =16.6.0 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2023-4317?
CVE-2023-4317 is a vulnerability in GitLab that allows users with the Developer role to update a pipeline schedule from an unprotected branch.
How does the vulnerability in GitLab affect the software?
The vulnerability affects all versions of GitLab starting from 9.2 before 16.4.3, all versions starting from 16.5 before 16.5.3, and version 16.6.0.
What is the severity of CVE-2023-4317?
The vulnerability has a severity rating of 4.3 (Medium).
Where can I find more information about CVE-2023-4317?
You can find more information about CVE-2023-4317 in the GitLab issue tracker and a HackerOne report.
How can I fix the vulnerability in GitLab?
To fix the vulnerability, you should update GitLab to version 16.4.3, 16.5.3, or 16.6.1 or later.
- collector/mitre-cve
- collector/nvd-api
- vendor/gitlab
- canonical/gitlab gitlab
- version/gitlab gitlab/9.2.0
- version/gitlab gitlab/16.5.0
- version/gitlab gitlab/16.6.0