Unauthorized issue creation via unchecked project identifier
Published Oct 17, 2022 · Updated May 13, 2025
Improper access control in GitLab allows remote authenticated users to create issues in projects they cannot access. Boards::IssuesController authorizes the board parent, but accepts a user-controlled project_id that overrides the authorized project passed to the issue service. A signed-in user with access to a board can write issues to private or public projects and learn their paths by enumerating project identifiers.
Summary
What happened
Improper access control in GitLab allows remote authenticated users to create issues in projects they cannot access. Boards::IssuesController authorizes the board parent, but accepts a user-controlled project_id that overrides the authorized project passed to the issue service. A signed-in user with access to a board can write issues to private or public projects and learn their paths by enumerating project identifiers.
The record
- CVE
- CVE-2022-3066
- Published
- Oct 17, 2022
- Updated
- May 13, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-284, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 17, 2022CVE publishedPublication date reported by the CVE source.
- May 13, 2025Record 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=>=10.0, <15.2.5
- Affected versionversion=>=15.3, <15.3.4
- Affected versionversion=>=15.4, <15.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.
Public exploit references
- HackerOne report 1685105 reproductionfunctional · 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