# CVE-2017-1000110: Improper Authentication in Jenkins Blue Ocean Plugin

> Attackers with read access can reconfigure GitHub organization folders to steal access tokens due to missing authorization checks.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Oct 2017
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-rm5m-9mx4-g5r7

## What is CVE-2017-1000110?

CVE-2017-1000110 is a medium-severity missing authorization vulnerability in n/a, published on 4 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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. 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2017-1000110?

2 open source packages ship an affected version, including io.jenkins.blueocean:blueocean. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `io.jenkins.blueocean:blueocean` | Maven | All versions | 1.2.0 |
| `io.jenkins.blueocean:blueocean` | Maven | All versions | 1.2.0 |

Products: Jenkins Blue Ocean.

## How do I fix CVE-2017-1000110?

Upgrade io.jenkins.blueocean:blueocean to 1.2.0 or later.

## Is CVE-2017-1000110 being exploited?

There is no known exploitation of CVE-2017-1000110 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-40341](https://insights.sbomify.com/CVE-2023-40341/): Jenkins Blue Ocean Plugin cross-site request forgery vulnerability (high 8.8)
- [CVE-2017-1000106](https://insights.sbomify.com/CVE-2017-1000106/): Improper Authentication in Jenkins Blue Ocean Plugin (high 8.5)
- [CVE-2022-30952](https://insights.sbomify.com/CVE-2022-30952/): Insufficiently Protected Credentials in Jenkins Pipeline SCM API for Blue Ocean Plugin (medium 6.5)
- [CVE-2022-30953](https://insights.sbomify.com/CVE-2022-30953/): Cross Site Request Forgery in Jenkins Blue Ocean Plugin (medium 6.5)
- [CVE-2022-30954](https://insights.sbomify.com/CVE-2022-30954/): Missing permission check in Jenkins Blue Ocean Plugin (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000110 and fix it if it is affected.

What it is: CVE-2017-1000110 is a medium-severity missing authorization vulnerability in n/a, published on 4 Oct 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-1000110 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.jenkins.blueocean:blueocean (Maven): affected all versions; fixed in 1.2.0
- io.jenkins.blueocean:blueocean (Maven): affected all versions; fixed in 1.2.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-1000110/ (Markdown: https://insights.sbomify.com/CVE-2017-1000110/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-1000110
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-1000110
- OSV: https://osv.dev/vulnerability/CVE-2017-1000110

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-1000110/
Summaries are generated and may contain mistakes; the official description above is the record.