CVE-2017-1000106: Improper Authentication in Jenkins Blue Ocean Plugin
Summary
CVE-2017-1000106: Improper Authentication in Jenkins Blue Ocean Plugin. Affects io.jenkins.blueocean:blueocean versions < 1.2.0. Fixed in 1.2.0. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Jenkins Blue Ocean Plugin is a tool that allows the creation and management of GitHub organization folders in Jenkins. These folders are used to scan GitHub organizations for repositories and branches containing a Jenkinsfile, and create corresponding pipelines in Jenkins. The Blue Ocean Plugin utilizes the SCM content REST API to support pipeline creation and editing. This API did not properly authenticate users, leading to a vulnerability in the plugin.
Vulnerability Detail
The vulnerability in the Jenkins Blue Ocean Plugin allowed users with read access to a GitHub organization folder to create arbitrary commits in the repositories inside the corresponding GitHub organization. This was possible because the plugin retained a reference to the creator's GitHub credentials. Additionally, users with read access could read arbitrary file contents from the repositories if the branch contained a Jenkinsfile. The vulnerability could be exploited by providing the organization folder name, repository name, branch name, and file name.
How To Fix
Minimum fixed version
1.2.0
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. It is recommended to update the plugin to the latest version as soon as possible.
Conclusion
The Jenkins Blue Ocean Plugin was vulnerable to improper authentication, allowing unauthorized users to create commits and read file contents in repositories within a GitHub organization. To mitigate this vulnerability, it is crucial to update the plugin to version 1.2.0 or later. Regularly monitoring and applying security updates is also recommended. For additional support, contact DevNack.com.
See every vulnerability recorded for io.jenkins.blueocean:blueocean →
FAQ
The vulnerability allowed unauthorized users to create commits and read file contents in repositories within a GitHub organization, potentially leading to unauthorized access and manipulation of sensitive data.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the pom.xml file.
There are no known public exploits for this vulnerability at the time of this report. However, it is important to update the plugin to the latest version to mitigate the risk.
In addition to updating the plugin, it is recommended to regularly monitor and apply security updates for all software components in your environment. This helps to ensure that known vulnerabilities are addressed promptly.
For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.
References
Related vulnerabilities
Recent vulnerabilities recorded for io.jenkins.blueocean:blueocean.
