# CVE-2017-1000105: Missing Authorization in Jenkins Blue Ocean Plugin

> Attackers with Item/Read permissions can access archived artifacts in Jenkins Blue Ocean without the required Run/Artifacts permission.

- **Severity:** Medium 5.3 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Oct 2017
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-phf8-3qgv-rg5q

## What is CVE-2017-1000105?

CVE-2017-1000105 is a medium-severity missing authorization vulnerability in n/a, published on 4 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The optional Run/Artifacts permission can be enabled by setting a Java system property. Blue Ocean did not check this permission before providing access to archived artifacts, Item/Read permission was sufficient.

Weakness: CWE-862 (Missing Authorization)

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

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 to 1.2.4 | None |
| `io.jenkins.blueocean:blueocean` | Maven | All versions to 1.2.4 | None |

Products: Jenkins Blue Ocean.

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

No fix has been published for CVE-2017-1000105 yet. Limit exposure of the affected software until one is available.

## Is CVE-2017-1000105 being exploited?

There is no known exploitation of CVE-2017-1000105 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-1000105 and fix it if it is affected.

What it is: CVE-2017-1000105 is a medium-severity missing authorization vulnerability in n/a, published on 4 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-1000105 in the wild and no public exploit code.

Affected packages and fixed versions:
- io.jenkins.blueocean:blueocean (Maven): affected all versions up to 1.2.4; no fix listed
- io.jenkins.blueocean:blueocean (Maven): affected all versions up to 1.2.4; no fix listed

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-1000105/ (Markdown: https://insights.sbomify.com/CVE-2017-1000105/index.md)
```

## Sources

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

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