Jenkins Subversion vulnerabilities

7 vulnerabilities

Known vulnerabilities in Jenkins Subversion, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.

5.3CVE-2018-1000111jenkinssubversion+1
EPSS score
0.90%
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.7.5CVE-2021-21698jenkins projectjenkins subversion plugin+2
EPSS score
2.14%
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.5.4CVE-2020-2111jenkins projectjenkins subversion plugin+2
EPSS score
0.92%
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.6.5CVE-2020-2304jenkins projectjenkins subversion plugin+2
EPSS score
1.52%
Jenkins Subversion Plugin 2.13.1 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.4.3CVE-2022-29048applemacos+3
EPSS score
1.88%
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.5.4CVE-2022-29046applemacos+3
EPSS score
2.51%
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.6.5CVE-2017-1000085jenkinssubversion+1
EPSS score
1.03%
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.