Stored script execution via merge request rendering
Published Mar 13, 2020 · Updated Aug 4, 2024
Stored cross-site scripting in GitLab 12.1 through 12.8.1 allows remote attackers to execute script when a user views a merge request. GitLab identifies merge-request display as the affected locus but has not published the vulnerable field, view, or missing neutralization operation. An attacker must store crafted merge-request content and induce another user to view it; the script then runs in that user's browser context and can read data or perform actions available to that session.
Summary
What happened
Stored cross-site scripting in GitLab 12.1 through 12.8.1 allows remote attackers to execute script when a user views a merge request. GitLab identifies merge-request display as the affected locus but has not published the vulnerable field, view, or missing neutralization operation. An attacker must store crafted merge-request content and induce another user to view it; the script then runs in that user's browser context and can read data or perform actions available to that session.
The record
- CVE
- CVE-2020-10076
- Published
- Mar 13, 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 13, 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