Stored XSS via unsanitized issue-details JSON
Published Apr 15, 2023 · Updated Feb 6, 2025
Stored XSS in GitLab CE and EE before 11.1.7, 11.2.0 through 11.2.3, and 11.3.0 allows remote authenticated users to run script. The issue details view embeds inadequately sanitized JSON data, allowing stored attacker-controlled content to execute in a visitor's browser. A low-privileged account must store the payload and another user must open the affected issue details screen; execution is limited to that user's web session.
Summary
What happened
Stored XSS in GitLab CE and EE before 11.1.7, 11.2.0 through 11.2.3, and 11.3.0 allows remote authenticated users to run script. The issue details view embeds inadequately sanitized JSON data, allowing stored attacker-controlled content to execute in a visitor's browser. A low-privileged account must store the payload and another user must open the affected issue details screen; execution is limited to that user's web session.
The record
- CVE
- CVE-2018-17454
- Published
- Apr 15, 2023
- Updated
- Feb 6, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 15, 2023CVE publishedPublication date reported by the CVE source.
- Feb 6, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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