Subversion Plugin connects to a user-specified Subversion repository as part of form validation (e.g.
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.
- Published
- Oct 4, 2017
- Updated
- Jun 16, 2026
- EPSS
- 1.0% · 62th percentile
- CWE
- CWE-352
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 1.0%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| jenkins | subversion | cpe:2.3:a:jenkins:subversion |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- jenkins subversionup to 2.8 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.jenkins-ci.plugins:subversion | before 2.9 | 2.9 |
| Red Hat:openshift:3.6::el7 | atomic-openshift | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | atomic-openshift-clients | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | atomic-openshift-clients-redistributable | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | atomic-openshift-cluster-capacity | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | atomic-openshift-docker-excluder | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | atomic-openshift-dockerregistry | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | atomic-openshift-excluder | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | atomic-openshift-federation-services | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | atomic-openshift-master | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | atomic-openshift-node | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | atomic-openshift-pod | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | atomic-openshift-sdn-ovs | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | atomic-openshift-service-catalog | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | atomic-openshift-tests | before 0:3.6.173.0.21-1.git.0.f95b0e7.el7 | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 |
| Red Hat:openshift:3.6::el7 | fluentd | before 0:0.12.39-2.el7 | 0:0.12.39-2.el7 |
| Red Hat:openshift:3.6::el7 | fluentd-doc | before 0:0.12.39-2.el7 | 0:0.12.39-2.el7 |
| Red Hat:openshift:3.6::el7 | jenkins-2-plugins | before 0:3.7.1502412812-1.el7 | 0:3.7.1502412812-1.el7 |
| Red Hat:openshift:3.6::el7 | kibana | before 0:4.6.4-3.el7 | 0:4.6.4-3.el7 |
| Red Hat:openshift:3.6::el7 | kibana-debuginfo | before 0:4.6.4-3.el7 | 0:4.6.4-3.el7 |
| Red Hat:openshift:3.6::el7 | rubygem-cool.io | before 0:1.5.1-1.el7 | 0:1.5.1-1.el7 |
| Red Hat:openshift:3.6::el7 | rubygem-cool.io-debuginfo | before 0:1.5.1-1.el7 | 0:1.5.1-1.el7 |
| Red Hat:openshift:3.6::el7 | rubygem-cool.io-doc | before 0:1.5.1-1.el7 | 0:1.5.1-1.el7 |
| Red Hat:openshift:3.6::el7 | rubygem-excon | before 0:0.58.0-1.el7 | 0:0.58.0-1.el7 |
+12
Same product
jenkins: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-21698Jenkins 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 fr31Monitor
- CVE-2020-2304Jenkins Subversion Plugin 2.13.1 and earlier does not configure its XML parser to prevent XML external entity (XXE) attacks.26Monitor
- CVE-2022-29046Jenkins Subversion Plugin 2.15.3 and earlier does not escape the name and description of List Subversion tags (and more) parameters on views22Monitor
- CVE-2020-2111Jenkins Subversion Plugin 2.13.0 and earlier does not escape the error message for the Project Repository Base URL field form validation, re21Monitor
- CVE-2018-1000111An improper authorization vulnerability exists in Jenkins Subversion Plugin version 2.10.2 and earlier in SubversionStatus.java and Subversi21Monitor
- CVE-2022-29048A cross-site request forgery (CSRF) vulnerability in Jenkins Subversion Plugin 2.15.3 and earlier allows attackers to connect to an attacker18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.jenkins-ci.plugins:subversion | 2.9 | Package registry (OSV) |
| red hat:atomic-openshift | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 · Red Hat:openshift:3.6::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 · Red Hat:openshift:3.6::el7 | Package registry (OSV) |
| red hat:atomic-openshift-clients-redistributable | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 · Red Hat:openshift:3.6::el7 | Package registry (OSV) |
| red hat:atomic-openshift-cluster-capacity | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 · Red Hat:openshift:3.6::el7 | Package registry (OSV) |
| red hat:atomic-openshift-docker-excluder | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 · Red Hat:openshift:3.6::el7 | Package registry (OSV) |
| red hat:atomic-openshift-dockerregistry | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 · Red Hat:openshift:3.6::el7 | Package registry (OSV) |
| red hat:atomic-openshift-excluder | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 · Red Hat:openshift:3.6::el7 | Package registry (OSV) |
| red hat:atomic-openshift-federation-services | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 · Red Hat:openshift:3.6::el7 | Package registry (OSV) |
| red hat:atomic-openshift-master | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 · Red Hat:openshift:3.6::el7 | Package registry (OSV) |
| red hat:atomic-openshift-node | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 · Red Hat:openshift:3.6::el7 | Package registry (OSV) |
| red hat:atomic-openshift-pod | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 · Red Hat:openshift:3.6::el7 | Package registry (OSV) |
| red hat:atomic-openshift-sdn-ovs | 0:3.6.173.0.21-1.git.0.f95b0e7.el7 · Red Hat:openshift:3.6::el7 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.