CVE-2022-25212 — swamp
HIGHCVE-2022-25212 is a high-severity (CVSS 8.8) Cross-Site Request Forgery (CSRF) vulnerability in org.continuousassurance.swamp.jenkins:swamp. No vendor fix is recorded yet; mitigation options are listed below.
CSRF vulnerability in Jenkins SWAMP Plugin allows capturing credentials
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2022-25212 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.continuousassurance.swamp.jenkins:swampReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
WAMP Plugin 1.2.6 and earlier does not perform a permission check in a method implementing form validation.\
This allows attackers with Overall/Read permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing credentials stored in Jenkins.
Additionally, this form validation method does not require POST requests, resulting in a cross-site request forgery (CSRF) vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.continuousassurance.swamp.jenkins:swamp | all versions | No fix |
Affected Products
swampjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.continuousassurance.swamp.jenkins:swamp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of org.continuousassurance.swamp.jenkins:swamp has shipped for CVE-2022-25212 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2022-25212 in your dependencies?
Find it across Maven, including transitive dependencies.