Read the docs

Blue Ocean allows the creation of GitHub organization folders that are set up to scan a…

Priority LOW 38CWE-287Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
Low · High · None
Fix status
Fixed

Attack profile from CVSS 3.0 · NVD. Fix status from CNA and GitHub. Impact type from CWE-287.

Summary

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.

Why it matters now

EPSS 0.00758 55th percentileScored 2026-11-07
Fix Fixed io.jenkins.blueocean:blueocean (Maven): 1.2.0

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
——all versions—No fix listedCNA
—io.jenkins.blueocean:blueocean (Maven)before 1.2.01.2.0Patch availableGHSA-qgjq-m78x-4gm8
  • — Vendor— Affected all versions Fixed in — No fix listed CNA
  • io.jenkins.blueocean:blueocean (Maven) Vendor— Affected before 1.2.0 Fixed in 1.2.0 Patch available GHSA-qgjq-m78x-4gm8

CPE configurations NVD · 4

CPEVersionsRoleVendor
cpe:2.3:a:jenkins:blue_ocean:*:*:*:*:*:jenkins:*:*up to 1.1.5VulnerableJenkins
cpe:2.3:a:jenkins:blue_ocean:1.2.0:beta1:*:*:*:jenkins:*:*1.2.0 beta1VulnerableJenkins
cpe:2.3:a:jenkins:blue_ocean:1.2.0:beta2:*:*:*:jenkins:*:*1.2.0 beta2VulnerableJenkins
cpe:2.3:a:jenkins:blue_ocean:1.2.0:beta3:*:*:*:jenkins:*:*1.2.0 beta3VulnerableJenkins
  • cpe:2.3:a:jenkins:blue_ocean:*:*:*:*:*:jenkins:*:* Versions up to 1.1.5 Vulnerable ·Jenkins
  • cpe:2.3:a:jenkins:blue_ocean:1.2.0:beta1:*:*:*:jenkins:*:* Versions 1.2.0 beta1 Vulnerable ·Jenkins
  • cpe:2.3:a:jenkins:blue_ocean:1.2.0:beta2:*:*:*:jenkins:*:* Versions 1.2.0 beta2 Vulnerable ·Jenkins
  • cpe:2.3:a:jenkins:blue_ocean:1.2.0:beta3:*:*:*:jenkins:*:* Versions 1.2.0 beta3 Vulnerable ·Jenkins

Remediation

  • Fix · GHSA-qgjq-m78x-4gm8 io.jenkins.blueocean:blueocean (Maven) Fixed in 1.2.0 Advisory →

Timeline

  1. 2026-10-02 Threatist record created from CVE-2017-1000106
  2. 2026-10-03 Alias added: GHSA-qgjq-m78x-4gm8

References

  • TI-2023-21170 Cross-site request forgery in Jenkins Blue Ocean Plugin CVSS 3.1HIGH 8.8
  • TI-2020-02131 Path traversal in Jenkins Blue Ocean Plugin CVSS 3.1MEDIUM 6.5
  • TI-2022-13010 Missing authorization in Jenkins Blue Ocean Plugin CVSS 3.1MEDIUM 6.5
  • TI-2022-13008 Insufficiently protected credentials in Jenkins Pipeline SCM API for Blue Ocean Plugin CVSS 3.1MEDIUM 6.5
  • TI-2019-15857 Cross-site request forgery in Jenkins Blue Ocean Plugins CVSS 3.0MEDIUM 6.5
  • TI-2022-13009 Cross-site request forgery in Jenkins Blue Ocean Plugin CVSS 3.1MEDIUM 6.5
See all 10 →

Sources