Persistent XSS via unencoded child-epic content
Published Mar 10, 2020 · Updated Aug 4, 2024
Persistent XSS in GitLab Enterprise Edition 11.7 through 11.11 allows remote attackers to execute script through crafted child epics. The epic details page renders attacker-controlled child-epic content without validating the input or encoding it for HTML output. Exploitation requires persistent content to reach a child epic and a user to view the affected details page, enabling script execution in that user's browser.
Summary
What happened
Persistent XSS in GitLab Enterprise Edition 11.7 through 11.11 allows remote attackers to execute script through crafted child epics. The epic details page renders attacker-controlled child-epic content without validating the input or encoding it for HTML output. Exploitation requires persistent content to reach a child epic and a user to view the affected details page, enabling script execution in that user's browser.
The record
- CVE
- CVE-2019-12442
- Published
- Mar 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
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