Active ChoicesApplication · Jenkins
CVE-2017-1000386
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 Active Choices plugin version 1.5.3 and earlier allowed users with Job/Configure permission to provide arbitrary HTML to be shown on the 'Build With Parameters' page through the 'Active Choices Reactive Reference Parameter' type. This could include, for example, arbitrary JavaScript. Active Choices now sanitizes the HTML inserted on the 'Build With Parameters' page if and only if the script is executed in a sandbox. As unsandboxed scripts are subject to administrator approval, it is up to the administrator to allow or disallow problematic script output.
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 Active Choices plugin versions 1.5.3 and earlier contained a stored XSS vulnerability in the 'Active Choices Reactive Reference Parameter' type. Users with Job/Configure permission could inject arbitrary HTML/JavaScript that would execute on the 'Build With Parameters' page. The fix sanitizes HTML when scripts run in a sandbox; unsandboxed scripts require administrator approval.
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
Active ChoicesApplication
<= 1.5.2= 1.5.3CVSS 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
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Verify Active Choices plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or use the Jenkins CLI: java -jar jenkins-cli.jar -s http://[jenkins-url] list-plugins | grep -i active-choicesAffected if The plugin is present in the installed plugins list
-
Determine the installed plugin versionIn Manage Plugins > Installed tab, locate 'Active Choices' and note the Version column; or check the plugin manifest file: $JENKINS_HOME/plugins/active-choices/META-INF/MANIFEST.MFAffected if Version is 1.5.3 or earlier (any version <= 1.5.3)
-
Identify jobs using Active Choices Reactive Reference ParameterNavigate to each job's Configure page and look for a parameter type named 'Active Choices Reactive Reference Parameter', or search job config XML files in $JENKINS_HOME/jobs/*/config.xml for the string 'ActiveChoicesReactiveReferenceParameter'Affected if Any job configuration contains the 'Active Choices Reactive Reference Parameter' parameter type
-
Check if scripts run without sandbox protectionIn a job's configuration, locate the Active Choices Reactive Reference Parameter section and verify whether the 'Sandbox' checkbox is enabled; unsandboxed scripts execute with full Groovy privilegesAffected if The 'Sandbox' checkbox is unchecked or missing for the reactive reference parameter
-
Review Job/Configure permission assignmentsNavigate to Manage Jenkins > Manage Users, or check matrix-based security at Manage Jenkins > Configure Global Security, to see which users or groups hold the 'Job/Configure' permissionAffected if Any user or group with Job/Configure permission is untrusted or unknown
You are affected if the Active Choices plugin version is 1.5.3 or earlier AND any job is configured to use the Active Choices Reactive Reference Parameter type, particularly with sandbox disabled.
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 the Jenkins Active Choices plugin to a version newer than 1.5.3. For environments where upgrading is not immediately possible, restrict Job/Configure permission to trusted users only and review existing job configurations for malicious parameter entries.
Fix this in Active Choices
Scoped from the published advisory
- Consultation1.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 $1,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-1000386 — 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-1000386 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