CVE-2018-1000601 is a medium-severity (CVSS 6.5) Information Exposure vulnerability in org.jenkins-ci.plugins:ssh-credentials. A fix is available for org.jenkins-ci.plugins:ssh-credentials — see the affected versions and patch details below.
Exposure of Sensitive Information to an Unauthorized Actor in Jenkins SSH Credentials 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:ssh-credentials☕org.jenkins-ci.plugins:credentialsReal-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
A arbitrary file read vulnerability exists in Jenkins SSH Credentials Plugin 1.13 and earlier in BasicSSHUserPrivateKey.java that allows attackers with a Jenkins account and the permission to configure credential bindings to read arbitrary files from the Jenkins master file system.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.plugins:ssh-credentials | all versions | 1.14org.jenkins-ci.plugins:ssh-credentials:1.14 |
| ☕Maven | org.jenkins-ci.plugins:credentials | all versions | 2.1.17org.jenkins-ci.plugins:credentials:2.1.17 |
Affected Products
ssh credentialsjenkinsDetection & 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:ssh-credentials, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:ssh-credentials to 1.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-1000601 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2018-1000601 in your dependencies?
Find it across Maven, including transitive dependencies.