First published: Thu Oct 05 2017(Updated: )
Blue Ocean allows the creation of GitHub organization folders that are set up to scan a GitHub organization for repositories and branches containing a Jenkinsfile, and create corresponding pipelines in Jenkins. It did not properly check the current user's authentication and authorization when configuring existing GitHub organization folders. This allowed users with read access to the GitHub organization folder to reconfigure it, including changing the GitHub API endpoint for the organization folder to an attacker-controlled server to obtain the GitHub access token, if the organization folder was initially created using Blue Ocean.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Jenkins | <=1.1.5 | |
Jenkins | =1.2.0-beta-1 | |
Jenkins | =1.2.0-beta-2 | |
Jenkins | =1.2.0-beta-3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-1000110 has been rated as a medium severity vulnerability.
To fix CVE-2017-1000110, you should upgrade to Blue Ocean versions 1.1.6 or later.
CVE-2017-1000110 affects specific versions of Jenkins Blue Ocean, particularly versions up to 1.1.5 and beta versions 1.2.0-beta-1 to 1.2.0-beta-3.
CVE-2017-1000110 allows unauthorized users to access and create GitHub organization folders in Jenkins.
While CVE-2017-1000110 is not a current threat if patched correctly, systems running vulnerable versions remain at risk.