Ssh CredentialsApplication · Jenkins
CVE-2018-1000601
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Jenkins SSH Credentials Plugin versions 1.13 and earlier contain an arbitrary file read vulnerability in BasicSSHUserPrivateKey.java. An authenticated attacker with permissions to configure credential bindings can read any file from the Jenkins master filesystem.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Ssh CredentialsApplication
<= 1.13CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if SSH Credentials Plugin is installedNavigate to Manage Jenkins > Manage Plugins > Installed tab. Search for 'SSH Credentials' in the list of installed plugins.Affected if The plugin is not listed in installed plugins, the vulnerability does not apply.
-
Determine installed SSH Credentials Plugin versionIn the Installed plugins tab, locate the SSH Credentials plugin and note the version number displayed in the Version column.Affected if Version is blank or cannot be determined from the UI.
-
Compare version against affected rangeCompare the installed version to the affected range: versions 1.13 and earlier are vulnerable. Version 1.14 and later are not affected.Affected if Installed version is 1.13 or lower (e.g., 1.13, 1.12, 1.11, etc.).
-
Verify user permissions for credential bindingsNavigate to Manage Jenkins > Configure Global Security. Check which users or groups have the 'Credentials' > 'Create' and 'Credentials' > 'Configure Binding' permissions, or review job configurations for credential binding settings.Affected if Non-admin users or untrusted accounts have permissions to configure credential bindings.
The environment is affected if SSH Credentials Plugin version 1.13 or earlier is installed AND non-admin users have permission to configure credential bindings in Jenkins.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Jenkins SSH Credentials Plugin to version 1.14 or later to remediate this vulnerability. Review user permissions for credential binding configurations in the interim.
Fix this in Ssh Credentials
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000601 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-1000601 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data