Protected-branch approval bypass via unverified email mapping
Published Nov 4, 2021 · Updated Aug 4, 2024
Authorization bypass in GitLab EE 11.3 through 14.2.5, 14.3 through 14.3.3, and 14.4.0 lets remote authenticated users merge code. The CODEOWNERS resolver maps email entries against all account addresses instead of limiting matches to verified addresses. Exploitation requires project membership, an unclaimed email in a CODEOWNERS rule, and protected-branch owner approval, and grants unauthorized merge and push access.
Summary
What happened
Authorization bypass in GitLab EE 11.3 through 14.2.5, 14.3 through 14.3.3, and 14.4.0 lets remote authenticated users merge code. The CODEOWNERS resolver maps email entries against all account addresses instead of limiting matches to verified addresses. Exploitation requires project membership, an unclaimed email in a CODEOWNERS rule, and protected-branch owner approval, and grants unauthorized merge and push access.
The record
- CVE
- CVE-2021-39909
- Published
- Nov 4, 2021
- Updated
- Aug 4, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-347, CAPEC-233, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 4, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=>=11.3, <14.2.6
- Affected versionversion=>=14.3, <14.3.4
- Affected versionversion=>=14.4, <14.4.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.
Weakness, pattern, technique
Public exploit references
- HackerOne report 1237750 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