Jenkins Subversion 1.29 for Jenkins

CPE Details

Jenkins Subversion 1.29 for Jenkins
jenkins
subversion
1.29
2019-04-25
12h08 +00:00
2019-04-25
12h08 +00:00
CPE NVD
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:jenkins:subversion:1.29:*:*:*:*:jenkins:*:*

Informations

Vendor

jenkins

Product

subversion

Version

1.29

Target Software

jenkins

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2022-29048 2022-04-12 17h50 +00:00 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.
4.3
Medium
CVE-2022-29046 2022-04-12 17h50 +00:00 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.
5.4
Medium
CVE-2021-21698 2021-11-04 15h30 +00:00 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.
7.5
High
CVE-2020-2304 2020-11-04 13h35 +00:00 Jenkins Subversion Plugin 2.13.1 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.
6.5
Medium
CVE-2020-2111 2020-02-12 13h35 +00:00 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.
5.4
Medium
CVE-2018-1000111 2018-03-13 13h00 +00:00 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.
5.3
Medium
CVE-2017-1000085 2017-10-03 23h00 +00:00 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.
6.5
Medium