Stored XSS via unescaped wiki commit author
Published Mar 24, 2021 · Updated Aug 3, 2024
Stored XSS in GitLab 13.8 through 13.8.4 and 13.9 through 13.9.1 allows remote authenticated users to run script via a wiki commit. The wiki page renderer interpolates the commit author name into a strong element and marks the assembled string HTML-safe without escaping the author-controlled value. A project member must create the crafted wiki commit, and another user must view the affected wiki content; script runs in that viewer's GitLab session.
Summary
What happened
Stored XSS in GitLab 13.8 through 13.8.4 and 13.9 through 13.9.1 allows remote authenticated users to run script via a wiki commit. The wiki page renderer interpolates the commit author name into a strong element and marks the assembled string HTML-safe without escaping the author-controlled value. A project member must create the crafted wiki commit, and another user must view the affected wiki content; script runs in that viewer's GitLab session.
The record
- CVE
- CVE-2021-22185
- Published
- Mar 24, 2021
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 24, 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.8, <13.8.5
- Affected versionversion=>=13.9, <13.9.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
No public exploit references are available in this record.
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