GHSA-cj6r-8pxj-5jv6 Incorrect Permission Preservation in Jenkins Core

• Maven org.jenkins-ci.main:jenkins-core: >= 2.376, < 2.387.1 → fixed in 2.387.1 • Maven org.jenkins-ci.main:jenkins-core: < 2.375.4 → fixed in 2.375.4 • Maven org.jenkins-ci.main:jenkins-core: >= 2.388, < 2.394 → fixed in 2.394

Jenkins uses temporary directories adjacent to workspace directories, usually with the @tmp name suffix, to store temporary files related to the build. In pipelines, these temporary directories are adjacent to the current working directory when operating in a subdirectory of the automatically allocated workspace. Jenkins-controlled processes, like SCMs, may store credentials in these directories. Jenkins 2.393 and earlier, LTS 2.375.3 and earlier, and prior to LTS 2.387.1 shows these temporary directories when viewing job workspaces, which allows attackers with Item/Workspace permission to access their contents. Jenkins 2.394, LTS 2.375.4, and LTS 2.387.1 does not list these temporary directories in job workspaces. As a workaround, do not grant Item/Workspace permission to users who lack Item/Configure permission, if you’re concerned about this issue but unable to immediately update Jenkins.