CVE-2023-22456

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

Configuration 1 (hide)

OR cpe:2.3:a:viewvc:viewvc:*:*:*:*:*:*:*:*
cpe:2.3:a:viewvc:viewvc:*:*:*:*:*:*:*:*

History

21 Nov 2024, 07:44

Type Values Removed Values Added
References () https://github.com/viewvc/viewvc/issues/311 - Issue Tracking, Third Party Advisory () https://github.com/viewvc/viewvc/issues/311 - Issue Tracking, Third Party Advisory
References () https://github.com/viewvc/viewvc/releases/tag/1.1.29 - Patch, Third Party Advisory () https://github.com/viewvc/viewvc/releases/tag/1.1.29 - Patch, Third Party Advisory
References () https://github.com/viewvc/viewvc/releases/tag/1.2.2 - Patch, Third Party Advisory () https://github.com/viewvc/viewvc/releases/tag/1.2.2 - Patch, Third Party Advisory
References () https://github.com/viewvc/viewvc/security/advisories/GHSA-j4mx-f97j-gc5g - Third Party Advisory () https://github.com/viewvc/viewvc/security/advisories/GHSA-j4mx-f97j-gc5g - Third Party Advisory
Summary
  • (es) ViewVC, una interfaz de navegador para repositorios de control de versiones de CVS y Subversion, es una vulnerabilidad de cross-site scripting que afecta a versiones anteriores a 1.2.2 y 1.1.29. El impacto de esta vulnerabilidad se ve mitigado por la necesidad de que un atacante tenga privilegios de confirmación en un repositorio de Subversion expuesto por una instancia de ViewVC que, de otro modo, sería de confianza. El vector de ataque implica archivos con nombres no seguros (nombres que, al incrustarse en una secuencia HTML, harían que el navegador ejecutara código no deseado), que pueden ser difíciles de crear. Los usuarios deben actualizar al menos a la versión 1.2.2 (si están usando una versión 1.2.x de ViewVC) o 1.1.29 (si están usando una versión 1.1.x). ViewVC 1.0.x ya no es compatible, por lo que los usuarios de esa línea de versiones deben implementar un workaround. Los usuarios pueden editar sus plantillas de vista EZT de ViewVC para escapar manualmente mediante HTML las rutas modificadas durante la representación. Localice en el archivo `revision.ezt` de su conjunto de plantillas las referencias a esas rutas modificadas y enciérrelas con `[format "html"]` y `[end]`. Para la mayoría de los usuarios, eso significa que las referencias a `[changes.path]` se convertirán en `[format "html"][changes.path][end]`. (Este workaround se debe revertir después de actualizar a una versión parcheada de ViewVC, de lo contrario, los nombres de las rutas modificadas se escaparán dos veces).

07 Nov 2023, 04:06

Type Values Removed Values Added
Summary 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.) 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.)

Information

Published : 2023-01-03 19:15

Updated : 2024-11-21 07:44


NVD link : CVE-2023-22456

Mitre link : CVE-2023-22456

CVE.ORG link : CVE-2023-22456


JSON object : View

Products Affected

viewvc

  • viewvc
CWE
CWE-79

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')