CVE-2017-1000106: Blueocean Improper Authentication Vulnerability
HIGHCVE-2017-1000106 is a HIGH (CVSS 8.5) improper authentication vulnerability (CWE-287: Improper Authentication) affecting Blueocean libraries in the Maven ecosystem. The issue involves improper authentication in jenkins blue ocean plugin. Remediation is available by upgrading affected packages to version 1.2.0.
CVE-2017-1000106 at a Glance
Security Impact
CVSS: 8.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N).
How to Fix CVE-2017-1000106
To remediate this vulnerability, upgrade all affected Blueocean dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>io.jenkins.blueocean</groupId>
<artifactId>blueocean</artifactId>
<version>1.2.0</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=io.jenkins.blueocean
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2017-1000106, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=io.jenkins.blueocean
Analyze the terminal output to locate any version of Blueocean in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.2.0), your application is affected.
Note: The mvn dependency:tree -Dincludes=io.jenkins.blueocean command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-287: Improper Authentication, where when an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. In Blueocean, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2017-1000106 Affected Blueocean Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
io.jenkins.blueocean:blueocean
|
Maven |
< 1.2.0
|
1.2.0
|
References
Frequently Asked Questions
What is CVE-2017-1000106?
Which Blueocean versions are affected?
What version fixes CVE-2017-1000106?
Is blueocean affected?
What is the CVSS score of CVE-2017-1000106?
What CWE is associated with CVE-2017-1000106?
How can I check Maven dependencies for CVE-2017-1000106?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-qgjq-m78x-4gm8",
"modified" : "2022-11-01T23:01:07Z",
"published" : "2022-05-13T01:40:57Z",
"aliases" : [ "CVE-2017-1000106" ],
"summary" : "Improper Authentication in Jenkins Blue Ocean Plugin",
"details" : "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.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "io.jenkins.blueocean:blueocean"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "1.2.0"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2017-1000106"
}, {
"type" : "WEB",
"url" : "https://jenkins.io/security/advisory/2017-08-07"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-287" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2022-11-01T23:01:07Z",
"nvd_published_at" : "2017-10-05T01:29:00Z"
}
}