First published: Fri Jan 26 2018(Updated: )
Jenkins 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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins Active Choices | <=1.5.2 | |
Jenkins Active Choices | =1.5.3 | |
Jenkins Active Choices | =1.5.3-alpha |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-1000386 has a severity rating of medium, as it allows for the injection of arbitrary HTML or JavaScript code.
To fix CVE-2017-1000386, upgrade the Jenkins Active Choices plugin to version 1.5.4 or later.
Users with Job/Configure permission in Jenkins using the affected versions of the Active Choices plugin are vulnerable to CVE-2017-1000386.
CVE-2017-1000386 is a remote code execution vulnerability due to improper handling of user-defined parameters.
No, CVE-2017-1000386 requires authenticated users with specific Jenkins permissions to exploit the vulnerability.