Stored XSS via unencoded Git ref names
Published Jan 30, 2020 · Updated Aug 6, 2024
Stored XSS in ViewGit before 0.0.7 allows remote authenticated users to run script in viewers' browsers via crafted Git ref names. The Shortlog and Heads templates insert attacker-controlled branch and tag names into HTML without encoding them, so a viewer's browser interprets the names as active content. The attacker needs permission to create a branch or tag in a displayed repository, and exploitation requires another user to open its summary or shortlog page.
Summary
What happened
Stored XSS in ViewGit before 0.0.7 allows remote authenticated users to run script in viewers' browsers via crafted Git ref names. The Shortlog and Heads templates insert attacker-controlled branch and tag names into HTML without encoding them, so a viewer's browser interprets the names as active content. The attacker needs permission to create a branch or tag in a displayed repository, and exploitation requires another user to open its summary or shortlog page.
The record
- CVE
- CVE-2013-2294
- Published
- Jan 30, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 30, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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
- ViewGit 0.0.6 Multiple Cross-Site Scripting Vulnerabilitiesproof of concept · demonstrated
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