Stored XSS via unsanitized Jira issue key
Published Oct 5, 2021 · Updated Aug 3, 2024
Stored XSS in GitLab 13.9 through 14.0.8, 14.1 through 14.1.3, and 14.2 through 14.2.1 allows remote authenticated users to run JavaScript. GitLab renders the Jira API response key field on Jira issue detail pages without sanitizing attacker-controlled markup. Exploitation requires control of a configured Jira API response and a victim to open the affected issue page, enabling actions in the victim's GitLab browser context.
Summary
What happened
Stored XSS in GitLab 13.9 through 14.0.8, 14.1 through 14.1.3, and 14.2 through 14.2.1 allows remote authenticated users to run JavaScript. GitLab renders the Jira API response key field on Jira issue detail pages without sanitizing attacker-controlled markup. Exploitation requires control of a configured Jira API response and a victim to open the affected issue page, enabling actions in the victim's GitLab browser context.
The record
- CVE
- CVE-2021-22261
- Published
- Oct 5, 2021
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- admin
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.9, <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?
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
- Stored XSS in Jira issue detail pages proof of conceptproof 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