CVE-2017-1000390 — jenkins-multijob-plugin
MEDIUMCVE-2017-1000390 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in org.jenkins-ci.plugins:jenkins-multijob-plugin. A fix is available for org.jenkins-ci.plugins:jenkins-multijob-plugin — see the affected versions and patch details below.
Jenkins Multijob plugin did not check permissions in the Resume Build action
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
org.jenkins-ci.plugins:jenkins-multijob-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
Jenkins Multijob plugin version 1.25 and earlier did not check permissions in the Resume Build action, allowing anyone with Job/Read permission to resume the build. Multijob plugin 1.26 introduced a permission check requiring Overall/Administer. This was lowered to Job/Build in version 1.27.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:jenkins-multijob-plugin | all versions | 1.26org.jenkins-ci.plugins:jenkins-multijob-plugin:1.26 |
Affected Products
multijobjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:jenkins-multijob-plugin, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:jenkins-multijob-plugin to 1.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-1000390 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 CVE-2017-1000390 in your dependencies?
Find it across Maven, including transitive dependencies.