Total
7 CVE
CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
---|---|---|---|---|---|
CVE-2022-29046 | 2 Apple, Jenkins | 2 Macos, Subversion | 2024-02-28 | 3.5 LOW | 5.4 MEDIUM |
Jenkins Subversion Plugin 2.15.3 and earlier does not escape the name and description of List Subversion tags (and more) parameters on views displaying parameters, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission. | |||||
CVE-2022-29048 | 2 Apple, Jenkins | 2 Macos, Subversion | 2024-02-28 | 4.3 MEDIUM | 4.3 MEDIUM |
A cross-site request forgery (CSRF) vulnerability in Jenkins Subversion Plugin 2.15.3 and earlier allows attackers to connect to an attacker-specified URL. | |||||
CVE-2021-21698 | 1 Jenkins | 1 Subversion | 2024-02-28 | 5.0 MEDIUM | 7.5 HIGH |
Jenkins Subversion Plugin 2.15.0 and earlier does not restrict the name of a file when looking up a subversion key file on the controller from an agent. | |||||
CVE-2020-2304 | 1 Jenkins | 1 Subversion | 2024-02-28 | 4.0 MEDIUM | 6.5 MEDIUM |
Jenkins Subversion Plugin 2.13.1 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks. | |||||
CVE-2020-2111 | 1 Jenkins | 1 Subversion | 2024-02-28 | 3.5 LOW | 5.4 MEDIUM |
Jenkins Subversion Plugin 2.13.0 and earlier does not escape the error message for the Project Repository Base URL field form validation, resulting in a stored cross-site scripting vulnerability. | |||||
CVE-2018-1000111 | 1 Jenkins | 1 Subversion | 2024-02-28 | 5.0 MEDIUM | 5.3 MEDIUM |
An improper authorization vulnerability exists in Jenkins Subversion Plugin version 2.10.2 and earlier in SubversionStatus.java and SubversionRepositoryStatus.java that allows an attacker with network access to obtain a list of nodes and users. | |||||
CVE-2017-1000085 | 1 Jenkins | 1 Subversion | 2024-02-28 | 4.3 MEDIUM | 6.5 MEDIUM |
Subversion Plugin connects to a user-specified Subversion repository as part of form validation (e.g. to retrieve a list of tags). This functionality improperly checked permissions, allowing any user with Item/Build permission (but not Item/Configure) to connect to any web server or Subversion server and send credentials with a known ID, thereby possibly capturing them. Additionally, this functionality did not require POST requests be used, thereby allowing the above to be performed without direct access to Jenkins via Cross-Site Request Forgery attacks. |