dbcve.org
JenkinsApplication

CVE-2017-1000354

HIGH · 8.8 CVSS v3.0 Published 2018-01-29
Fix available
A fix is available. Upgrade to after 2.56 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
Jenkins versions 2.56 and earlier as well as 2.46.1 LTS and earlier are vulnerable to a login command which allowed impersonating any Jenkins user. The `login` command available in the remoting-based CLI stored the encrypted user name of the successfully authenticated user in a cache file used to authenticate further commands. Users with sufficient permission to create secrets in Jenkins, and download their encrypted values (e.g. with Job/Configure permission), were able to impersonate any other Jenkins user on the same instance.

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 CLI login command stored encrypted usernames in a cache file used for authenticating subsequent commands. Users with permissions to create secrets and download encrypted values (such as Job/Configure permission) could read this cache and impersonate any Jenkins user on the instance.

MitigationUpgrade Jenkins to version 2.57 or later, or 2.46.2 LTS or later, to patch the login command cache vulnerability.

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
JenkinsApplication
Affected:<= 2.56<= 2.46.1

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

CVSS:3.0/AV:N/AC:L/PR:L/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 installed Jenkins version
    Navigate to Manage Jenkins > About Jenkins, or run `java -jar jenkins.war --version` from the server, or check the $JENKINS_HOME/war directory for the version manifest
    Affected if Version is 2.56 or earlier, or 2.46.1 LTS or earlier
  2. Verify CLI login cache file exists
    Search for the Jenkins CLI cache file at ~/.jenkins-cli.cache (user home directory) or $JENKINS_HOME/.jenkins-cli.cache
    Affected if A cache file named .jenkins-cli.cache exists and contains encrypted username entries
  3. Confirm CLI login was used
    Review the cache file content (if present) for entries under sections like [user] or [login] containing base64 or encrypted credential data
    Affected if The cache file contains login entries, indicating the CLI login command was previously executed
  4. Identify users with elevated permissions
    Navigate to Manage Jenkins > Manage Users, and check for users granted Job/Configure, Credentials/Manage, or Administer permissions via matrix authorization or project-based security
    Affected if Multiple users exist with permissions to create secrets or download encrypted credentials (Job/Configure, Credentials/Manage, or Administer)
  5. Review CLI authentication configuration
    Check Manage Jenkins > Configure Global Security > CLI section, or inspect $JENKINS_HOME/config.xml for <cliMode> or authentication settings
    Affected if CLI authentication is configured to allow password-based login rather than SSH key authentication

If Jenkins version is 2.56 or earlier (or 2.46.1 LTS or earlier), a CLI login cache file exists, and users with elevated permissions to create or read secrets are present, the environment is vulnerable to user impersonation through the exposed cache.

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.

From vendor data
Upgrade available Upgrade to a release after 2.56
Interim mitigation

Upgrade Jenkins to version 2.57 or later, or 2.46.2 LTS or later, to patch the login command cache vulnerability.

Fix this in Jenkins Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-1000354 — 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-1000354 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