CVE-2017-1000110: Blueocean Improper Authentication Vulnerability

MODERATE
Advisory Identifier: GHSA-rm5m-9mx4-g5r7
Share
CVSS 4.3
CWE-287
Published
Advisory Summary

CVE-2017-1000110 is a MODERATE (CVSS 4.3) 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-1000110 at a Glance

CVE Identifier CVE-2017-1000110
GHSA Identifier GHSA-rm5m-9mx4-g5r7
Severity MODERATE
CVSS v3.1 Base Score 4.3
CWE Classification CWE-287: Improper Authentication
Affected Product Blueocean
Package Ecosystem Maven
Published Date
Last Updated

Security Impact

CVSS: 4.3

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:U/C:N/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2017-1000110

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.

io.jenkins.blueocean:blueocean fixed: 1.2.0 
<dependency>
    <groupId>io.jenkins.blueocean</groupId>
    <artifactId>blueocean</artifactId>
    <version>1.2.0</version>
</dependency>
Verify Direct and Transitive Dependencies

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-1000110, 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

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.

CVE-2017-1000110 Affected Blueocean Versions

1 component(s)
Fixed Versions:
1.2.0
Product / Package Ecosystem Affected Versions Fixed Version
io.jenkins.blueocean:blueocean
maven/io.jenkins.blueocean/blueocean
Maven
< 1.2.0
1.2.0

References

NVD — CVE-2017-1000110 NVD
https://nvd.nist.gov/vuln/detail/CVE-2017-1000110
Blueocean Security Information SECURITY
https://jenkins.io/security/advisory/2017-08-07

Frequently Asked Questions

What is CVE-2017-1000110?
CVE-2017-1000110 is a security vulnerability in Blueocean involving Improper Authentication in Jenkins Blue Ocean Plugin under CWE-287: Improper Authentication.
Which Blueocean versions are affected?
Affected versions include releases prior to 1.2.0 across affected packages: io.jenkins.blueocean:blueocean.
What version fixes CVE-2017-1000110?
Upgrading to 1.2.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is blueocean affected?
Yes, io.jenkins.blueocean:blueocean is affected in releases prior to 1.2.0. Upgrade your dependency to 1.2.0 or later.
What is the CVSS score of CVE-2017-1000110?
CVE-2017-1000110 has a CVSS v3.1 base score of 4.3 (MODERATE) with vector string CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N.
What CWE is associated with CVE-2017-1000110?
CVE-2017-1000110 is classified under CWE-287: Improper Authentication (When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.).
How can I check Maven dependencies for CVE-2017-1000110?
Run the dependency tree command: 'mvn dependency:tree -Dincludes=io.jenkins.blueocean'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rm5m-9mx4-g5r7",
  "modified" : "2022-11-01T23:01:41Z",
  "published" : "2022-05-13T01:40:56Z",
  "aliases" : [ "CVE-2017-1000110" ],
  "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. 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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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-1000110"
  }, {
    "type" : "WEB",
    "url" : "https://jenkins.io/security/advisory/2017-08-07"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-287" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2022-11-01T23:01:41Z",
    "nvd_published_at" : "2017-10-05T01:29:00Z"
  }
}