First published: Wed Oct 04 2017(Updated: )
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. Blue Ocean now correctly checks the Run/Artifacts permission if it’s enabled before providing access to artifacts.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/io.jenkins.blueocean:blueocean | <=1.2.4 | |
Jenkins | <=1.1.5 | |
Jenkins | =1.2.0-beta-1 | |
Jenkins | =1.2.0-beta-2 | |
Jenkins | =1.2.0-beta-3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-1000105 is classified as a medium severity vulnerability due to its potential to expose sensitive data.
To fix CVE-2017-1000105, ensure that the Run/Artifacts permission is enabled and verify the access control settings in Jenkins Blue Ocean.
CVE-2017-1000105 affects Jenkins Blue Ocean versions up to 1.1.5 and 1.2.0-beta versions up to 1.2.0-beta-3.
CVE-2017-1000105 exploits a lack of permission checks in Jenkins Blue Ocean that allows unauthorized access to archived artifacts.
No, CVE-2017-1000105 does not allow for code execution but it does enable unauthorized access to secured resources.