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.
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Link | Tags |
---|---|
http://www.openwall.com/lists/oss-security/2018/02/14/1 | third party advisory mailing list |
http://www.securityfocus.com/bid/103037 | vdb entry broken link |
https://www.oracle.com/security-alerts/cpuapr2022.html | third party advisory patch |
https://jenkins.io/security/advisory/2018-02-14/ | vendor advisory |