Unauthorized namespace changes via unchecked Jira permissions
Published Oct 5, 2021 · Updated Aug 3, 2024
Missing authorization in GitLab allows remote authenticated users to add or remove Jira Connect namespaces through the Jira Cloud app. The Jira Connect configuration page trusted a JWT issued to any Jira user without checking the user's Jira administrative permissions. The flaw requires Jira Cloud integration and a basic Jira account, and it permits unauthorized linking or unlinking of GitLab groups.
Summary
What happened
Missing authorization in GitLab allows remote authenticated users to add or remove Jira Connect namespaces through the Jira Cloud app. The Jira Connect configuration page trusted a JWT issued to any Jira user without checking the user's Jira administrative permissions. The flaw requires Jira Cloud integration and a basic Jira account, and it permits unauthorized linking or unlinking of GitLab groups.
The record
- CVE
- CVE-2021-22262
- Published
- Oct 5, 2021
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-863, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 5, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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.12, <14.0.9
- Affected versionversion=>=14.1, <14.1.4
- Affected versionversion=>=14.2, <14.2.2
What conditions does exploitation require?
What is affected?
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
- Jira Connect namespace authorization reproductionfunctional · validated
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