Vulnerability record · CVE-2023-22456 · published 3 January 2023
CVE-2023-22456: Viewvc cross-site scripting vulnerability
Viewvc · Viewvc
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.)
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.)
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://github.com/viewvc/viewvc/issues/311 | Issue TrackingThird Party Advisory |
| https://github.com/viewvc/viewvc/releases/tag/1.1.29 | PatchThird Party Advisory |
| https://github.com/viewvc/viewvc/releases/tag/1.2.2 | PatchThird Party Advisory |
| https://github.com/viewvc/viewvc/security/advisories/GHSA-j4mx-f97j-gc5g | Third Party Advisory |
| https://github.com/viewvc/viewvc/issues/311 | Issue TrackingThird Party Advisory |
| https://github.com/viewvc/viewvc/releases/tag/1.1.29 | PatchThird Party Advisory |
| https://github.com/viewvc/viewvc/releases/tag/1.2.2 | PatchThird Party Advisory |
| https://github.com/viewvc/viewvc/security/advisories/GHSA-j4mx-f97j-gc5g | Third Party Advisory |
Track CVE-2023-22456 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2023-22456), CISA KEV, FIRST EPSS (scores of 2026-11-16). This page is refreshed as NVD updates the record.