CVE-2023-22464

ViewVC XSS vulnerability in revision view changed path "copyfrom" locations

MEDIUM
5.4
CVSS Score
Published: January 4, 2023 at 03:12 PM UTC
Updated: June 17, 2026 at 05:35 AM UTC
1 product affected across 1 vendorViewvc

Using viewvc by viewvc?

Get instant alerts when new vulnerabilities affect viewvc - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.4
Exploit prediction
EPSS 0.7%
SSVC
PoC

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.)

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 1.1.30v < 1.2.31.2.0 ≤ v < 1.2.3
Affected range stops below 1.1.30, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.2.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (4)

x_refsource_MISCExploitIssue TrackingMitigationThird Party Advisory
https://github.com/viewvc/viewvc/issues/311
x_refsource_MISCRelease NotesThird Party Advisory
https://github.com/viewvc/viewvc/releases/tag/1.1.30
x_refsource_MISCRelease NotesThird Party Advisory
https://github.com/viewvc/viewvc/releases/tag/1.2.3

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.4MEDIUMGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
REQUIRED
Scope
CHANGED
Confidentiality
LOW
Integrity
LOW
Availability
NONE
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-79CWE-80

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card