JenkinsApplication
CVE-2017-1000391
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 · uneditedJenkins versions 2.88 and earlier and 2.73.2 and earlier stores metadata related to 'people', which encompasses actual user accounts, as well as users appearing in SCM, in directories corresponding to the user ID on disk. These directories used the user ID for their name without additional escaping, potentially resulting in problems like overwriting of unrelated configuration files.
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 confidenceJenkins versions 2.88 and earlier and 2.73.2 and earlier stores user metadata (from actual user accounts and SCM users) in directories named after the raw user ID without sanitization/escaping. This path traversal vulnerability allows malicious user IDs to potentially overwrite or create arbitrary configuration files on the system.
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
<= 2.73.2<= 2.88CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Jenkins versionRun 'java -jar jenkins.war --version' from the Jenkins installation directory, or access /about in the Jenkins web UI, or check for a version file in the Jenkins home directoryAffected if The version is 2.73.2 or earlier, or any version from 2.74 through 2.88 inclusive. Versions 2.73.3 and later, or 2.89 and later are not affected.
-
Verify if user creation is enabledCheck the Jenkins security configuration at 'Manage Jenkins > Configure Global Security' and look at the 'Security Realm' setting. If it is set to 'Jenkins own user database' or allows user sign-up, users can be created.Affected if User creation is enabled - this is required for the vulnerability to be exploitable. If Jenkins uses an external security realm like LDAP, user creation through Jenkins is not possible.
-
Inspect user metadata directory for suspicious namesNavigate to the Jenkins home directory, then to the 'users' subdirectory. List all directory names and check if any contain path traversal characters like '../' or unusual patterns that could indicate attempted exploitation.Affected if Any user directory name contains path traversal sequences (such as '..') or appears to target specific configuration files. This indicates either an active exploit attempt or successful exploitation.
You are affected if your Jenkins version is 2.73.2 or earlier, or between 2.74 and 2.88 inclusive, AND user creation is enabled in your security configuration. Additionally, check the users directory for any directory names with path traversal characters as this indicates exploitation.
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 to version 2.89 or later, or 2.73.3 or later. Until upgraded, restrict who can create users and monitor for user IDs attempting to use path traversal characters.
Fix this in Jenkins
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing1.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,032.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000391 — 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-2017-1000391 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