CVE-2023-22456
ViewVC Cross-Site Scripting Vulnerability
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.)
INFO
Published Date :
Jan. 3, 2023, 7:15 p.m.
Last Modified :
Nov. 21, 2024, 7:44 a.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
2.7
Exploitability Score :
2.8
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2023-22456
.
URL | Resource |
---|---|
https://github.com/viewvc/viewvc/issues/311 | Issue Tracking Third Party Advisory |
https://github.com/viewvc/viewvc/releases/tag/1.1.29 | Patch Third Party Advisory |
https://github.com/viewvc/viewvc/releases/tag/1.2.2 | Patch Third Party Advisory |
https://github.com/viewvc/viewvc/security/advisories/GHSA-j4mx-f97j-gc5g | Third Party Advisory |
https://github.com/viewvc/viewvc/issues/311 | Issue Tracking Third Party Advisory |
https://github.com/viewvc/viewvc/releases/tag/1.1.29 | Patch Third Party Advisory |
https://github.com/viewvc/viewvc/releases/tag/1.2.2 | Patch Third Party Advisory |
https://github.com/viewvc/viewvc/security/advisories/GHSA-j4mx-f97j-gc5g | Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2023-22456
vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2023-22456
vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Nov. 21, 2024
Action Type Old Value New Value Added Reference https://github.com/viewvc/viewvc/issues/311 Added Reference https://github.com/viewvc/viewvc/releases/tag/1.1.29 Added Reference https://github.com/viewvc/viewvc/releases/tag/1.2.2 Added Reference https://github.com/viewvc/viewvc/security/advisories/GHSA-j4mx-f97j-gc5g -
CVE Modified by [email protected]
May. 14, 2024
Action Type Old Value New Value -
CVE Modified by [email protected]
Nov. 07, 2023
Action Type Old Value New Value Changed 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.) 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.) -
Initial Analysis by [email protected]
Jan. 11, 2023
Action Type Old Value New Value Added CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N Changed Reference Type https://github.com/viewvc/viewvc/issues/311 No Types Assigned https://github.com/viewvc/viewvc/issues/311 Issue Tracking, Third Party Advisory Changed Reference Type https://github.com/viewvc/viewvc/releases/tag/1.1.29 No Types Assigned https://github.com/viewvc/viewvc/releases/tag/1.1.29 Patch, Third Party Advisory Changed Reference Type https://github.com/viewvc/viewvc/releases/tag/1.2.2 No Types Assigned https://github.com/viewvc/viewvc/releases/tag/1.2.2 Patch, Third Party Advisory Changed Reference Type https://github.com/viewvc/viewvc/security/advisories/GHSA-j4mx-f97j-gc5g No Types Assigned https://github.com/viewvc/viewvc/security/advisories/GHSA-j4mx-f97j-gc5g Third Party Advisory Added CPE Configuration OR *cpe:2.3:a:viewvc:viewvc:*:*:*:*:*:*:*:* versions up to (excluding) 1.1.29 *cpe:2.3:a:viewvc:viewvc:*:*:*:*:*:*:*:* versions from (including) 1.2.0 up to (excluding) 1.2.2
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2023-22456
is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2023-22456
weaknesses.
Exploit Prediction
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days.
0.10 }} -0.00%
score
0.40477
percentile