Stored XSS via unsanitized job error messages
Published Aug 5, 2022 · Updated Aug 3, 2024
Stored XSS in GitLab before 15.0.5, 15.1 through 15.1.3, and 15.2.0 allows remote authenticated users to act as a viewing user. GitLab renders attacker-controlled job error messages without adequately neutralizing executable HTML, so a stored payload runs in the victim's browser. Exploitation requires low-privileged project access and a victim to view the crafted error; the payload can read data or perform actions with that victim's session.
Summary
What happened
Stored XSS in GitLab before 15.0.5, 15.1 through 15.1.3, and 15.2.0 allows remote authenticated users to act as a viewing user. GitLab renders attacker-controlled job error messages without adequately neutralizing executable HTML, so a stored payload runs in the victim's browser. Exploitation requires low-privileged project access and a victim to view the crafted error; the payload can read data or perform actions with that victim's session.
The record
- CVE
- CVE-2022-2500
- Published
- Aug 5, 2022
- Updated
- Aug 3, 2024
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 5, 2022CVE 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=>=0.0, <15.0.5
- Affected versionversion=>=15.1, <15.1.4
- Affected versionversion=>=15.2, <15.2.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
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