CVE-2020-2202 — fortify-on-demand-uploader
MEDIUMFix: jenkinsci/fortify-on-demand-uploader-plugin@28932f7CVE-2020-2202 is a medium-severity (CVSS 4.3) CWE-862 vulnerability in org.jenkins-ci.plugins:fortify-on-demand-uploader. A fix is available for org.jenkins-ci.plugins:fortify-on-demand-uploader — see the affected versions and patch details below.
Users with Overall/Read access could enumerate credentials IDs in Jenkins Fortify on Demand 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:fortify-on-demand-uploaderReal-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
Fortify on Demand Plugin provides a list of applicable credentials IDs to allow users configuring the plugin to select the one to use.
This functionality does not correctly check permissions in Fortify on Demand Plugin 6.0.0 and earlier, allowing any user with Overall/Read permission to get a list of valid credentials IDs. Those can be used as part of an attack to capture the credentials using another vulnerability.
An enumeration of credentials IDs in Fortify on Demand Plugin 6.0.1 now requires the appropriate permissions.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:fortify-on-demand-uploader | all versions | 6.0.1org.jenkins-ci.plugins:fortify-on-demand-uploader:6.0.1 |
Affected Products
fortify on demandjenkinsDetection & 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:fortify-on-demand-uploader, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:fortify-on-demand-uploader to 6.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-2202 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-2020-2202 in your dependencies?
Find it across Maven, including transitive dependencies.