Protected-branch modification via ambiguous Git ref resolution
Published Jul 13, 2023 · Updated Oct 30, 2024
Incorrect authorization in GitLab 13.7 through 15.11.9, 16.0 through 16.0.5, and 16.1.0 allows developers to bypass CODEOWNERS. A tag sharing the protected branch's name takes precedence during ambiguous Git ref resolution, so the approval check reads the tag instead of the branch. Developer access plus a non-default protected branch with required Code Owner approval is enough to merge unapproved changes without maintainer interaction.
Summary
What happened
Incorrect authorization in GitLab 13.7 through 15.11.9, 16.0 through 16.0.5, and 16.1.0 allows developers to bypass CODEOWNERS. A tag sharing the protected branch's name takes precedence during ambiguous Git ref resolution, so the approval check reads the tag instead of the branch. Developer access plus a non-default protected branch with required Code Owner approval is enough to merge unapproved changes without maintainer interaction.
The record
- CVE
- CVE-2023-2576
- Published
- Jul 13, 2023
- Updated
- Oct 30, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863, T1565.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 13, 2023CVE publishedPublication date reported by the CVE source.
- Oct 30, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13.7 <15.11.10
- Affected versionversion=16.0 <16.0.6
- Affected versionversion=16.1 <16.1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- Same-named tag CODEOWNERS bypass reproductionproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo