Medium Subversion CVEs
11 CVEs, 1 protected by Waratek
Overview 11 matches · 1 protected · 0 exploited · 0 CISA KEV · 0 public PoC · 0 EPSS ≥ 0.5
Protected by Waratek
1
9.1%
Rule in development
0
0.0%
Mitigation candidate
0
0.0%
No exploit published
10
90.9%
blocked by ARMR today
1
9.1%
partly blocked
0
0.0%
not blocked
10
90.9%
not established
0
0.0%
unrecorded
0
0.0%
Exploited
0
0.0%
Working exploit published
0
0.0%
Proof of concept only
0
0.0%
Forecast only
0
0.0%
No public exploit
11
100.0%
split by
peak 4 / year
20171
No exploit published1
Medium1
not blocked1
No public exploit1
20181
No exploit published1
Medium1
not blocked1
No public exploit1
20190
20204
Protected by Waratek1
No exploit published3
Medium4
blocked by ARMR today1
not blocked3
No public exploit4
20210
20222
No exploit published2
Medium2
not blocked2
No public exploit2
20230
20243
No exploit published3
Medium3
not blocked3
No public exploit3
20172018201920202021202220232024
| CVE | Severity | Published▾ | Status | Exploitation | Description |
|---|---|---|---|---|---|
| CVE-2024-34148 | Medium | 2024-05-02 | No exploit published | No public exploit | Jenkins Subversion Partial Release Manager Plugin 1.0.1 and earlier programmatically disables the fix for CVE-2016-3721 whenever a build is triggered from a release tag, by setting the Java system property 'hudson.model.ParametersAction.keepUndefinedParameters'. |
| CVE-2024-28159 | Medium | 2024-03-06 | No exploit published | No public exploit | A missing permission check in Jenkins Subversion Partial Release Manager Plugin 1.0.1 and earlier allows attackers with Item/Read permission to trigger a build. |
| CVE-2024-28158 | Medium | 2024-03-06 | No exploit published | No public exploit | A cross-site request forgery (CSRF) vulnerability in Jenkins Subversion Partial Release Manager Plugin 1.0.1 and earlier allows attackers to trigger a build. |
| CVE-2022-29048 | Medium | 2022-04-12 | No exploit published | No public exploit | 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-2022-29046 | Medium | 2022-04-12 | No exploit published | No public exploit | 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-2020-2304 | Medium | 2020-11-04 | Protected by Waratek | No public exploit | Jenkins Subversion Plugin 2.13.1 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks. |
| CVE-2020-2199 | Medium | 2020-06-03 | No exploit published | No public exploit | Jenkins Subversion Partial Release Manager Plugin 1.0.1 and earlier does not escape the error message for the repository URL field form validation, resulting in a reflected cross-site scripting vulnerability. |
| CVE-2020-2152 | Medium | 2020-03-09 | No exploit published | No public exploit | Jenkins Subversion Release Manager Plugin 1.2 and earlier does not escape the error message for the Repository URL field form validation, resulting in a reflected cross-site scripting vulnerability. |
| CVE-2020-2111 | Medium | 2020-02-12 | No exploit published | No public exploit | 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 | Medium | 2018-03-13 | No exploit published | No public exploit | 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 | Medium | 2017-10-05 | No exploit published | No public exploit | 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. |