CVE-2017-1000106
Last modified
CVE-2017-1000106 is a vulnerability of currently unknown severity. 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. Its SCM content REST API supports the pipeline creation and editing feature in Blue Ocean. EPSS estimates a 0.76% chance of exploitation in the next 30 days.
Description
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. Its SCM content REST API supports the pipeline creation and editing feature in Blue Ocean. The SCM content REST API did not check the current user's authentication or credentials. If the GitHub organization folder was created via Blue Ocean, it retained a reference to its creator's GitHub credentials. This allowed users with read access to the GitHub organization folder to create arbitrary commits in the repositories inside the GitHub organization corresponding to the GitHub organization folder with the GitHub credentials of the creator of the organization folder. Additionally, users with read access to the GitHub organization folder could read arbitrary file contents from the repositories inside the GitHub organization corresponding to the GitHub organization folder if the branch contained a Jenkinsfile (which could be created using the other part of this vulnerability), and they could provide the organization folder name, repository name, branch name, and file name.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Jenkins | Blue Ocean | <= 1.1.5 | — |
| Jenkins | Blue Ocean | 1.2.0 | Beta1 |
References
- https://jenkins.io/security/advisory/2017-08-07/Vendor Advisory
- https://jenkins.io/security/advisory/2017-08-07/Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-1000106?
How severe is CVE-2017-1000106?
How do I fix CVE-2017-1000106?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-1000100When doing a TFTP transfer and curl/libcurl is given a URL t…6.5
- CVE-2017-1000101curl supports "globbing" of URLs, in which a user can pass a…6.5
- CVE-2017-1000102The Details view of some Static Analysis Utilities based plu…
- CVE-2017-1000103The custom Details view of the Static Analysis Utilities bas…
- CVE-2017-1000104The Config File Provider Plugin is used to centrally manage …
- CVE-2017-1000105The optional Run/Artifacts permission can be enabled by sett…
- CVE-2017-1000107Script Security Plugin did not apply sandboxing restrictions…
- CVE-2017-1000108The Pipeline: Input Step Plugin by default allowed users wit…
- CVE-2017-1000109The custom Details view of the Static Analysis Utilities bas…
- CVE-2017-1000110Blue Ocean allows the creation of GitHub organization folder…
- CVE-2017-1000111Linux kernel: heap out-of-bounds in AF_PACKET sockets. This …7.8
- CVE-2017-1000112Linux kernel: Exploitable memory corruption due to UFO to no…7
Are you affected by CVE-2017-1000106?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
