JenkinsApplication
CVE-2017-1000393
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 2.73.1 and earlier, 2.83 and earlier users with permission to create or configure agents in Jenkins could configure a launch method called 'Launch agent via execution of command on master'. This allowed them to run arbitrary shell commands on the master node whenever the agent was supposed to be launched. Configuration of this launch method now requires the Run Scripts permission typically only granted to administrators.
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.73.1 and earlier, 2.83 and earlier allowed users with permission to create or configure agents to use the 'Launch agent via execution of command on master' launch method. This permitted arbitrary shell command execution on the master node, enabling privilege escalation from agent configuration permissions to full master node compromise.
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.1<= 2.83CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Jenkins versionNavigate to Manage Jenkins > About Jenkins, or run `java -jar jenkins.war --version`, or check the jenkins.war file versionAffected if Version is 2.73.1 or earlier, or 2.83 or earlier (versions below 2.74 or 2.84)
-
Verify agent create/configure permissions exist for non-adminsGo to Manage Jenkins > Configure Global Security > Authorization section. Check if any users or groups have Agent/Create or Agent/Configure permissions enabled without having Overall/Administer permissionAffected if Non-administrator users have Agent/Create or Agent/Configure permissions enabled
-
Identify agents using command launch methodNavigate to Manage Jenkins > Manage Nodes. For each agent, click the agent name > Configuration. Look for the 'Launch method' dropdown. If it shows 'Launch agent via execution of command on master', that agent is configured to use this methodAffected if Any agent is configured with 'Launch agent via execution of command on master' launch method
-
Check Run Scripts permission assignmentIn Configure Global Security > Authorization, verify which users or groups have the Run Scripts permission. This permission was required post-fix but not pre-fixAffected if Non-admin users with agent config permissions also have Run Scripts permission (indicating potential for full compromise in affected versions)
You are affected if your Jenkins version is 2.73.1/2.83 or earlier AND non-administrator users have Agent/Create or Agent/Configure permissions AND at least one agent uses the 'Launch agent via execution of command on master' launch method.
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 dataRestrict agent create/configure permissions to administrators only and ensure only admins have the Run Scripts permission. Upgrade to Jenkins 2.74+ or 2.84+ which require Run Scripts permission for this launch method.
Fix this in Jenkins
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000393 — 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-1000393 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