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

The remote Debian 10 host has packages installed that are affected by multiple vulnerabilities as referenced in the dla-3266 advisory.

  - 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.) (CVE-2023-22456)

  - 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.) (CVE-2023-22464)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of FreeBSD installed on the remote host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the 541696ed-8d12-11ed-af80-ecf4bbc0bda0 advisory.

  - 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.) (CVE-2023-22456)

  - 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.) (CVE-2023-22464)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
169915	Debian DLA-3266-1 : viewvc - LTS security update	Nessus	Debian Local Security Checks	medium
169702	FreeBSD : devel/viewvc-devel is vulnerable to cross-site scripting (541696ed-8d12-11ed-af80-ecf4bbc0bda0)	Nessus	FreeBSD Local Security Checks	medium

Detections

Analytics

CVE-2023-22456

medium

Tenable Plugins

medium

medium