First published: Tue Feb 20 2018(Updated: )
Jenkins before 2.107 and Jenkins LTS before 2.89.4 did not properly prevent specifying relative paths that escape a base directory for URLs accessing plugin resource files. This allowed users with Overall/Read permission to download files from the Jenkins master they should not have access to. On Windows, any file accessible to the Jenkins master process could be downloaded. On other operating systems, any file within the Jenkins home directory accessible to the Jenkins master process could be downloaded.
Credit: cve@mitre.org cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.jenkins-ci.main:jenkins-core | >=2.90<2.107 | 2.107 |
maven/org.jenkins-ci.main:jenkins-core | <2.89.4 | 2.89.4 |
Jenkins | <2.107 | |
Jenkins | <2.89.4 | |
Oracle Communications Cloud Native Core Automated Test Suite | =1.9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-6356 is categorized as a medium severity vulnerability due to its potential to allow unauthorized file access.
To fix CVE-2018-6356, upgrade Jenkins to version 2.107 or higher, or Jenkins LTS to version 2.89.4 or higher.
CVE-2018-6356 affects plugin resource files accessed through URLs within Jenkins.
Users with Overall/Read permission can potentially exploit CVE-2018-6356 to access restricted files.
Jenkins versions before 2.107 and Jenkins LTS versions before 2.89.4 are impacted by CVE-2018-6356.