CVE-2022-20616 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in org.jenkins-ci.plugins:credentials-binding. A fix is available for org.jenkins-ci.plugins:credentials-binding — see the affected versions and patch details below.
Incorrect Permission Assignment for Critical Resource in Jenkins Credentials Binding Plugin
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:credentials-binding☕org.jenkins-ci.plugins:credentials-bindingReal-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 Credentials Binding Plugin prior to 1.27.1 and 1.24.1 does not perform a permission check in a method implementing form validation.
This allows attackers with Overall/Read access to validate if a credential ID refers to a secret file credential and whether it’s a zip file.
Credentials Binding Plugin 1.27.1 and 1.24.1 performs permission checks when validating secret file credentials IDs.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:credentials-binding | ≥ 1.25&&< 1.27.1 | 1.27.1org.jenkins-ci.plugins:credentials-binding:1.27.1 |
| ☕Maven | org.jenkins-ci.plugins:credentials-binding | all versions | 1.24.1org.jenkins-ci.plugins:credentials-binding:1.24.1 |
Affected Products
credentials bindingjenkinsDetection & 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:credentials-binding, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:credentials-binding to 1.27.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-20616 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-2022-20616 in your dependencies?
Find it across Maven, including transitive dependencies.