Incorrect permission check in XebiaLabs XL Deploy Plugin allows capturing credentialsGHSA-jm4g-8rvq-v87j
MEDIUMFix: jenkinsci/xldeploy-plugin@79ae204GHSA-jm4g-8rvq-v87j is a medium-severity (CVSS 6.5) CWE-863 vulnerability in com.xebialabs.deployit.ci:deployit-plugin. A fix is available for com.xebialabs.deployit.ci:deployit-plugin — see the affected versions and patch details below.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
com.xebialabs.deployit.ci:deployit-pluginReal-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
An incorrect permission check in Jenkins XebiaLabs XL Deploy Plugin 10.0.1 and earlier allows attackers with Generic Create permission to connect to an attacker-specified URL using attacker-specified credentials IDs obtained through another method, capturing Username/password credentials stored in Jenkins.
The permission check was partially fixed in XebiaLabs XL Deploy Plugin 7.5.9: A permission check was added, but for the wrong permission, still allowing some non-admin users to access the form validation method.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | com.xebialabs.deployit.ci:deployit-plugin | all versions | 10.0.2com.xebialabs.deployit.ci:deployit-plugin:10.0.2 |
Affected Products
xebialabs xl deployjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.xebialabs.deployit.ci:deployit-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.xebialabs.deployit.ci:deployit-plugin to 10.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jm4g-8rvq-v87j is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is GHSA-jm4g-8rvq-v87j in your dependencies?
Find it across Maven, including transitive dependencies.