Stored XSS via Asciidoctor file rendering
Published Jan 24, 2025 · Updated Feb 12, 2025
Stored XSS in GitLab CE/EE 17.2 through 17.6.3, 17.7 through 17.7.2, and 17.8.0 allows remote authenticated users to execute script. GitLab identifies the locus as its Asciidoctor renderer but does not disclose which file type or sanitization operation is defective. A low-privileged user must supply a crafted file and another user must render it, enabling script execution in the viewer's browser.
Summary
What happened
Stored XSS in GitLab CE/EE 17.2 through 17.6.3, 17.7 through 17.7.2, and 17.8.0 allows remote authenticated users to execute script. GitLab identifies the locus as its Asciidoctor renderer but does not disclose which file type or sanitization operation is defective. A low-privileged user must supply a crafted file and another user must render it, enabling script execution in the viewer's browser.
The record
- CVE
- CVE-2025-0314
- Published
- Jan 24, 2025
- Updated
- Feb 12, 2025
- Vendor
- GitLab
- Product
- GitLab
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 24, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17.2 <17.6.4
- Affected versionversion=17.7 <17.7.3
- Affected versionversion=17.8 <17.8.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