CVE-2018-6356: Path Traversal
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
maven/org.jenkins-ci.main:jenkins-coreto a version that resolves this vulnerability.Fixed in 2.107 - Upgrade
Upgrade
maven/org.jenkins-ci.main:jenkins-coreto a version that resolves this vulnerability.Fixed in 2.89.4
Event History
Frequently Asked Questions
What is the severity of CVE-2018-6356?
CVE-2018-6356 is categorized as a medium severity vulnerability due to its potential to allow unauthorized file access.
How do I fix CVE-2018-6356?
To fix CVE-2018-6356, upgrade Jenkins to version 2.107 or higher, or Jenkins LTS to version 2.89.4 or higher.
What resources are affected by CVE-2018-6356?
CVE-2018-6356 affects plugin resource files accessed through URLs within Jenkins.
Who is affected by CVE-2018-6356?
Users with Overall/Read permission can potentially exploit CVE-2018-6356 to access restricted files.
What versions of Jenkins are impacted by CVE-2018-6356?
Jenkins versions before 2.107 and Jenkins LTS versions before 2.89.4 are impacted by CVE-2018-6356.