CVE-2023-22464: ViewVC is a browser interface for CVS and Subversion version control repositories. Versions prior to 1.2.3 and 1.1.30 are vulnerable to cross-site scr...

Description

ViewVC is a browser interface for CVS and Subversion version control repositories. Versions prior to 1.2.3 and 1.1.30 are vulnerable to cross-site scripting. 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.3 (if they are using a 1.2.x version of ViewVC) or 1.1.30 (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 one of the following workarounds. Users can edit their ViewVC EZT view templates to manually HTML-escape changed path "copyfrom 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.copy_path]` will become `[format "html"][changes.copy_path][end]`. (This workaround should be reverted after upgrading to a patched version of ViewVC, else "copyfrom path" names will be doubly escaped.)

Metrics

CVSS 3.1

5.4/10

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

EPSS Probability

0.64%

46.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

Vendor	Product	Versions
Viewvc	Viewvc	< 1.1.30
Viewvc	Viewvc	>= 1.2.0, < 1.2.3

References

https://github.com/viewvc/viewvc/issues/311Exploit, Issue Tracking, Mitigation, Third Party Advisory
https://github.com/viewvc/viewvc/releases/tag/1.1.30Release Notes, Third Party Advisory
https://github.com/viewvc/viewvc/releases/tag/1.2.3Release Notes, Third Party Advisory
https://github.com/viewvc/viewvc/security/advisories/GHSA-jvpj-293q-q53hMitigation, Third Party Advisory
https://github.com/viewvc/viewvc/issues/311Exploit, Issue Tracking, Mitigation, Third Party Advisory
https://github.com/viewvc/viewvc/releases/tag/1.1.30Release Notes, Third Party Advisory
https://github.com/viewvc/viewvc/releases/tag/1.2.3Release Notes, Third Party Advisory
https://github.com/viewvc/viewvc/security/advisories/GHSA-jvpj-293q-q53hMitigation, Third Party Advisory

Timeline

Published: Jan 4, 2023
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2023-22464?

ViewVC is a browser interface for CVS and Subversion version control repositories. Versions prior to 1.2.3 and 1.1.30 are vulnerable to cross-site scripting. 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.3 (if they are using a 1.2.x version of ViewVC) or 1.1.30 (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 one of the following workarounds. Users can edit their ViewVC EZT view templates to manually HTML-escape changed path "copyfrom 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.copy_path]` will become `[format "html"][changes.copy_path][end]`. (This workaround should be reverted after upgrading to a patched version of ViewVC, else "copyfrom path" names will be doubly escaped.)

How severe is CVE-2023-22464?

CVE-2023-22464 has a CVSS score of 5.4/10 (MEDIUM severity). The EPSS model estimates a 0.64% probability of exploitation in the next 30 days.

How do I fix CVE-2023-22464?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.