dbcve.org
SshApplication · Jenkins

CVE-2017-1000245

CRITICAL · 9.8 CVSS v3.0 Published 2017-11-01
Fix available
A fix is available. Upgrade to after 2.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The SSH Plugin stores credentials which allow jobs to access remote servers via the SSH protocol. User passwords and passphrases for encrypted SSH keys are stored in plaintext in a configuration file.

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 confidence

The Jenkins SSH Plugin stores user passwords and passphrases for encrypted SSH keys in plaintext within a configuration file. This exposes credentials in clear text, allowing anyone with file system access to read sensitive authentication material used to access remote servers.

MitigationEnable the built-in Jenkins credentials store and migrate SSH credentials to use Jenkins' encrypted credential storage mechanism. Rotate all exposed passwords and SSH key passphrases immediately after remediation.

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
SshApplication
Affected:<= 2.4

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Jenkins SSH Plugin is installed
    Navigate to Manage Jenkins > Manage Plugins > Installed and look for 'SSH' plugin, or inspect the $JENKINS_HOME/plugins/ directory for the ssh plugin folder and its manifest
    Affected if The SSH plugin version is 2.4 or lower
  2. Locate the SSH plugin configuration file
    Inspect Jenkins configuration files in $JENKINS_HOME/ for XML files containing SSH-related configuration, typically in the main config.xml or in credentials.xml if SSH credentials were defined through Jenkins' native credentials management
    Affected if A configuration file exists in the Jenkins home directory that stores SSH plugin settings or credentials
  3. Search for plaintext passwords in configuration files
    Grep through XML configuration files in $JENKINS_HOME/ for patterns matching '<password>', '<passphrase>', or plain credential strings associated with SSH server definitions
    Affected if Any password or passphrase values appear in cleartext (not Base64-encoded or Jenkins-encrypted format) within configuration XML files
  4. Verify file permissions on the configuration directory
    Check file permissions on $JENKINS_HOME/ and its configuration files using 'ls -la' - ensure they are not world-readable
    Affected if Configuration files containing credentials are readable by users other than the Jenkins process owner

The environment is affected if the Jenkins SSH Plugin version 2.4 or lower is installed and plaintext passwords or passphrases are found in configuration files accessible beyond the Jenkins process owner.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2.4
Interim mitigation

Enable the built-in Jenkins credentials store and migrate SSH credentials to use Jenkins' encrypted credential storage mechanism. Rotate all exposed passwords and SSH key passphrases immediately after remediation.

Recommended fix Moderate confidence

SSH Plugin version 2.5 or later

  1. 1. Back up your Jenkins configuration and credentials store.
  2. 2. Navigate to Manage Jenkins > Manage Plugins.
  3. 3. Go to the 'Installed' tab and locate the SSH Plugin.
  4. 4. Check the current version of the SSH Plugin - if it is version 2.4 or earlier, an upgrade is required.
  5. 5. Go to the 'Available' tab and search for 'SSH Plugin'.
  6. 6. If a newer version is available, select it and click 'Install without restart' or 'Download now and install after restart'.
  7. 7. After installation, verify the new version is installed (should be version 2.5 or later).
  8. 8. Review credentials configuration in Manage Jenkins > Credentials to confirm credentials are now properly encrypted.
Caveat Verify that existing SSH credential configurations work correctly after upgrade, as the encryption mechanism may have changed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ssh Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000245 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-1000245 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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