CVE-2023-22456 ViewVC XSS vulnerability in revision view changed paths
An attacker with commit privileges can inject malicious scripts via unsafe file names in ViewVC, potentially executing code in victim browsers.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2023-22456?
CVE-2023-22456 is a medium-severity cross-site scripting vulnerability in viewvc, published on 3 Jan 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official description
ViewVC, a browser interface for CVS and Subversion version control repositories, as a cross-site scripting vulnerability that affects versions prior to 1.2.2 and 1.1.29. The impact of this vulnerability is mitigated by the need for an attacker to have commit privileges to a Subversion repository exposed by an otherwise trusted ViewVC instance. The attack vector involves files with unsafe names (names that, when embedded into an HTML stream, would cause the browser to run unwanted code), which themselves can be challenging to create. Users should update to at least version 1.2.2 (if they are using a 1.2.x version of ViewVC) or 1.1.29 (if they are using a 1.1.x version).
ViewVC 1.0.x is no longer supported, so users of that release lineage should implement a workaround. Users can edit their ViewVC EZT view templates to manually HTML-escape changed paths during rendering. Locate in your template set's `revision.ezt` file references to those changed paths, and wrap them with `[format "html"]` and `[end]`. For most users, that means that references to `[changes.path]` will become `[format "html"][changes.path][end]`. (This workaround should be reverted after upgrading to a patched version of ViewVC, else changed path names will be doubly escaped.)
Weakness: CWE-79
Which versions are affected by CVE-2023-22456?
It affects 1 product.
Products include Viewvc Viewvc.
How do I fix CVE-2023-22456?
Upgrade to a fixed version.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2023-22456 being exploited?
There is no known exploitation of CVE-2023-22456 in the wild and no public exploit code.
Other vulnerabilities in viewvc
Sources
Also known as GHSA-j4mx-f97j-gc5g, UBUNTU-CVE-2023-22456.